Last week my Premiere XL crashed with the GSOD. Based on what I read here and my tests I'm thinking of trying ggieseke's DvrBARS process on it but not sure how to do what I'm thinking or if it is even doable. And would like any insight into what I'm seeing.
First thing, I pulled the HDD and ran the WD short and Extended diags on it. It passed with flying colors. I then used ddrescue to clone the drive to another WD identical sized drive so I could experiment. Ddrescue reported no errors in the process. This seems to imply that the drive isn't actually failing but that the OS has gotten corrupted in some way.
I tried booting from the cloned drive which encountered the GSOD (not surprising). I then tried to run various Kickstart codes. I could launch 54 HD test and run the tests. But could not start 51, 52 or 56 in an attempt to restore a potentially corrupted OS. I then ran KS 57, MFS check. After a while, the XL became stuck in a Welcome, Almost there, GSOD loop. Now I can't get to the KS codes on this drive. Strange.
I went and bought the Weaknees upgrade drive of the same size. I ran guided setup and the TiVo is alive. I cloned this onto the previously cloned drive and it also works. So now I have a working copy.
I see indications in the DvrBARS instructions that I may be able to copy certain partitions and get my original, or the clone working with my recordings. But I can't see any partition structure with my Ubuntu Live boot environment.
Given all that I have the follwoing questions:
1. What could the MFS check have done to corrupt it further?
2. Will the DvrBARS utility show the partitions?
3. I've also seen it stated that you should not boot Windowws with a TiVo drive attached because it will corrupt the drive. Is that no longer the case since DvrBARS is running under Windows?
4. Am I off in the weeds or is this possible?
Thanks for your help.
First thing, I pulled the HDD and ran the WD short and Extended diags on it. It passed with flying colors. I then used ddrescue to clone the drive to another WD identical sized drive so I could experiment. Ddrescue reported no errors in the process. This seems to imply that the drive isn't actually failing but that the OS has gotten corrupted in some way.
I tried booting from the cloned drive which encountered the GSOD (not surprising). I then tried to run various Kickstart codes. I could launch 54 HD test and run the tests. But could not start 51, 52 or 56 in an attempt to restore a potentially corrupted OS. I then ran KS 57, MFS check. After a while, the XL became stuck in a Welcome, Almost there, GSOD loop. Now I can't get to the KS codes on this drive. Strange.
I went and bought the Weaknees upgrade drive of the same size. I ran guided setup and the TiVo is alive. I cloned this onto the previously cloned drive and it also works. So now I have a working copy.
I see indications in the DvrBARS instructions that I may be able to copy certain partitions and get my original, or the clone working with my recordings. But I can't see any partition structure with my Ubuntu Live boot environment.
Given all that I have the follwoing questions:
1. What could the MFS check have done to corrupt it further?
2. Will the DvrBARS utility show the partitions?
3. I've also seen it stated that you should not boot Windowws with a TiVo drive attached because it will corrupt the drive. Is that no longer the case since DvrBARS is running under Windows?
4. Am I off in the weeds or is this possible?
Thanks for your help.
Aucun commentaire:
Enregistrer un commentaire