SSD seen by BIOS, but not named. Will not boot

[Cp_12]

I have an SSD boot/Windows drive and a second hard disk that stores my media. It is close to 2 years old now, and has been running Windows 10 as an upgrade from Windows 7 for 6 months.

Now, when it boots, the BIOS will identify that a hard drive is present in the SATA port of the SSD but does not identify a name/model number. When I select that drive to boot to Windows, the boot fails and requests that I insert the system disk. Running DiskPart on the windows USB boot drive would not recognize the drive at all.

I'm hoping that the disk hasn't failed completely but if it did, it did. This is just a bizarre behavior and I'm trying to find out whether I can use the SSD. Any insight would be appreciated.

 

[BadAsAl]

Can you try another SATA port? I would use the one from your data drive. This will eliminate the SATA port or cable as an issue if it is the same while connected to a different port and cable.
Then, I would try a Linux Live CD and see if the drive is there when you boot to the CD.
I would pull the drive and hook it up to another computer using a USB adapter too if that is an option for you.
I have not done any testing on an SSD but check the manufacturers website and see if they have a tool to try.

 

[Bob57]

This sounds like the SSD has borked Logical Block 0. If this happens your BIOS will still see the device as a valid SATA device, the firmware is up sufficiently to provide the requirements for the interface, but when the system tries to fetch the boot block it will fail. The failure causes the boot process to bring up the message saying it can't find a boot device. Additionally, if you boot up Windows from another bootable device you "may" be able to access the file system on the broken device. If this is the case you may be able to manually copy files from the borked device to a working device. If you don't have anything else that can boot, you may also be able to access the file system by getting into the command line console from Windows recovery mode. Again, if so, then you can manually copy files from your borked device to a working device. However going this route is very primitive, no gui just a DOS-like command prompt interface. At least this way you can attempt to preserve some of your data.

You won't be able to reformat it either.

My suggestion is that if the device is still under manufacturers warranty you contact them to see about an RMA.