GSOD with new hard drive.

[Thrantor]

My system decided it was time to have a nice GSOD reboot repeat situation. It would get through the "Powering on... Almost there... Green Screen... Reboot" cycle. I figured this was a faulty harddrive. So I grabbed a new WD250gb to move things to.

I have tried multiple options.

mfsbackup -f 9999 -sp - /dev/hda /dev/hdb | mfsrestore -s 127 -r 4 -xzpi - /dev/hdd
(This one let me copy the data to the drive)
mfsbackup -Tao - /dev/hda /dev/hdb | mfsrestore -s 127 -r 4 -xzpi - /dev/hdd
(that one wouldn't let me copy the drives)
mfsbackup -Tao - /dev/hda /dev/hdb | mfsrestore -s 127 -r 4 -zpi - /dev/hdd
(This one let me copy both drives to the new drive with full data but I lost the extra space)

However, The first and the last option both produce the same problem as I originally saw. GSOD lather rinse repeat. I've tested the new drive in my windows box and nothing seems to be wrong with it. I've swapped the cables. I've reseated everything. I'm pretty much at a loss for ideas right now. I don't want to have to buy a new tivo, nor would I really want to try to find another AT&TIVO to copy the shows to.

Suggestions?

[xnevergiveinx]

probably the reason that you are seeing the gsod on the new drive is that you are copying over corrupted infomation from the bad drive to the new one.
you need a virgin image to copy onto the new drive.
unless someone can provide that, you could buy instantcake for the drive

[Klydeman]

Hello. I'm kind of new at this but something in your commands doesn't look right. It might work with the existing image. GSOD is mfs_fix or equivalent to scandisk. If it's run for a long time, it probably doesn't have large enough swap file size.

Your trying to go from a dual drive to a single, & smaller, A-drive? What is the size of the original 2 drive set?

If you can swing it, back up the original 2-drive TIVO. Then mfsrestore to the single drive. Check here for exact details.

http://www.newreleasesvideo.com/hinsdale-how-to/

But probably (2) drive Series 2:
mfsbackup -f 9999 -6so /mnt/dos/tivo.bak /dev/hdX /dev/hdY (where X=TIVO A, Y=TIVO B)
Then
mfsrestore -s 127 -bzpi /mnt/dos/tivo.bak /dev/hdX (X=New TIVO A)

Need to pay attention to original drive sizes, as this will restore to original size or Larger HD.

If you need to expand. Then:
mfsadd -x /dev/hdX

But really, check for your exact situation on the Hinsdale guide.

[Thrantor]

Is there a way to do the equivilant of a scandisk or a fdisk on the drive when it's hooked up to a seperate system. If we know the partition information and can mount the filesystems we should be able to repair them from another linux machine.

Thoughts?

[Klydeman]

Is there a way to do the equivilant of a scandisk or a fdisk on the drive when it's hooked up to a seperate system. If we know the partition information and can mount the filesystems we should be able to repair them from another linux machine.

Thoughts?

Someone else may need to comment on this. I do know you can run surface scan using spinrite or something equivalent. But the linux based OS has a certain partition structure (so NO windows based dos utilities which may spell disaster i.e. fdisk or scandisk). Maybe one of the MFS Tools CD has something, but I don't know.

If your really in a pickle with the existing image, you can d/l one...mfs restore to your WD250, expand and away you go.
http://www.ptvupgrade.com/products/instantcake/
(which what was being eluded to in the first reply)

But I think if you got the right commands, it probably can be restored.

[Klydeman]

With your previous 2 drive setup you can try this....

To Preserver Recordings....
mfsbackup -Tao - /dev/hda /dev/hdb | mfsrestore -s 127 -xzpi - /dev/hdd

[Thrantor]

I'm suspecting now that I'm end up copying over the corrupted data from the previous drive. I'm going to try messing with the copies for awhile longer and see what I can find.

But I'm wondering if there isn't a way to use a linux filesystem tool to correct the files systems... something like fsck?

[Klydeman]

If the above didn't work, I'm a little beyond my ability to help...but you might try dd_rescue. But somebody else might chime in.

http://www.garloff.de/kurt/linux/ddrescue/


Here was a thread, sounds like a similiar problem you have, used dd_rescue to fix

http://www.tivocommunity.com/tivo-vb/archive/index.php/t-170147.html


I've just been poking around. On this dd_rescue...in both cases that I read, after doing the dd_rescue, initially the TIVO will GSOD but msfix runs, and after several hours, there TIVO recovers.