0

Brand 1TB: FIKWOT Solid State Drive - This one: https://www.amazon.com/gp/product/B0B4J9HHW6

I have this SSD SATA drive below. I plugged it into my computer and the bios doesn't detect it. But when I plug it in via a USB adapter it just stuck on loading, but detects the drive in Acronis, see below.

It was working fine for a good 6 months running windows 10. Now it just doesn't detect. I'd like to access my data back if possible.

What could be the issue with this SSD that its not detecting properly?

enter image description here

enter image description hereenter image description here

Improve this question
8
  • 1
    This question should include more details and clarify the problem.
    – Ramhound
    Commented Jun 12 at 17:20
  • 1
    Es ist kaputt? We need, of course, a little background story. But if BIOS does not detect, Disk Management stalls then for some reason it's not ID'ing as it should. What is the brand, a Patriot? Don't answer / add info to comments, edit the question instead. Does the Acronis tool have a SMART tool and if so does it display data about the drive?
    – Joep van Steen
    Commented Jun 12 at 17:35
  • updated. what more details do you like?
    – Patoshi パトシ
    Commented Jun 12 at 17:46
  • Either the controller or flash has died. If you absolutely must get the data back then you may well have to contact a data recovery service.
    – Mokubai ♦
    Commented Jun 12 at 17:57
  • @Patoshiパトシ - I don't trust your motherboard has a m.2 SATA capability. I also don't trust it's a SATA. I don't have the required information to do any research. Specifications on Amazon are not reliable.
    – Ramhound
    Commented Jun 12 at 18:25

1 Answer 1

Reset to default
1

Most common cause is a firmware level issue. SSDs operate like hard drive when they 'boot'. I am referring the drive itself 'booting', so controller powering on and attempting to load it's firmware from the NAND (or in case of a spinning drive from the platters).

Firmware should be taken in broad sense, so not just code but also for example the 'translator' or FTL. In turn the failure to load firmware can be due to for example improper shutdown or NAND degradation.

To recover the data one would need access to the firmware. Pro grade data recovery tools like PC3000 can try accessing the firmware by booting the drive in factory-mode and by using a custom loader. They can then attempt to for example generate a new virtual translator.

Think of it as a logical file recovery tool rebuilding a virtual file system and MFT to allow recovery of lost files from a corrupt NTFS drive.

Problem with the Pro grade tools is that they're expensive and they support only a limited amount of SSD models. The more obscure the model, the less chance it's supported, and I fear this Maxio controller isn't. A lab may still be able to recover the data but the odds aren't great.

enter image description here

DIY level there isn't much you can do. IF the issue is for example at FTL level just powering on the drive and granting it idle time occasionally helps. In case of SATA you could for example power up the drive without data cable and let it sit for a few hours. I've seen cases reported where it needed over-night or over-weekend to eventually come to life. The idle time essentially allows for the SSD to fix itself (think of it as a chkdsk on firmware level).

For specific controllers DIY type fixes can be found on Chinese and Russian forums (SM2258XT for example).

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .