S2 SA Restore to Seagate 160gb Problem

[nilknarf]

Used Sleepers ISO to backup my original 80gb drive (Sony SVR-3000; 4.0.1b-02). Backed up to a fat32 2.3GB drive.

When I tried to restore the image to a new Seagate 160gb drive (limited to 137gb before I began), I received quite a few inode errors saying something to the effect of Inode error at xxxxx backup corrupt, giving up, etc. Although the process ends with "Success".

Put in Tivo to test and get GSOD, followed by reboot loop. Ok, restore obviously corrupt.

Soooo....Tried the whole process again using MFStools. Same inode errors. This time the tivo booted up ok, but there were 3 problems. #1 the size of my new drive is still showing as 88 hours, even though this is my 137gb Seagate. #2 the Tivo would reboot every five minutes or so #3 The picture was glitching where I would lose fragments of the screen every 20 seconds or so. Ok, this restore was obviously corrupt also.

Now I try the whole process again using a new fat32 Backup drive. Same Inode errors during restore.

During the backup process there are no errors, but every time I try to restore the image to the Seagate 160gb, I get the Inode corrupt backup errors.

I ran diagnostics on the Seagate 160gb and it tested fine.

So I've eliminated: A. The backup drive B. The backup ISO C. The new drive

I'm running this stuff on a PIII dual 933mhz with 512mb ram.


I'm stuck.........any Ideas?

[nilknarf]

Well Nilknarf, this is just a guess, but perhaps you should have told us that you purchased this Tivo used. Maybe there's a chance that the previous owner screwed around with your original drive and that's what's causing the problems. Hmm...anyone think this is likely or should nilknarf look elsewhere?

[nilknarf]

Well all I know is that the previous owner is an IT guy and he had the stock network and HMO settings enabled. So it's possible he screwed around with it. Everything works perfectly on the original drive however.

[compwiz312]

First off, the whole third person thing is freaky...on a more serious note:

Inode errors usually denote a failing/failed hard drive, so I would recommend replacing the drive and begging for a fresh image unless you have a backup.

Justin

[nilknarf]

I finally figured it out. After trying everything else, new backup drive, new restore drive, different ISO's, mfsrestore, etc...I finally got it! It was my computer. I switched to my other PC and the backup worked perfectly the first time. :)

PS: The computer that wouldn't work was a Gateway 6400 - Modified server, PIII, dual 933 mhz processors.

[acharuss]

I finally figured it out. After trying everything else, new backup drive, new restore drive, different ISO's, mfsrestore, etc...I finally got it! It was my computer. I switched to my other PC and the backup worked perfectly the first time. :)

PS: The computer that wouldn't work was a Gateway 6400 - Modified server, PIII, dual 933 mhz processors.


It's not just your Gateway that's having this issue. It would seem any computer with not enough resources will cause mfstools to fail.

I was using a PIII 450 Mhz with 320 MB of memory, which would normally be just fine for a command line Linux environment. Even doing the backup I would get loads of errors. After reading your post I loaded into a P4 3 Ghz with 512 mb and everything completed successfully.

So a word to the wise, MFSTools requires a bit of horsepower inside the case.

[Jamie]

So a word to the wise, MFSTools requires a bit of horsepower inside the case.I have a 400mhz Celeron on an i810 motherboard with 32mb of memory I use for tivo imaging. Works just fine. mfstools has very modust resource needs.