A WD Red pulled from a NAS, turning at full speed with no clicking and no grinding, and invisible to every machine it was connected to. The mechanism was healthy. What had failed was the drive’s ability to describe itself.
A WD Red 4 TB stopped being recognised — not by the NAS it lived in, not by Windows, not by macOS. The owner had done the sensible things first: different cables, different ports, a different machine. Nothing changed. The drive spun up every time, sounded entirely normal, and appeared nowhere.
That combination is worth recognising, because it feels like the worst outcome and is usually among the better ones. Mechanical failures announce themselves — clicking, grinding, a buzz with no spin. Silence plus rotation plus invisibility points somewhere else entirely.
The motor and heads were functional. The fault was in the service area: a reserved region on the platters, outside the user data area, where the drive stores the firmware modules it loads at power-up. Among them are the modules describing the drive's own geometry and the translator that maps logical sector addresses to physical positions.
When one of those becomes unreadable the drive cannot complete its startup routine, so it never presents itself to the interface. It is not refusing to give you the data — it has lost the ability to say what it is. WD Red drives keep these modules on the platters like any other drive, which means the repair happens through the drive's own diagnostic interface rather than by swapping anything.
This is the one situation where our normal order of work has to change, and it is worth explaining. The standing rule is to image read-only before touching anything, so every subsequent attempt runs against a copy. Here that was not possible: you cannot image a drive that will not enumerate. There is nothing to read from.
So the service area had to be addressed first. Access was established through the manufacturer's diagnostic mode, the damaged modules identified, and the translator repaired until the drive reported its true 4 TB capacity and presented normally. Only then — and immediately — was it imaged sector by sector, read-only, with nothing written to the user data area at any point during either stage.
The distinction matters: the firmware repair touched the reserved region only, and the user data was never modified. But it is a genuine exception to imaging first, and any lab telling you otherwise about a non-enumerating drive is describing something that cannot be done.
The file system mounted from the image without repair, which is typical of service-area faults — nothing had ever been written incorrectly, the drive had simply become unable to present itself. Business documents, archives and database files were opened in their applications and the set returned on fresh media.
A complete recovery. The single risk factor throughout was repeated power-cycling: each start gives an unstable drive another opportunity to write over what remains of its own firmware, and this one had been through a fair number of cable-and-port attempts before it arrived. It survived them, but that is not a given.
A drive that turns normally and reports nothing usually has a service-area or board fault with the user data untouched. The harm comes from repeated attempts while somebody troubleshoots, because each start gives an unstable drive another chance to overwrite its own firmware. Where a drive will not enumerate at all, the firmware must be repaired before it can be imaged — there is nothing to read from until it does. Single drives from £300 +VAT.
Send us your device for a free diagnostic, and tell us a little about what happened — an engineer will review it and confirm your exact quote in writing before any work begins.
Getting your data back begins with getting the device to us. Pack it up safely, pop your contact details inside, and send it over — once we’ve run the free diagnostic, we’ll confirm your exact price in writing before any work starts.
Posting it? A tracked, insured service is what we’d recommend. Rather drop it in? You’re welcome Monday to Friday, 9am to 5:30pm — just package the device up as above first.
Want a bit more detail first? Fill in the form with more about your issue and an engineer will review it and send you a custom quote.
We’ll be in touch shortly. For anything urgent, call 01865 593000.
Usually a service-area or firmware fault rather than a mechanical one. Drives load their operating firmware from a reserved region on the platters, and if a module becomes unreadable the drive cannot finish starting — so it never presents itself, while the user data sits untouched.
Normally yes, and that is our standing rule. A drive that will not enumerate is the exception, because there is nothing to image from — the service area has to be repaired first to make the drive readable at all. That work touches the reserved region only, never the user data.
Not for this fault. WD Reds store firmware modules on the platters like any other drive, so the repair route is the same. What it does change is context — a Red is usually one member of an array, and if the array is degraded the other disks should come in too.
Possibly slightly. Each power-up gives an unstable drive another opportunity to write over what remains of its own firmware. Eliminating cables and ports is reasonable, but once the drive is consistently invisible, repeating it has no diagnostic value.
From £300 plus VAT for a single drive after a free 48-hour diagnostic. Where the drive forms part of a NAS or RAID set, array work starts from £500 plus VAT and every member should be sent, labelled by bay.
Start with an instant online quote, or call and talk it through with us first. You'll have a clear, fixed price before any work begins.