Odd mfsrestore issue

[AlphaWolf]

I have been having this problem lately where every time I do an MFS restore, everything works fine until after the unit is powered down and up a few times, and then a GSOD shows up. The tivo eventually reboots again and seems to recover, however it gets permanently stuck on the "almost there" screen with this error: InitializeProgramOrDie failed: 0x30001.

That indicates to me that for some reason the restores I am doing aren't exactly kosher, and thus when the tivo eventually sees the problem and runs fsfix, it possibly nukes the swsystem from mfs.

Has anybody ever run into this before? I have tried changing the cables, drives, restore image, etc, nothing seems to resolve it. I am wondering if theres some other way to ensure the integrity of the fs after a restore.

[Lost Dog]

I have been having this problem lately where every time I do an MFS restore, everything works fine until after the unit is powered down and up a few times, and then a GSOD shows up. The tivo eventually reboots again and seems to recover, however it gets permanently stuck on the "almost there" screen with this error: InitializeProgramOrDie failed: 0x30001.

That indicates to me that for some reason the restores I am doing aren't exactly kosher, and thus when the tivo eventually sees the problem and runs fsfix, it possibly nukes the swsystem from mfs.

Has anybody ever run into this before? I have tried changing the cables, drives, restore image, etc, nothing seems to resolve it. I am wondering if theres some other way to ensure the integrity of the fs after a restore.

Damn newbies. Have you even *made* a serial cable yet? Did you *search*?!?! If you want a guide, write it yourself.

Heh heh... Sorry AW. I've seen so many "First Posts" recently my fingers twitch a bit too much...

Are these your own images or emuled ones? I've ran in to several that I snagged of emule that caused similar issues. Do you see the error on serial bash or from digging in the log files in /hda9? I wonder that program it's trying to initialize before it dies (I guess InitializeProgramOrDie is an accurate message...).

Are you using your custom kernel? Could there be some interaction there?

[AlphaWolf]

Well, I am 100% certain that the image is fine. It's the same image that I used on my other tivo about 4 months ago which is still working fine, and the md5sum is the same then as it is now so I know it hasn't been corrupted since then. That means its using the same kernel and everything as well.

[Lost Dog]

Well, I am 100% certain that the image is fine. It's the same image that I used on my other tivo about 4 months ago which is still working fine, and the md5sum is the same then as it is now so I know it hasn't been corrupted since then. That means its using the same kernel and everything as well.

Odd. Same swapfile size?

You've switched out all the hardware except for the actual TiVo it sounds like. I wonder if your power supply is on it's last leg and causing issues.

[captain_video]

Is this a series 1 or series 2 image? I've found that the series 1 images are more susceptible to GSODs and that they will occur if you even look at a S1 DTivo cross-eyed. I had a DSR6000 that contained some old recordings that I wanted to pull off but the unit hadn't been powered up in over a year. I plugged it in a got an instant GSOD whereas it had been running fine with no issues prior to being put in mothballs for that period. Once the GSOD cleared I had no further problems. I have yet to see a GSOD on a series 2 DTivo.

[AlphaWolf]

Well, this is two different tivos that this is happening to, both of them S2.

[crazyrat]

I'm assuming you did, but would you mind posting what the eventual solution to this was? I believe I'm having the same problems with my HDVR2. I've restored an image about 30 times which initially worked on a few systems but now crashes with the same issue.

The drive is fine (verified with Seatools) and the cable has been replaced with a couple known good ones.

[11/11/05] Looks like my problem is a dying drive. The drive verifies with Seatools and I can format the entire drive under Windows. When the drive is being accessed though, occasionally it will make a chirping noise and access will stop for a second or two. It will then continue. I believe this was happening during the restore process and causing mfstools to barf during the mfs expansion. After about 20 tries, I finally got the image to restore correctly without this error but I think the drive is going to die soon.