A 12TB IronWolf Pro with something close to 10TB on it had simply stopped appearing. The owner, who runs a small architectural practice in the Georgian Quarter, was blunt about what he wanted: the drawings back, or failing that a list of the file names so he knew what had to be redrawn. He asked about a counter in town he could take it to. There is no such counter, so the drive came by post.
| Media | A 12TB Seagate IronWolf Pro holding roughly 10TB of drawings and project files, no longer registering on the machine it had always sat on. |
| What was reported | IronWolf Pro 12TB, about 10TB in use, stopped registering on the desktop, no unusual noise, owner wanted the files or at minimum a file listing, asked about dropping it in. |
| Fault class | Firmware. The drive was not presenting itself to the host, so it never registered. The platters were untouched and the board was healthy, which the bench established before it touched anything. |
| On the bench | Read directly behind a hardware write blocker on PC-3000 UDMA, firmware modules and service area profiled first, the damaged module set rebuilt from the drive's own copies, imaged on DeepSpar, filesystem parsed in R-Studio and a full file listing generated from the same image. |
A drive that will not register is not a drive that has lost anything. Registering is the handshake. If the drive cannot complete it, the machine has nothing to show, and the machine says so in the only way it can, which is silence. Nothing about that silence tells you the platters are damaged. It tells you the drive cannot introduce itself.
Three things stop that handshake, and they carry different prices. Firmware, the board, or the mechanism. Firmware is code and tables the drive keeps on the platters and in its own ROM. The board is electronics. The mechanism is heads and motor. They present almost identically to a user and not at all identically to a bench, which is why the diagnostic runs before the quote and not after it.
This one was firmware, and that matters commercially. The service area held a corrupted module and the drive was stalling on it. Rebuilding it is code work. It is not board repair, and the distinction is not academic: firmware sits inside no fix, no fee, and board repair does not, because board repair is electronic work and the published terms carve electronic work out.
The file listing was never a fallback. Owners ask for one when they are bracing for bad news. In practice the listing comes out of the same image as the data, so if the bench can give you the names it can usually give you the files. He got both.
The drive was put behind a hardware write blocker and read directly on PC-3000 UDMA, so nothing was written back to it at any stage. Its firmware modules and service area were profiled before any attempt to bring it ready. One module was corrupt and the drive was hanging on it. It was rebuilt from the drive's own redundant copies rather than from a donor, which keeps the translation honest.
With the drive ready, it was imaged on DeepSpar in a single controlled pass. The filesystem was parsed in R-Studio from the image, never from the drive. The full file listing the owner had asked for was generated from that same image and sent ahead of the data so he could check nothing was missing.
The module was rebuilt, the drive imaged, and the whole of the working set came back, drawings and project folders intact. The listing he had braced himself to settle for turned out to be the index of a complete recovery.
One drive, £300 + VAT. The fault was firmware, which is logical work, so the job ran on no fix, no fee terms and nothing was payable until the files were confirmed. Had the diagnostic pointed at the board instead, the terms would have been different, and he would have been told that before the work started rather than after it.
Stop plugging it in. Every retry is another spin-up, and if the cause turns out to be mechanical rather than firmware, spin-ups are exactly what you cannot afford to spend. There is nothing you can run at home that separates a firmware fault from a head fault, and the free software that claims to will do its guessing while writing to the disk. Send it in, let the diagnostic name the fault in two working days, and decide with a figure in front of you. If you want a file listing before you commit, ask for one. It costs nothing to produce and it usually arrives attached to good news.
Every case file here is written up from a real enquiry handled for households and businesses across Liverpool, Merseyside and the wider North West, anonymised so that nobody is identifiable. Each one gives the reasoning behind the diagnosis, the method the fault actually called for, and the equipment it was worked on.
Clicking is a head fault and a rattle after a knock is usually loose hardware, and both are settled in one clean-air visit
Write errors are an early warning, and the right response is one careful image, not weeks of retries
A drive that has been taken out of a machine is read on its own, whatever it was doing while it was still in one
The diagnostic is free and takes 2 working days from arrival, the figure is fixed in writing, and logical faults run on no fix, no fee. Start online or ring the freephone.