dmprantz
02-08-2006, 09:08 PM
Background:
I have a Seriens 1 DTiVo, DSR6000. I had upgraded the HDD so that it had a 60GB and a 40GB. 4 MFS pairs between the two HDDs. I felt that I detected that one of the HDDs was going bad, so I bought a new 250 GB Maxtor drive, and copied everything over. Because of the 16 partition A Drive limit, I had to combine some partitions. I did this with pdisk, turning the 8 total into 4 total. I then used MFSTools to expand and add one more pair. I then used the PVRUpgrade boot CD and copykern to put on a 3.1.0 kernel that supports LBA48. At that point everything seemed to be going well, and the unit worked for several days. Last time I remember using it was Sunday night (72 hours ago) to record/watch the Superbowl.
Tonight I turned on the TV and saw the following message on screen, "Can't boot kernel" I had never seen this before, so I tried to power cycle, same thing. I took the drive out, and connected it to the computer again. Tried to rerun copykern, and it kept complaining about unknown boot sector signature. it also didn't mount /dev/hda on /cdrom appropriately. I Tried to mount /dev/hdX9 to check out the logs, and the file system didn't like that. It reported something like "Value too large..." Finally, I decided to reboot and dd /dev/hdX2, /dev/hdX3, /dev/hdX4, /dev/hdX5, /dev/hdX6, and /dev/hdX7 from the old A-Drive to the new one. I then had to manually mount /dev/hda as /cdrom again, re-ran copykern, and that time it worked correctly. I put the drive back in the TiVo, turned it on, and it booted fine, but now it is running through GSOD/reboot over and over again. I figure I'll give it an hour in case it's actually doing something, and then check the logs.
Any one know what's going on? Ever hear of this before? If I had to guess, I would say that either the TiVo itself is screwed up, or the HDD is faulty, but the HDD seems to work (only TiVo mounted partitions don't work). Any one have any thoughts or ideas? I don't mind starting the copy over again from scratch, but I don't want this to keep happening.
Thanks,
dmp
I have a Seriens 1 DTiVo, DSR6000. I had upgraded the HDD so that it had a 60GB and a 40GB. 4 MFS pairs between the two HDDs. I felt that I detected that one of the HDDs was going bad, so I bought a new 250 GB Maxtor drive, and copied everything over. Because of the 16 partition A Drive limit, I had to combine some partitions. I did this with pdisk, turning the 8 total into 4 total. I then used MFSTools to expand and add one more pair. I then used the PVRUpgrade boot CD and copykern to put on a 3.1.0 kernel that supports LBA48. At that point everything seemed to be going well, and the unit worked for several days. Last time I remember using it was Sunday night (72 hours ago) to record/watch the Superbowl.
Tonight I turned on the TV and saw the following message on screen, "Can't boot kernel" I had never seen this before, so I tried to power cycle, same thing. I took the drive out, and connected it to the computer again. Tried to rerun copykern, and it kept complaining about unknown boot sector signature. it also didn't mount /dev/hda on /cdrom appropriately. I Tried to mount /dev/hdX9 to check out the logs, and the file system didn't like that. It reported something like "Value too large..." Finally, I decided to reboot and dd /dev/hdX2, /dev/hdX3, /dev/hdX4, /dev/hdX5, /dev/hdX6, and /dev/hdX7 from the old A-Drive to the new one. I then had to manually mount /dev/hda as /cdrom again, re-ran copykern, and that time it worked correctly. I put the drive back in the TiVo, turned it on, and it booted fine, but now it is running through GSOD/reboot over and over again. I figure I'll give it an hour in case it's actually doing something, and then check the logs.
Any one know what's going on? Ever hear of this before? If I had to guess, I would say that either the TiVo itself is screwed up, or the HDD is faulty, but the HDD seems to work (only TiVo mounted partitions don't work). Any one have any thoughts or ideas? I don't mind starting the copy over again from scratch, but I don't want this to keep happening.
Thanks,
dmp