We have a couple old Series 1 Tivos that I've done multiple disk upgrades/replacements on over the years. One of the disks just died so I'm trying to image up a new one. I am trying to avoid the hassle of digging out the old Linux PC as I have in the past so I'm trying something new. I'm trying to use WinMfs as defined here: http://www.mfslive.org/winmfs/ Using the image as provided here: http://www.tivocommunity.com/tivo-vb/showthread.php?p=8919428#post8919428 I've now done this with three different disk drives each with similar (bad) results: 80G - imaged fine, boots, did guided setup, data downloads, but part way through indexing it crashes. I went around this loop several times. For "fun" I tried to do a KickStart 57 (disk check) and now every time it gets to the GSoD it reboots - round and round. This disk is dead until I re-image it. 80G (a different one) - imaged find, will not boot (stays on the initial Tivo splash-screen forever). 200G - imaged fine, boots, did guided setup, data downloads, but part way through indexing it crashes (just like the first 80). The second time through the loop it rebooted to the GSoD and is now stuck in that loop. These disks all came out of working (retired) PCs and passed a disk check utility before I imaged them. So I don't believe I have three bad disks (I don't think any of them are bad). I am left with the conclusion that either the image is bad, or the utility is bad. Or perhaps there some undocumented magic I'm failing to do, but if there was I wouldn't think it would work at all. So, does anyone have any idea what might be going wrong here? I'm in the process now of trying to get one of my original/small disks to update from software version 2.5 to 3.0 so I can try capturing and using that image. That might confirm/deny that the above image is bad. All thoughts, idea, suggestions welcome. Thanks.