The Solution for Seagate 7200.11 HDDs

[seg77]

Test lasted for 30 min, then failed, the computer suddenly rebooted I do not know why, I had to turn it off, then Windows reported the error blue screen.
Right now i'm using this drive,no problems.
I will not attempt to do anything with the hard drive!

Thank's!

[jaclaz]

Test lasted for 30 min, then failed, the computer suddenly rebooted I do not know why, I had to turn it off, then Windows reported the error blue screen.

Right now i'm using this drive,no problems.

I will not attempt to do anything with the hard drive!

Thank's!

Yep , but all the "combined" reports (including the failure to perform a "Long" test) lead to believe that the disk is having issues, I personally would not EVEN THINK of using it as "System" drive, further use is suggested possibly ONLY as a secondary or tertiary backup.

jaclaz

[seg77]

Test lasted for 30 min, then failed, the computer suddenly rebooted I do not know why, I had to turn it off, then Windows reported the error blue screen.

Right now i'm using this drive,no problems.

I will not attempt to do anything with the hard drive!

Thank's!

Yep , but all the "combined" reports (including the failure to perform a "Long" test) lead to believe that the disk is having issues, I personally would not EVEN THINK of using it as "System" drive, further use is suggested possibly ONLY as a secondary or tertiary backup.

jaclaz

Yes,certainly the problem to the hard disk.

I dont use it anymore,now it's on auction,I hope to get rid of that drive!

Thank's again.

[bphlpt]

Yes,certainly the problem to the hard disk.

I dont use it anymore,now it's on auction,I hope to get rid of that drive!

I hope you are honest and tell whoever buys it that it has problems?

Cheers and Regards

[seg77]

Yes,certainly the problem to the hard disk.

I dont use it anymore,now it's on auction,I hope to get rid of that drive!

I hope you are honest and tell whoever buys it that it has problems?

Cheers and Regards

Yes I mentioned what the problem is,if someone does buy!

All the best!

[duckevo]

I did managed to put the code in hyper terminal till F3 2>U which it prompted error in spinning up...

I tried to redo the whole process again but no prompt in hyper terminal when I press ctrl+z

Any advise to get it back??

[Elpigo]

Did the BSY method but I adapted it for my 7200.12 (inverted the m0 and the N1 commands) and it worked fine after a couple of tries. But after, what should I do? I made a copies of the main files on the drive but can the drive still be used afterward? I'll also do the firmware update as offered on Seagate site for my drive but will it be stable after that for everyday use or should I consider using it as a dead weight for my CD collection?

Thanks for any help

[jaclaz]

Did the BSY method but I adapted it for my 7200.12 (inverted the m0 and the N1 commands) and it worked fine after a couple of tries. But after, what should I do? I made a copies of the main files on the drive but can the drive still be used afterward? I'll also do the firmware update as offered on Seagate site for my drive but will it be stable after that for everyday use or should I consider using it as a dead weight for my CD collection?

Thanks for any help

Please do READ the read-me first, (that you should have read BEFORE):

http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/

Particularly points #1 and #5.

You posted on the wrong thread (as this is for 7200.11 ONLY as per point #1) and asked a question that has been answered in the read-me-first point #5 (and in reply to countless other posts by people that also did not manage to read the read-me-first FIRST).

jaclaz

[Elpigo]

Dear jaclaz,

 

Hum, seems to me you've been offended by my post. I'm sorry about that but it was made while still finding ways to retrieve the data from the HD that had suffered this bug. I know that this site is devoted to the 7200.11 only but the medecine also applies to his kin brother 7200.12. I used it and had success with it and I clearly mentionned it in my post. I have now read the read-me-first and smoke has cleared now.

 

My question still remains: what do you do next after the emergency operation? What about if the firmware update is made and the drive is reformated? I don't think Seagate produced this drive to be defective and as they must have sold thousands if not millions of it, some must have worked perfectly, more so when you think that the same kind of bug affected the 7200.12 after getting to the 7200.11. I'd like to understand what exactly has been done to the drive with the Gradius method, why should it work afterward? Then what about "Life after surgery" for these unfortunate drives? I don't intend to reuse it as my main drive, only for back-up purposes, but what would be the percentage of it going wrong again?

 

Thanks

[bphlpt]

Elpigo, if you are not dealing with a 7200.11 drive, PLEASE start a separate thread for ANY questions or discussions you might have.  It does not matter if "... the medecine also applies to his kin brother 7200.12. I used it and had success with it and I clearly mentionned it in my post.". Keeping questions and discussions about any drive besides a 7200.11 in separate threads will help others find those threads if they are in similar circumstances to you.

As to whether a "repaired" 7200.11 can be safely used, I believe it has been stated that just because the 7200.11 drive has been "repaired" does not mean that it has been "fixed" so that it will not fail again. If the same circumstances happen again that caused it to fail the first time, it is just as likely that it will fail again, even if the drive has had its firmware updated and it has been reformatted. There is no known "percentage of it going wrong again". So it is recommended that it only be used as a secondary or tertiary backup drive.

 

Cheers and Regards

[jaclaz]

This may help you take a decision, though the same theme is discussed also in the read-me-first (point 5, to which you were ALREADY pointed to) here it is more explicit:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-187#entry1067976

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-119#entry930329

http://www.msfn.org/board/topic/158397-invalid-partition-table-on-my-500gb-hdd/page-2#entry1012499

 

 

WHAT is the "difficult part" in those?

 

Let's try again.

 

Question: OK, I have revived a hard disk, <insert here any number of wordy descriptions and considerations>, can the drive be trusted afterwards? <optionally insert here any number of more logical reasons why you think you repaired the disk and how you think it should be blindly trusted, and how it is not possible that the manufacturer built a bad disk>

Answer: NO, nein, non, ...

More:

http://www.freelang.net/expressions/no.php

 

See if these further clears the matter:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=1004448

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-161?p=985254#entry985254

 

You have applied a "miracle" cure to an UNDIAGNOSED illness, there is NO way on Earth to know WHAT was the problem and HOW it was fixed (IF it was fixed) and how long this UNKNOWN CURE will prevent the SAME (or other) ILLNESS to affect again the disk.

 

I am not at all offended , I am exasperated (which is different) as the SAME, SAME, SAME question that has been answered IN ALL POSSIBLE WAYS is asked AGAIN, and AGAIN and AGAIN.

 

Your disk has been by sheer luck revived, if you managed to get the data you already were very lucky, if I were you I would not bet on it working properly again (which does not mean that it cannot happen, only that I would not bet on this).

 

More:

http://www.msfn.org/board/topic/158663-problem-during-firmware-update-drive-is-not-detected/?p=1014387

http://www.msfn.org/board/topic/158663-problem-during-firmware-update-drive-is-not-detected/#entry1014421

 

jaclaz

Edited May 6, 2014 by jaclaz

[nitro91]

does anyone know,

when i get to the point where it says take power out of the hdd and then put it back in then wait then type the m,0,,22, command. when i put the power back in, i cant type anything into hyperterminal?

[nitro91]

nevermind, i plugged it in and it showed the 0mb on BIOS, so i did 0 lba trick.

and its all working!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

how do i update firmware so it doesnt happen again, or should i just copy filess over and throw it out?

[jaclaz]

how do i update firmware so it doesnt happen again, or should i just copy filess over and throw it out?

Point #5 of the read-me-first:

http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/

further expanded here:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-121#entry932258

 

jaclaz

[nitro91]

yeh soz simple google search and i got it.

 

for some reason i first had the bsy error, then playing with the m0,22 thing i then plugged it onto my motherboard and it came up on the bios but as 0 mb so the 0lba error.

fixed that and its all fixed!

 

not sure why this only happened to me now since ive been using it since 2008, and this is my primary storage hard drive, from 08-11 it was my primary hard drive with OS on it.