A lecturer in Childwall noticed write errors and did the sensible thing, which was to start copying everything off. He got about seventy per cent across before Windows stopped being able to read the drive at all. What was left behind was a single folder of recorded lectures, around 50GB, and it was the folder he could least afford to lose.
| Media | A WD Elements 3TB external drive that began reporting write errors, from which most content was rescued before Windows lost the ability to read it, with one 50GB folder still outstanding. |
| What was reported | WD Elements 3TB, write errors reported, roughly 70% copied off before failure, Windows now unable to read the drive at all, one folder of about 50GB still needed. |
| Fault class | Logical, at sector level. The drive had developed a growing population of weak and unreadable sectors, and ordinary retries were making the read take longer rather than making it work. No mechanical fault was present and the board was healthy. |
| On the bench | Read behind a hardware write blocker so nothing could be written, imaged read only on DeepSpar in controlled passes with the good areas taken first and weak sectors approached gently under a head health watch, filesystem parsed in R-Studio from the image, the outstanding folder located, validated and written to fresh media. |
Write errors are the first symptom you get, not the first fault you have. By the time a drive is failing writes it has usually been quietly reallocating sectors for a while. The error is the point at which it runs out of spare capacity to hide the problem behind.
Copying everything off was the right instinct executed the hard way. A file copy reads in the order the filesystem hands it out, and when it hits an unreadable sector it stops and retries until it gives up. On a drive with a growing bad area, that turns into hours spent hammering the worst part of the disk while the healthy part goes unread.
Imaging inverts the order and that is the whole point. The bench takes the readable areas first, in a single pass, and only then goes back for the difficult ones, in short controlled attempts. That way the bulk of the data is safely captured before any time is spent on the sectors most likely to finish the drive off.
No opening, no board work. Bad sectors are not a mechanical failure and they are not an electronic one. This was a read job, done read only, which is why it ran on the logical terms rather than the physical ones.
The drive was put behind a hardware write blocker so nothing, including Windows itself, could write to it. It was imaged read only on DeepSpar in controlled passes. The first pass skipped anything slow and captured everything that came back cleanly, which took the majority of the surface.
Later passes went back over the weak areas in short attempts with head health watched throughout, so the drive was never left grinding at a sector it was not going to return. The filesystem was parsed in R-Studio from the finished image, the outstanding folder located, and the recordings validated by playing samples from across the set before being written to fresh media.
The folder came back complete, recordings playable end to end. The seventy per cent he had already rescued stayed where it was, which kept the job small.
One drive, £300 + VAT. The fault was at sector level and the work was a read only image with nothing opened and no board touched, so it ran on no fix, no fee terms.
Stop copying and stop retrying. Every retry against a failing sector is more running time spent on the part of the disk least able to take it, and the clock you are burning belongs to the healthy part you have not read yet. If a copy has already stalled, cancel it rather than leaving it to grind overnight. Do not run a check disk, because repair tools write. Unplug the drive, note roughly how much you managed to rescue and what is still missing, and send it in. Imaging in controlled passes gets far more back than a file copy ever will.
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.
A large drive that will not register has a firmware, board or mechanical cause, and only a direct read separates them
Clicking is a head fault and a rattle after a knock is usually loose hardware, and both are settled in one clean-air visit
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.