GSOD - New Software????

[jgkurz]

Hi Folks,

I experienced my first known Green Screen of Death today. My HR20-250 is unhacked and is running 6.2e. The only modification I've done is to add a 500GB Seagate DB35 drive. My WD 250GB was failing but I was able to copy it successfully using DD_RESCUE and expand using MFS Tools. The new drive has worked flawlessly for a couple weeks. Speed was noticeably improved and all phone updates were finishing successfully.

I am waiting for the GSOD to complete but I find it hard to believe the new Seagate drive has failed already. I know it's possible but I'm wondering if there was a software update that came out recently that could have caused the failure. Any thoughts?

Fortunately I still have my old 250GB drive with the 6.2e image.

[fjwagner]

Hr20-250?

[jgkurz]

Hr20-250?

Wow...how'd that happen. I meant HR10-250. :o

[incog-neato]

Is it possible you copied some corrupt data from the "failing" drive which caused the problem? A failing drive can corrupt data which remains corrupt no matter where you move it to. It may have just bit you after 2 weeks.

Hi Folks,

I experienced my first known Green Screen of Death today. My HR20-250 is unhacked and is running 6.2e. The only modification I've done is to add a 500GB Seagate DB35 drive. My WD 250GB was failing but I was able to copy it successfully using DD_RESCUE and expand using MFS Tools. The new drive has worked flawlessly for a couple weeks. Speed was noticeably improved and all phone updates were finishing successfully.

I am waiting for the GSOD to complete but I find it hard to believe the new Seagate drive has failed already. I know it's possible but I'm wondering if there was a software update that came out recently that could have caused the failure. Any thoughts?

Fortunately I still have my old 250GB drive with the 6.2e image.

[jgkurz]

Is it possible you copied some corrupt data from the "failing" drive which caused the problem? A failing drive can corrupt data which remains corrupt no matter where you move it to. It may have just bit you after 2 weeks.

I'm not an HR10-250 expert but that does seem like the most plausible answer. I did notice that the GSOD happened around the same time an indexing had started.

The GSOD is now gone and my Tivo is working normally, at least as much as I can tell. I also took the drive out and tested it, and as suspected, it had no failures.

Thank you for your input.