techead
Honorary Master
Thanks for the reference. Im in touch with him, and he is dropping his drive off tonight!
Cheers
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How do you normally pay for purchases in stores?
Seagate 7200.11 BSY (not detected in BIOS) error solution
- Thread starter vigilantis
- Start date
Thanks for the reference. Im in touch with him, and he is dropping his drive off tonight!
Cheers
The_Unbeliever
Honorary Master
Thanks for the reference. Im in touch with him, and he is dropping his drive off tonight!
Cheers
*shameless bump*
was it a success?
techead
Honorary Master
what do you think?
PHOBOS
Well-Known Member
Just googled 7200.11 firmware issue and found this thread. 
I have a 1TB Seagate ST31000340AS that was working fine.
One morning a shut down the PC and when I got home at night and switched on the PC the boot up got stuck on the BIOS trying to detect the drive, about a minute later it skipped the drive and booted into Window.
I was one a few data drives.
Once in Windows the drive was simply missing.
The drive sounds like it powers up fine and there's no weird noises. So I don't think it's died and there were no warnings.
Anyone able to help me out as I want my 1TB of data but don't have R12k?
I have a 1TB Seagate ST31000340AS that was working fine.
One morning a shut down the PC and when I got home at night and switched on the PC the boot up got stuck on the BIOS trying to detect the drive, about a minute later it skipped the drive and booted into Window.
I was one a few data drives.
Once in Windows the drive was simply missing.
The drive sounds like it powers up fine and there's no weird noises. So I don't think it's died and there were no warnings.
Anyone able to help me out as I want my 1TB of data but don't have R12k?
Hey
Sounds like the BSY error...
If it is... then there is a solution that costs about as much as a Nokia Data Cable and a steady nerve...
Link..
I have some more links somewhere... will try and find them... but google youtube for a Seagate 7200.11 BSY fix and you will find some videos about this and how to fix it.
I myself am trying to find a Nokia CA-42 cable to butcher...
Sounds like the BSY error...
If it is... then there is a solution that costs about as much as a Nokia Data Cable and a steady nerve...
Link..
I have some more links somewhere... will try and find them... but google youtube for a Seagate 7200.11 BSY fix and you will find some videos about this and how to fix it.
I myself am trying to find a Nokia CA-42 cable to butcher...
PHOBOS
Well-Known Member
I take it Seagate SA can't help?
They not having a recall and fixing it like Toyota and its stuck accelerator pedal.
They not having a recall and fixing it like Toyota and its stuck accelerator pedal.
Nope... there actually is NO Seagate SA... all you will get is a replacement drive... no data recovery... that you will be charged for. Only in the USA did Seagate offer free data recovery because of a class action lawsuit threat.
Seagate will offer you data recovery services... for a fee of course.
If you read up and follow the youtube vids, you will see it is actually very quick and simple to remedy. The hardest part is finding a cable! I cannot understand why these okes who recover data from BSY'd Seagate drives want to charge 1 handling fee, then a recovery fee and then a fee per GB of "recovered" data! Geeeez. There is no need to recovery anything... you just have to "wake" the drive up and interrupt its busy firmware wobbly... once done, update the firmware and all is OK.
PHOBOS
Well-Known Member
Well that Sux bum.
Watched http://www.youtube.com/watch?v=29FztWJVxbM and well it's just a case of getting the right stuff (cable and torx driver).
Hopefully I can find one where the USB plugs open really easily and the wires are labelled.
The commands look wack. But I guess if after all that's done and then the drive just works fine there after then sweet.
I don't know what firmware is on the drive right now though.
Does it matter?
Watched http://www.youtube.com/watch?v=29FztWJVxbM and well it's just a case of getting the right stuff (cable and torx driver).
Hopefully I can find one where the USB plugs open really easily and the wires are labelled.
The commands look wack. But I guess if after all that's done and then the drive just works fine there after then sweet.
I don't know what firmware is on the drive right now though.
Does it matter?
Hi Phobos
Yes... the commands you need to type in HAVE to be done 100% as outlined... if you get a comma wrong, or mis-type, then there is a chance you might brick your drive - it has been told and warned on a number of forums to get those commands perfectly correct.
The firmware of the drive should be listed on the actual disk - look under the Seagate logo on the sticker on the drive, you will see its serial no, model... and just above the date code you will see the firmware that it was shipped with.
The affected firmware is also a bit of a grey-area. Seagate had a lot of drives listed as unaffected... but these drives WERE affected, and some of them actually EVENTUALLY made it onto the official Seagate list more than A YEAR LATER! I had such a drive... my family had 2 of these... were told it is not the BSY error as the drive serial numbers and firmware numbers were not listed as affected.... and then, a year later suddenly appeared on the Seagate site.
I was also told a lot of bullsh*t about data recovery and having to actually "scan and recover" the data - which costs a lot as it has to be monitored etc... then found the BSY links and vids on youtube and saw just how recovery intensive it is. Attach cable, insert card, power up, wait, remove card, wait, input code, wait, power down, remove cable, tighten screws, power up... and all the data is there as it always has been... no actual recovery required. 3 minutes of "work" that they (the cheapest) wanted to charge R500 handling fee, R1000 recovery fee and then a charge per 100MB recovered data. * grrrrrrrrrr *
This is assuming that your drive is stuck in the BSY error loop, but the symptoms you mentioned are classic BSY error... working fine one moment... nothing wrong and no errors, then, without warning - poof. Not seen in BIOS, gone from windows and the drive makes all the normal sounds...
Yes... the commands you need to type in HAVE to be done 100% as outlined... if you get a comma wrong, or mis-type, then there is a chance you might brick your drive - it has been told and warned on a number of forums to get those commands perfectly correct.
The firmware of the drive should be listed on the actual disk - look under the Seagate logo on the sticker on the drive, you will see its serial no, model... and just above the date code you will see the firmware that it was shipped with.
The affected firmware is also a bit of a grey-area. Seagate had a lot of drives listed as unaffected... but these drives WERE affected, and some of them actually EVENTUALLY made it onto the official Seagate list more than A YEAR LATER! I had such a drive... my family had 2 of these... were told it is not the BSY error as the drive serial numbers and firmware numbers were not listed as affected.... and then, a year later suddenly appeared on the Seagate site.
I was also told a lot of bullsh*t about data recovery and having to actually "scan and recover" the data - which costs a lot as it has to be monitored etc... then found the BSY links and vids on youtube and saw just how recovery intensive it is. Attach cable, insert card, power up, wait, remove card, wait, input code, wait, power down, remove cable, tighten screws, power up... and all the data is there as it always has been... no actual recovery required. 3 minutes of "work" that they (the cheapest) wanted to charge R500 handling fee, R1000 recovery fee and then a charge per 100MB recovered data. * grrrrrrrrrr *
This is assuming that your drive is stuck in the BSY error loop, but the symptoms you mentioned are classic BSY error... working fine one moment... nothing wrong and no errors, then, without warning - poof. Not seen in BIOS, gone from windows and the drive makes all the normal sounds...
Oh... one more thing...
I initially struggled to find a cable that works... I bought an original Nokia CA-42 cable... R355... cut it up, it did not work... apparently the chipset was "wrong"... I tried a CA-53 Nokia cable, as was suggested, that too did not work... another R200 gone... I found a generic cable at a little cell shop in the Brightwater Commons in Randburg, R120 and it worked... alas gave this to another needy soul when I was done with it.
Am in Cape Town now, and need another cable - these 7200.11 drives are still turning up BSY'd - tried an Incredible Connection generic... no go. These Nokia CA-42 cables are in short supply I think because of their Seagate saving uses... also... the prices have shot up for them... I was quoted R576 for an original Nokia cable !!
I initially struggled to find a cable that works... I bought an original Nokia CA-42 cable... R355... cut it up, it did not work... apparently the chipset was "wrong"... I tried a CA-53 Nokia cable, as was suggested, that too did not work... another R200 gone... I found a generic cable at a little cell shop in the Brightwater Commons in Randburg, R120 and it worked... alas gave this to another needy soul when I was done with it.
Am in Cape Town now, and need another cable - these 7200.11 drives are still turning up BSY'd - tried an Incredible Connection generic... no go. These Nokia CA-42 cables are in short supply I think because of their Seagate saving uses... also... the prices have shot up for them... I was quoted R576 for an original Nokia cable !!
PHOBOS
Well-Known Member
Hi
Thanks for the replies.
Will look around for cable and torx drive.
I hope Seagate doesn't have any other drives that are ticking time bombs. *Hint LP's.*
Thanks for the replies.
Will look around for cable and torx drive.
I hope Seagate doesn't have any other drives that are ticking time bombs. *Hint LP's.*
buffalobill
Senior Member
It looks like Seagate drives have a major quality problem or at least that's been my recent experience. A year-and-a-half ago I bought a Freeagent 500Gb and an internal 500gb Barracuda which failed OTB and was replaced. This same drive failed today. In December I bought two 500GBs and a 1Tb. The 1Tb failed OTB. I'll pick up the replacement this week. The question is: Are the local suppliers being dumped with crap stock or is this a general failing with Seagate's quality control? Either way, I'm not going to be buying Seagate any more. What worries me is I have 500Gbs on two of my C: drives here at home.
Now, I would like to recover the data on the failed 500Gb. I guess I should have read the warning signs. It spun through several CHKDSKs, would work fine in Windows and then stop. Now, BIOS reports it can see it, but a failure to read and 0Gb. No knocking or sounds inside that I can hear or feel. I'm anyway going to be putting in an i5 board and processor over the next weekend and will see what I can do. I might call for data recovery help here in Joeys. Who can assist? The drive in question is not a main drive, but it contains data I would prefer not to have to replace.
Now, I would like to recover the data on the failed 500Gb. I guess I should have read the warning signs. It spun through several CHKDSKs, would work fine in Windows and then stop. Now, BIOS reports it can see it, but a failure to read and 0Gb. No knocking or sounds inside that I can hear or feel. I'm anyway going to be putting in an i5 board and processor over the next weekend and will see what I can do. I might call for data recovery help here in Joeys. Who can assist? The drive in question is not a main drive, but it contains data I would prefer not to have to replace.
Image drive to a file with GNU ddrescue, work on the image file to recover whatever data you need.
Unfortunately the 0GB problem is not the same as the BSY bug and requires a different fix. Running the BSY fix on a drive with a 0GB problem isn't a good idea. Best to send it to a pro to get it back in working order.
buffalobill
Senior Member
Sorry, I maybe didn't make myself clear. The drive now fails at the BIOS level with "Master hard disc error" - I guess I might have formatted it in the past as a bootable drive (I dunno if that makes any difference). A few hours before failing, CHKDSK /f reported something about empty sectors being marked containing data (can't remember the exact message). It seems bad to me. Once I have the new i5 system up and running with a spare drive, I'll try the freezing route, or is there any reason why I shouldn't?
You should definitely stay away from freezing it. All it will do is condense the water vapour inside when you take it out and ruin the platters, ie your data. Freezing is a highly risky DIY attempt aimed only at the 'stiction' problem where heads become stuck to the platter.
I could help you but I am based in CT. If you are serious about getting your data back you will need to pay for professional help.
sposton
Member
I just did this fix for a chaps' 500G HD in the office here...Had the things lying around on the bench...Quite an easy process.
If anyone wants help with this problem and can get to Centurion, send me a pm...I won't ask for much!!
Word to note though, after I fixed the drive, we tried it in a spare PC in the office and windows didn't pick it up. We then put it in another PC and windows recognised it, installed the drivers and all was well.
If anyone wants help with this problem and can get to Centurion, send me a pm...I won't ask for much!!
Word to note though, after I fixed the drive, we tried it in a spare PC in the office and windows didn't pick it up. We then put it in another PC and windows recognised it, installed the drivers and all was well.
Lol, drivers for a hard drive?