← Back to Knowledge Hub SSD & NVMe

NVMe SSD not detected in BIOS: a real case with an SM2263XT controller

📅 19 November 2026 ⏱ 7 min read

In short: an M.2 NVMe SSD that no longer shows up in the BIOS is not necessarily empty. Most of the time its controller can no longer start, while the data is still sitting in the memory chips. Sometimes the computer first becomes very slow, then stops booting. Stop trying, and do not reflash or initialise the SSD. In a lab, that data can often be recovered. In the real case described here, a 1 TB SSD with an SM2263XT controller, the software first announced 16 days of reading. In the end the read took 26 hours, and a short re-read picked up the last missing sectors.

By Takhir Saidov, data recovery engineer at Belgium Data Recovery (Brussels). We handled this case in our lab in November 2026. The method we used was presented at the SSD workshop at ACE Lab TechWeek 2026 (Alicante, October 2026). We already wrote about that workshop in our article on SSDs with an SM2259XT controller.

The client's NVMe SSD connected to the PC-3000 Portable PRO
The client's NVMe SSD connected to the PC-3000 Portable PRO

The symptoms

The client brought us a 1 TB M.2 NVMe SSD made by Innovation IT. His computer had been very slow for a while. He restarted it, and it never booted again: the SSD no longer appeared anywhere, either in the BIOS or in Windows, as if the M.2 slot were empty. What mattered most to him were his photos.

On our test bench it was the same story: with normal power, the SSD did not respond at all.

Signs that can announce this kind of failure:

  • the computer becomes very slow, as in this case;
  • the SSD appears and disappears, or the computer hangs at start-up when the SSD is connected;
  • the SSD shows a nonsensical capacity (0 GB, 1 GB) or an unknown name;
  • Windows asks to initialise or format it.

What you can check yourself

Open your computer's BIOS and look at three things: is the SSD in the list? Does it show its real name? Does it show its real capacity? One look in the BIOS is enough.

  • If the SSD is not there, or it is listed under another name or with the wrong capacity, the problem is the SSD itself. Do not keep trying.
  • If everything looks normal in the BIOS and you can still reach your files, plug in an external USB drive and copy your data straight away.

Which SSDs are affected?

The SSD in this case uses a Silicon Motion SM2263XT controller. It is an NVMe controller without a cache memory (DRAM), found in many entry-level M.2 SSDs, for example (depending on the version and production date):

The same model can switch controllers from one batch to the next. Only a diagnosis can tell what is really inside your SSD.

Why the SSD disappears

An SSD does not store your files in order. The controller keeps a table, the translator, which says where each piece of data sits in the memory chips. That table is itself stored in the chips.

In this case the cause seems fairly simple to us. This is an entry-level SSD, very probably fitted with cheap memory. Over time, the cells of that memory "drift": they hold their charge less and less well, and read errors pile up. One day there are too many, and the controller can no longer load its tables at start-up. It stops there, and for the computer the SSD no longer exists. The files have not been erased, though. They are still in the chips, but nothing can find them any more.

What to do right now

  1. Stop trying. Every restart puts more strain on memory that is already struggling. Disconnect the SSD or switch the computer off.
  2. Do not update or reflash the firmware (the SSD's internal software), and do not use factory tools ("MPTool") found on the internet. They reformat the chips: the SSD may work again, but empty.
  3. Do not initialise or format the SSD if Windows offers to. If that has already happened, read Can you recover data from a formatted SSD or after reinstalling Windows?
  4. Write down the exact model and what happened before the failure: power cut, update, computer freezing, slowness…

What we did

Access through the technological mode

Using the PC-3000 SSD utility on our PC-3000 Portable PRO, we took control of the controller in technological mode, bypassing its blocked firmware, and rebuilt the translator. As a precaution we rebuilt it twice, independently. The two results were strictly identical.

First attempt: 16 days announced

The data was reachable again, but the read was barely moving: 2.4 GB read in 58 minutes, about 700 KB per second. The log was filling up with correction (ECC) errors, and the read map, where each square stands for an area of the SSD, showed whole bands of unreadable sectors. For the full SSD, the software announced more than 16 days, with holes in the files.

Before: repeated ECC errors and unreadable sectors
Before: repeated ECC errors and unreadable sectors
Before: about 700 KB/s, more than 16 days estimated
Before: about 700 KB/s, more than 16 days estimated

The feature presented by ACE Lab

At the SSD workshop at TechWeek 2026, the ACE Lab engineer presented a new SSD initialisation feature (nothing to do with the initialisation Windows offers). It is meant for exactly this situation: the translator has been rebuilt, but the poor-quality memory gives a lot of unreadable sectors. According to him, it then allows "better reading and fewer bad sectors". He presented it on SATA SSDs with an SM2259XT controller, the subject of his workshop, adding that NVMe controllers are more powerful and read the memory better than those in SATA SSDs.

Our SSD is an NVMe with an SM2263XT controller, a different controller from the one in the demonstration. We first backed up everything that could be backed up (firmware, service areas, translator), then started the operation. The software warns that afterwards the data will only be reachable through the PC-3000. Without those backups and without a translator rebuilt beforehand, you end up with an empty SSD.

After the operation: ten times faster

The SSD restarted with its real name and its real capacity. With our translator, the partitions and the folder list appeared at once. The read ran at between 5 and 9 MB per second, around ten times faster, with a clean log and a green read map. The estimated time dropped below 2 days.

BeforeAfter
Read speedabout 700 KB/s5 to 9 MB/s
Read timemore than 16 days (estimate)26 hours (actual)
Read logrepeated ECC errors, unreadable sectorsclean
After: the folder tree is visible, the read map is green
After: the folder tree is visible, the read map is green
After: 5 to 9 MB/s, less than 2 days estimated
After: 5 to 9 MB/s, less than 2 days estimated

Why such a difference?

After this operation, the SSD works with its own firmware again. Its internal mechanisms for re-reading and error correction, designed by the manufacturer for these exact chips, are active again. In technological mode, the tool reads the memory without them.

Result

The read finished on 14 November, in 26 hours, instead of the 16 days announced at the start. The average speed was close to 9 MB per second. Of the roughly 840 GB in use, about 20 MB of sectors were still unread at that point, or 0.002 %.

End of the read: 26 hours, about 20 MB unread out of 840 GB
End of the read: 26 hours, about 20 MB unread out of 840 GB

We then re-read only those missing sectors, in several rounds. In a quarter of an hour, what was left fell from 20 MB to 1 MB, then to zero. The 840 GB in use were read in full, and the final statistics no longer show a single sector in error.

The unread sectors after the read: about 20 MB
The unread sectors after the read: about 20 MB
End of the re-read: the map of the last missing sectors is entirely green
End of the re-read: the map of the last missing sectors is entirely green

This SSD is also among our solved cases: NVMe SSD missing from BIOS, read in 26 h instead of 16 days.

How we handle it

At Belgium Data Recovery, we recover data from SSDs with a Silicon Motion controller, SATA and NVMe alike, using the PC-3000 SSD utility on our PC-3000 Portable PRO. You can drop the SSD off at the lab in Brussels, by appointment, or send it to us by post. More details on our SSD data recovery page and in how a recovery works.

  1. Free diagnosis: identifying the controller and the chips, assessing the chances, then a quote.
  2. Accessing the SSD through the controller's technological mode and rebuilding the translator, after backing up the service areas.
  3. Copying the data with the reading method best suited to the condition of the memory, then extracting your files.
  4. Your data is returned on a drive you provide, or on a Belgium Data Recovery drive at extra cost.

We work on a No Cure No Pay basis: if we cannot recover your data, you pay nothing. If you gave us a list of your important files and we recover less than 75 % of them, you can turn down the result at no cost.

Further reading

Frequently asked questions

01My NVMe SSD no longer shows up in the BIOS. Is my data lost?

Not necessarily. In most cases the controller can no longer start, but the data is still in the memory chips. The diagnosis shows what can be recovered.

02My computer became very slow, then stopped booting. Is it the SSD?

It may be. That is what happened to the SSD described here. When an SSD's memory degrades, the controller has to re-read and correct more and more data, and everything slows down before the complete failure. If your computer slows down for no reason, back up your important files straight away. If it already no longer boots, do not keep trying.

03How do I know whether it is the SSD or the computer?

Look in the BIOS. If the SSD is not there, or it is listed under another name or with the wrong capacity, the problem is the SSD.

04Does the initialisation feature work on every SSD?

No. The result depends on the controller and on the condition of the chips. At the workshop it was shown on a SATA SSD with an SM2259XT controller; in our lab it worked on an NVMe with an SM2263XT controller. When it does not apply, what remains is reading in technological mode, which is slower.

05Can I repair the SSD myself with a reflashing tool?

No, not if you want your data back. These tools return the SSD to its factory state. As for the operation described here, it needs professional equipment and only makes sense once the translator has been rebuilt and backed up.

06Will my SSD be usable again after the recovery?

No. We recover the data, we do not repair the SSD. Memory that has failed once is no longer reliable.

07How long does it take?

Usually less than two weeks. Reading an SSD with degraded memory can take one or several days on its own, and we check the files before handing them back.

Real cases

Real cases handled in the lab

All solved cases →

Takhir Saidov
By Takhir Saidov
Founder · Belgium Data Recovery since 2012

Need help? Call us.

Free diagnosis · No Cure, No Pay · 24/7