havanahjoe
04-08-2006, 08:14 PM
So my WD 120 GB drive is dying for the 3rd time and it is now out of warranty which meant I had to buy a new drive. I got a Seagate Barracuda 160 GB and decided to transfer the info from the WD to the Seagate. Not really interested in the recordings, but would like to keep the hacks I already have.
First problem. The WD drive is already expanded, so I can't expand it to 160 and I would like to take advantage of the LBA48 support in the new 6.2.
I upgraded my 4.X monte to 6.2 unmonte'd a month ago (which is when the hard drive problems made the TiVo stutter with video once in a while). I tried doing a mfsbackup/mfsrestore to copy the whole thing (losing the extra 20 gb) but since the WD is dying, it was going to take about 3 days. I scratched that and decided to backup without the recordings.
The backup/restore (mfsbackup/mfsrestore -xzp) went well using an LBA48 aware boot disc. I put the Seagate drive in the TiVo and let it boot. The first time I saw it go up to the directv wait a few minutes screen and then reboot, only to go to the GSOD the second time it came up.
My PC hadn't boot up yet for me to see the TiVo's serial output, I could barely see that it was trying to restore the MFS system.
Redid the backup/restore and paid attention to what was going on. The TiVo boots fine but it determines that the MFS is damaged so it decides to rebuild it completely! I let it run for as many hours as it needed, only to find out that it was unable to do it.
Right now I just decided to start with the 62small.mfs image and rehack the thing since I don't have that many season passes or stuff I want to save and I'm losing more time by trying to figure this out.
I'm posting this just because I'm curious about why this is failing. I know that the hard drive is bad, but I'm pretty sure that if I did it with another 120 gb it would work fine. What I'm wondering is if for some reason the kernel I'm using in my WD at the moment can't see the extra space and is freaking out because of that. I'm using a hacked 3.1 (I think this is the version, it's the latest one) kernel to run without a monte.
I appreciate any comments. At the moment I was able to get the new drive running with the virgin 62small.mfs image and now I'm off to put the hacked kernel and the rest of the mods on it.
I'll try and use that old season pass backup script that I've used in the past to see if I can backup/restore that info.
First problem. The WD drive is already expanded, so I can't expand it to 160 and I would like to take advantage of the LBA48 support in the new 6.2.
I upgraded my 4.X monte to 6.2 unmonte'd a month ago (which is when the hard drive problems made the TiVo stutter with video once in a while). I tried doing a mfsbackup/mfsrestore to copy the whole thing (losing the extra 20 gb) but since the WD is dying, it was going to take about 3 days. I scratched that and decided to backup without the recordings.
The backup/restore (mfsbackup/mfsrestore -xzp) went well using an LBA48 aware boot disc. I put the Seagate drive in the TiVo and let it boot. The first time I saw it go up to the directv wait a few minutes screen and then reboot, only to go to the GSOD the second time it came up.
My PC hadn't boot up yet for me to see the TiVo's serial output, I could barely see that it was trying to restore the MFS system.
Redid the backup/restore and paid attention to what was going on. The TiVo boots fine but it determines that the MFS is damaged so it decides to rebuild it completely! I let it run for as many hours as it needed, only to find out that it was unable to do it.
Right now I just decided to start with the 62small.mfs image and rehack the thing since I don't have that many season passes or stuff I want to save and I'm losing more time by trying to figure this out.
I'm posting this just because I'm curious about why this is failing. I know that the hard drive is bad, but I'm pretty sure that if I did it with another 120 gb it would work fine. What I'm wondering is if for some reason the kernel I'm using in my WD at the moment can't see the extra space and is freaking out because of that. I'm using a hacked 3.1 (I think this is the version, it's the latest one) kernel to run without a monte.
I appreciate any comments. At the moment I was able to get the new drive running with the virgin 62small.mfs image and now I'm off to put the hacked kernel and the rest of the mods on it.
I'll try and use that old season pass backup script that I've used in the past to see if I can backup/restore that info.