Hard Drive Not Detected in BIOS: Causes and Fixes

When a computer fails to detect a hard drive or SSD in BIOS, the machine typically displays an error such as “No boot device found” or “Hard disk not found” during startup, or the drive simply does not appear in the BIOS storage list. This means the firmware cannot communicate with the drive, so the system has nothing to boot from. The failure can stem from four distinct problems that present identically: a dead drive, a faulty cable or port, a firmware setting that disables the drive, or a drive that is present but unreadable. Telling these apart is the first step to a repair, because applying the wrong fix wastes time and can risk data loss.

Diagnose the Cause

Before touching anything, determine which of the four categories applies. The table below summarizes the causes and their distinguishing signs.

Step 1: Check the Obvious (Power and Cables)

A loose SATA data cable or power connector is the most common cause, and it is the least destructive to check. Shut down the machine, unplug it, and open the case. Reseat both ends of the data cable (motherboard and drive) and the power cable. If the drive uses an M.2 form factor, remove and reinsert it firmly, ensuring the screw is tight.

If the drive is still not detected, try a different SATA port on the motherboard. Some boards disable certain ports when an M.2 drive is installed, so consult the motherboard manual. Also try a different SATA cable, as cables can fail internally without visible damage.

Step 2: Test the Drive on Another Machine

To rule out a dead drive, connect it to a known-working computer. Use a USB-to-SATA adapter if necessary. If the drive is detected there, the drive itself is likely fine, and the problem lies in the original machine’s port, cable, or settings. If it is not detected anywhere, the drive is likely dead, but proceed to Step 5 before discarding it.

Step 3: Check BIOS Settings

Enter BIOS/UEFI setup (usually by pressing Del, F2, F12, or Esc during startup). Look for storage configuration options. Ensure the SATA controller is set to AHCI mode, not RAID or IDE, unless the OS was installed in a different mode. Also check if the drive is disabled in the boot order or in a “disabled” list. Reset BIOS to defaults if unsure: in the BIOS, choose “Load Optimized Defaults” or similar, then save and exit.

Step 4: Use Disk Management in Windows

If the drive appears in BIOS but not in Windows, it may be present but unreadable. Boot into Windows, right-click the Start button, and select Disk Management. If the disk shows as “Offline”, right-click it and select “Online”; that changes nothing on the disk.

Do not click “Initialize Disk” on a drive that held data. A disk that used to work and now shows as “Unknown” or “Not Initialized” has usually lost or damaged its partition table; the files are often still there. Initializing writes a new, empty partition table over it, and Microsoft’s own instructions warn that “the initialization process erases all data on the disk”. Creating a volume afterwards overwrites more of it. Recover first: restore from a backup if you have one, or run TestDisk, a free tool that can find and rewrite lost partition tables, ideally after copying the disk with ddrescue so recovery works on the copy (see Step 5). Initialize the disk only when it is new, or when you have confirmed that nothing on it is needed.

Step 5: Recover Data Before Assuming the Drive Is Dead

If the drive is not detected anywhere, it may still be recoverable. Do not format or reinstall immediately. Connect the drive to a working computer and use a live Linux USB to see if the kernel detects it. For example, boot from a Ubuntu USB and run:

lsblk

This lists all block devices. If the drive appears (e.g., as /dev/sdb), it is present but possibly failing. Use dmesg | grep sd to see kernel messages about the drive. If the drive is detected, back up data immediately using ddrescue or similar tools.

If the drive is not detected even in Linux, it may be a firmware issue or a dead controller. Some drives can be revived by updating firmware, but that is rare. In most cases, a drive that is not detected on any machine and makes no sound is dead.

What People Get Wrong

The most common mistake is assuming a dead drive when the problem is a setting or a cable. This is a natural error because the symptom is identical: the drive does not appear in BIOS. But a loose cable is far more common than a failed drive, and a BIOS setting can disable a drive without any hardware fault. Another frequent misdiagnosis is formatting a drive that is actually present but unreadable, destroying data that could have been recovered. Always confirm the drive is not detected on another machine before considering it dead, and always check BIOS settings before any destructive action.

Repairs in Order of Least Destructive

Reseat Cables and Ports

As described in Step 1, this is the first action. It costs nothing and can fix the issue immediately.

Reset BIOS to Defaults

Enter BIOS and load optimized defaults. This clears any incorrect settings that may disable the drive. It does not affect data on the drive.

Update Motherboard Firmware

If the drive is not detected after a BIOS update or on a new motherboard, a firmware bug may be the cause. Check the motherboard manufacturer’s website for a BIOS update. This is more involved but still non-destructive. Follow the manufacturer’s instructions exactly; an interrupted update can brick the motherboard.

Use a Different Interface

If the drive is SATA and the port is suspected faulty, try a USB-to-SATA adapter. If the drive is detected via USB, the motherboard’s SATA controller may be failing. In that case, a PCIe SATA card can be installed.

Check for Drive Firmware Updates

Some SSDs have known firmware bugs that cause them to drop off the bus. Check the drive manufacturer’s website for a firmware update. This is specific to the drive model and should be done with caution, as a failed update can make the drive unusable.

Recover Data with Linux Tools

If the drive is detected but unreadable, use Linux tools to attempt data recovery before any formatting. Tools like testdisk and photorec can recover partitions and files. Run them from a live USB.

Format and Reinstall (Last Resort)

If the drive is detected but unreadable and data recovery is not needed or failed, the drive may be formatted and used again. This destroys all data on the drive. To format, use Disk Management in Windows or diskpart:

diskpart
list disk
select disk X
clean
create partition primary
format fs=ntfs quick

Replace X with the correct disk number. This erases the entire drive. Only do this after confirming the drive is the one you intend to use and that data is not needed.

Replace the Drive

If the drive is not detected on any machine, makes no sound, and firmware updates do not help, it is dead. Replace it. There is no software fix for a dead drive.

Summary of Commands and Their Outputs

These commands are for advanced troubleshooting. Always back up data before using destructive commands.

When to Seek Professional Help

If the drive contains irreplaceable data and is not detected, professional data recovery services may be able to retrieve it. This is expensive and not guaranteed, but it is an option before discarding the drive. Do not attempt to open the drive yourself, as that can make recovery impossible.

By following these steps, you can identify whether the drive is truly dead or if a simpler fix exists. The key is to test each possibility in order, from least destructive to most, and to avoid assuming the worst until you have confirmed it.