Server Hard Drive Not Detected: A Troubleshooting Guide

A drive that is not showing up looks like a dead drive, and often is not. A meaningful share of the drives returned to us as faulty are working units that failed for a different reason — a carrier mismatch, a firmware rejection, a seating problem or a controller state.

This guide works through the checks in order, from most likely to least, so you can rule out the cheap causes before concluding you have a failure.

Start with what changed

Before touching anything, establish which situation you are in, because the likely causes are completely different.

A new drive is not detected. This is almost always compatibility rather than failure. Work through the sections below in order.

An existing drive has disappeared. This is more likely an actual fault or a seating problem, but controller state and cabling are worth ruling out first.

Several drives disappeared at once. Suspect the backplane, an expander, a cable or the controller rather than the drives. Multiple simultaneous drive failures are rare; a single shared component failing is not.

Check one: is it physically seated

Obvious and frequently the answer. Drives can appear seated while sitting a few millimetres short of the backplane connector, particularly if the carrier latch was closed against resistance.

Pull the drive fully out and reinsert it firmly until the latch engages properly on its own. On a hot-swap system you can do this while the server runs if the array is otherwise healthy. On a simple-swap system the server must be powered down first.

If the drive does not slide home smoothly, stop and check the carrier before forcing it. Which brings us to the most common cause of all.

Check two: carrier and caddy generation

This is the single most common reason a new drive is not detected, and it is entirely a compatibility issue rather than a fault.

Server manufacturers used several carrier designs and they are not interchangeable. The differences are in latch geometry, connector alignment and the position of the status indicator contacts. A drive in the wrong generation either will not slide home or will seat without registering correctly on the backplane.

IBM System x used simple-swap, early hot-swap, G2HS and later G3HS. Four possibilities, one correct.

Lenovo ThinkSystem continues G3HS, which does not interchange with G2HS.

HPE ProLiant Gen8 onwards uses Smart Carrier trays, and the generation must match the chassis. Earlier HP G-series servers use a different design again, and HP Integrity another.

The check: pull a working drive from the same chassis and compare the trays side by side. Better still, read its part number — that string encodes drive, carrier and firmware together, and ordering against it removes the guesswork. Our compatibility guide lists carrier types by platform.

Check three: interface mismatch

Three situations produce a drive that will never be detected regardless of anything else.

SAS drive in a SATA backplane. This does not work. The compatibility runs one way only: SATA drives work in SAS backplanes, SAS drives do not work in SATA backplanes.

SATA drive in a SAS-only backplane. Some enterprise chassis and storage arrays accept SAS exclusively and will not recognise a SATA drive at all. Where that is the case, the capacity option is NL-SAS.

Fibre Channel in anything else. FC is electrically and logically distinct from SAS, with different connectors and no adapter path. FC drives work only in FC shelves.

Interface generation, by contrast, is rarely the problem. SAS and SATA both negotiate down — a 12Gb/s drive runs at 3Gb/s in an older backplane and functions normally.

Check four: firmware rejection

If the drive is physically correct and still not usable, this is the next candidate — and it is not a fault either.

HPE Smart Array, Dell PERC and IBM ServeRAID controllers validate drive firmware. A mechanically identical drive without vendor coding produces one of several outcomes: it may be flagged as unsupported in the management interface, may be detected but refused for array membership, may work without reporting health telemetry, or may be rejected specifically during a rebuild.

The tell is that the drive is visible somewhere — in the controller utility, in a device list — but marked unsupported, foreign or unusable rather than absent entirely.

NetApp is the extreme case and behaves differently: its disks are formatted with non-standard sector sizes, so a standard drive is rejected outright and cannot be made to work. See our NetApp guide.

Check five: controller state

Sometimes the drive is fine and the controller is holding it in a state that hides it.

Foreign configuration. A drive previously used in another array carries configuration metadata. Controllers often quarantine these rather than adopting them silently, and the drive appears as foreign until you import or clear that configuration deliberately.

Unconfigured good. The drive is detected and healthy but not assigned to anything. It will not appear as usable storage until it is added to an array or set as a spare.

Previously failed state. A drive marked failed by the controller stays marked, even if the underlying issue was transient. It has to be cleared explicitly.

All three look like a missing drive from the operating system and are visible in the controller utility. Always check there before concluding anything.

Check six: cabling, expanders and the backplane

If several drives went at once, start here rather than at the drives.

A loose or failing SAS cable, a failed expander, or a backplane fault takes out everything downstream of it. The pattern is diagnostic: if the affected drives are all in the same bay group or all behind the same connector, the shared component is the suspect.

On Fibre Channel shelves there is an additional failure mode worth knowing. FC uses an arbitrated loop, so one drive misbehaving electrically can disrupt communication for others on the same loop. Several drives appearing troubled at once on FC does not necessarily mean several failures.

When it really is the drive

Signs that point at genuine failure rather than compatibility:

Audible clicking, grinding or repeated spin-up attempts. The drive not spinning up at all, with no vibration when held. SMART attributes showing reallocated sector counts climbing, pending sectors, or a failure prediction. The drive detected but reporting incorrect capacity or identity. Detection that comes and goes intermittently under load.

The last one is worth flagging: an intermittently failing drive is more dangerous than a dead one, because an array may keep using it while it corrupts. If a drive drops and returns repeatedly, replace it rather than reseating it again.

Before you return it

Run through this list: is it fully seated; does the carrier generation match a drive already in the chassis; is the interface correct for the backplane; does the controller utility show it as unsupported or foreign rather than absent; did several drives go at once.

If all five are clear and the symptoms above are present, it is a drive fault. Our warranty and returns page covers the process, and everything we supply carries a 30-day warranty with 30-day returns and no restocking fees.

If you are unsure, send us the server model and the part number from a fitted drive and we will work through it with you rather than processing a return that will not fix the problem.

Common questions

Send us the server model and the part number from a fitted drive and we will help identify whether it is a fault or a fit problem.