new question.......dsr6000

[Mikell808]

It appears that my DSR6000 has failed and it is not necessarily the drive. No matter what I do it just sticks on the powering up screen. My question is about being able to use the drive from this DSR6000 in another DSR6000. I have one still funcitoning in the other room. I would like to try and at least go thru the recordings and get caught up. I know in the past I was not able to image a drive from one and have it work in the other. Is there something i can do?

Also any thoughts on the powering up screen issue, I would like to try and fix that, at this point I have reseated all the cables and pulled the mother board battery out hoping it would reset the mother board.

[eastwind]

Pull the drive, mount it in a PC, and check the logs. They might give you a clue.

ew

[Mikell808]

How do I check the logs? While I am asking questions.......I have been doing alot of reading and came across a post about cleaning some type of metal strip that is part of the power supply. I have not been able to figure out what that my might be.......any ideas?

[ScanMan]

The logs are in /var which tivo mounts as the 9th partition on the drive. Mount the 9th partition and look for /var/log/kernel for the kernel log. Post it here so others can assist.

[Mikell808]

The logs are in /var which tivo mounts as the 9th partition on the drive. Mount the 9th partition and look for /var/log/kernel for the kernel log. Post it here so others can assist.

There was a time when I would know exactly what mounting the 9th partition means. I do know how load and run msftools, I have also recently downloaded and created the boot cd for pvr tools. What would be the command line to mount the drive. Then I do know how to get to the var/log kernal directory. Then what is the command line to read a log file.

Thanks.

[ScanMan]

See my post here (http://www.dealdatabase.com/forum/showpost.php?p=256399&postcount=6) that has some general information about mounting drives in linux. So, assuming you have a fat/fat32 and your tivo drive attached to your pc and you've booted from the ptv cd, you would do something like the following:

1. Make mount points and mount drives

mkdir /tivo9
mount /dev/hdx9 /tivo9

"x" is the drive letter of the tivo mapped in your PC's IDE chain.

mkdir /fat
mount -t vfat /dev/hdy1 /fat

"y" is the drive letter of the fat/fat32 mapped in your PC's IDE chain.

2. Copy kernel log over to fat drive

cp /tivo9/log/kernel /fat

If something's unclear, post a question...

[Mikell808]

I get an error mesage after entering mount dev/hdc9 /tivo9 saying "must specify file system.

I don't know if it is important, but my computer is running xp using ntfs not fat32.

[ScanMan]

I get an error mesage after entering mount dev/hdc9 /tivo9 saying "must specify file system.Might just be a typo but you're missing a backslash: /dev/hdc9

The type would be ext2 though; also, I believe Series 1 tivos need to boot with byteswapping enabled; should be OK with mfstools but you might need to throw a command line switch at the ptv boot cd.

I don't know if it is important, but my computer is running xp using ntfs not fat32.It would be important if you needed to save (write) a file to your PC's hard disk.

[Mikell808]

Might just be a typo but you're missing a backslash: /dev/hdc9

It would be important if you needed to save (write) a file to your PC's hard disk.


Yes it is a Typo and based on your instruction I am supposed to copy the log file to my PCs hard drive which is NTFS. I could probably connect an old unused FAT32 drive if needed. What would be the new command lines to accomplish this.

[ScanMan]

What about a floppy drive? The kernel log shouldn't be more than 1.44M. A DOS formatted floppy disk would typically be mounted like:

mount -t msdos /dev/fd0 /mnt/floppy

You could also use a USB thumb drive but they are hardware specific; generally mounted as /dev/sda.

[ScanMan]

Another thought; if you're getting that "must specify file system" error, it's likely your boot cd isn't recognizing your tivo drive, probably due to the byte swapping issue. Do you see a partition map in the boot messages? I have read there are problems with the ptvupgrade disk in mounting series 1 drives.

As I said the MFSTools boot cd may work OK, but if not you may want to get an older boot cd like Kazymyr's located here (http://www.9thtee.com/tivobootcd.htm); just be aware it's not LBA48 aware and thus will not properly recognize drives > 137GB. I have used it on my S1 Philips and it's never failed me...

[freakyb]

While I am asking questions.......I have been doing alot of reading and came across a post about cleaning some type of metal strip that is part of the power supply. I have not been able to figure out what that my might be.......any ideas?

It's the little white ribbon cable that runs between the power supply and the motherboard to supply power to the motherboard.. Yes, I'd definitely check this. Take it out, clean off the silvery metal ends, and put it back in. That may fix your problem, at least temporarily. If you find that it helps but the problem comes back, you can buy a new cable at weaknees -- it's referred to as a Parlex cable.