Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Baracuda 7200.12 not detected in bios

March 5th, 2018, 1:02

Hello, I was hoping that maybe someone might could help me diagnose and possibly fix a problem I have with my Hard Drive.
I have a Seagate Barracuda 1TB ST31000528AS 9SL154-023 7200.12. So everything was fine last night, no problems. I wake up in the morning, turn on my pc, and basically bios was not detecting any hard drive. It just doesn't show up no matter what I do. Tried it in another pc, same problem. I hear nothing wrong with the hard drive at all, so I'm wondering if it may be a firmware issue like the 7200.11.

Any help would be appreciated. I would like to get some family photos and some of my digital artwork off of there. Any yes, I'm keeping back ups of my important files since this happened. I learned from my mistake. :D

Re: Baracuda 7200.12 not detected in bios

March 5th, 2018, 3:31

Hi

Since this is 7200.12, it doesn't suffer from the 7200.11 bug (but it has plenty of other ones). Do NOT attempt the 7200.11 fix you'll find on the internet, it can brick your drive.
Since drive does not produce clicking noise, most probably there is something wrong with the firmware. At this point it shouldn't be expensive if you consult a decent pro.

Alternatively, you can connect a TTL and post here terminal report. But DO NOT issue any commands.
If you value your data consult a pro.

Re: Baracuda 7200.12 not detected in bios

March 18th, 2018, 15:55

You must check NRG list via T>V40 . if there is no entry you can try bsy-fix

Re: Baracuda 7200.12 not detected in bios

March 18th, 2018, 16:13

northwind wrote:Hi

Since this is 7200.12, it doesn't suffer from the 7200.11 bug (but it has plenty of other ones). Do NOT attempt the 7200.11 fix you'll find on the internet, it can brick your drive.
Since drive does not produce clicking noise, most probably there is something wrong with the firmware. At this point it shouldn't be expensive if you consult a decent pro.

Alternatively, you can connect a TTL and post here terminal report. But DO NOT issue any commands.
If you value your data consult a pro.


this is a good piece of advise...
Post a reply