SSD Boot Failure

GraphicMan2014

Reputable
Mar 13, 2014
4
0
4,510
I bought a Corsair Force Series GS CSSD-F360GBGS-BK 2.5" 360GB SATA III Internal Solid State Drive about 3 months ago. Got it up and running about 2.5 months ago. Yesterday, I tried to turn on the computer and it goes right to BIOS. BIOS sees both my drives (an SSD with windows 7 64-bit installed and an HDD as data storage). But, BIOS only sees the drive size on the HDD. No other data is found or able to be browsed via BIOS attempts.

Previous night I do not recall doing anything that could have caused such a problem. Did some graphic design. I open and closed Adobe editing software like After Effects and Premier. And that was it.

What I've done so far:

Tried to check a number of BIOS settings ranging from boot designation to manual booting from SSD. Checked some other settings like RAM, voltage, and BIOS settings and they all seemed normal.

Tried putting SSD in a second computer and disconnected all other drives. It didn't even recognize anything was plugged in. Put it back into main computer and tried booting off of Windows 7 Disc. Got it up, and Windows can't see the SSD. It sees the HDD, but for some reason, it doesn't recognize any backup files like my system recovery files (which I thought I stored on both drives for just such a problem). I tried doing bootrec.exe repairs. I used on both the default X: prompt and C: prompt. Nothing worked.

Went through these cmd prompt commands:
C:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /Rebuild Bcd

Now that I think of it, I didn't do it to X drive but will once I get out of the office. Let's assume for now the same results below occur. C: was designated my SSD, though, so going off of my storage device shouldn't result in any progress.

When typing out "cd boot" it claimed nothing was recognized. When typing out "attrib bcd -s -h -r" in cmd prompt, it claimed -r was not recognizable. And when I typed "bootrec.exe /FixBoot" I would get an "Element not found" error. It also claimed there was no recognizable Windows installation on either X or C drive. Tried to rebuild and it claimed it was successful even though it didn't recognize a Windows install. Restart = same boot to BIOS unless I boot to disc.

If you anyone can help, I have a $30,000 project on this drive and really need this drive up and running. Anything would be appreciated. So far, no local store gave me much confidence in pulling data from the drive.
 

TyrOd

Honorable
Aug 16, 2013
527
0
11,160
All I can do is laugh at you for not making a backup and then being obtuse enough to try to troubleshoot on your own without making an image of the HDD first.
At best you'll need to get a professional lab to recover your backups9which you have probably corrupted further) fro your hard drive.

If your SSD is physically failed it is impossible to do bare chip recovery because it is a SF controller.
Seriously, you should stop what you're doing and get your hard drive to a professional data recovery lab.
 

GraphicMan2014

Reputable
Mar 13, 2014
4
0
4,510


Can't help but feel like your response was a bit uncalled for. And I already stated I've created back up content on both hard drives and the only mistake is that somehow it didn't create to the 2nd drive.

I'd rather fix this myself at this point. I called data recovery shops all over my town and nobody had good confidence they would be able to help (and in all likely hood, they wouldn't be able to). Hence the reason I started trying all this out.

Another try I'm going to make is booting up in Linux from another box. I'm going to see if I can just get the drive to recognize so I can pull any data off of it. Couple of people on another forum advised this was a good solution for similar issues they've had.
 

TyrOd

Honorable
Aug 16, 2013
527
0
11,160


You're right, I apologize.

The point I was trying to make is that backing up to a second drive in the same machine is not a backup at all.
The second issue is that there are only 2 reasons why an ssd wouldn't show up in bios. The first and most common is a physical failure of the controller. The second is shorted resistors/capacitors or other superficial components on the SSD.

Because Sandforce uses built in hardware encryption on the controller no data recovery company can rebuild your data from the bare chips if the controller is failed.

If it's the second case, then it's a matter of repairing/replacing the shorted components to get the drive stable enough to copy the data over. obviously this still requires being familiar with SSD repair.

There are only a handful of labs in the US in general who do SSD Repair/rebuilds so obviously it's unlikely you'll find one in your town, though you may try looking elsewhere to send it out to.

Your best bet is to focus on recovering the backup data from your hard drive, but you should never work with the drive itself, because if you don't know why it's failed, you have a huge risk of causing further files system corruption.

You're next step should be to make an image of the hard drive and work with the image.
If you have no luck recovering the data with basic or commercially available data recovery software, then you'll still have the option of sending the original drive out to a lab.
 

GraphicMan2014

Reputable
Mar 13, 2014
4
0
4,510
Great, I'll do that. Haven't had a chance to work on it all weekend. Just now got my 2nd computer back up and working properly to trouble shoot this. I'll try and get an image of the drive and go from there. Thank you.
 

TRENDING THREADS