A Seagate portable, used every day without incident, has suddenly "come up with a message saying 'The file or directory is corrupted and unreadable'", and access is wanted back as soon as possible. That message is Windows reporting that it cannot make sense of the drive's filing structures — it is not a statement about your files, which are almost certainly untouched. The structures in question are the tables saying where each file begins and ends, and they get damaged in ordinary ways: a cable knocked while a copy was running, a machine sleeping mid-write, a drive that stalled for a moment at the wrong moment. What follows next is what decides the outcome, and Windows will shortly offer to format it.
| Media | A Seagate portable drive in daily use that has begun returning the message that the file or directory is corrupted and unreadable. |
| Reported situation | Seagate portable drive · used every day · suddenly reports that the file or directory is corrupted and unreadable · contents inaccessible · access needed as soon as possible. |
| Fault class | Filesystem fault — the directory structures are damaged, most often by an interrupted write, so Windows cannot interpret the drive. Files generally intact and reached by imaging read-only and rebuilding the structure from the copy. Formatting or in-place repair is the real hazard. |
| Equipment used | Read through a hardware write-blocker so nothing could be written or repaired in place · read out to an image on DeepSpar, driven through PC-3000 UDMA · the filesystem taken apart in R-Studio from the image and the damaged directory structures rebuilt on the copy · files whose references had gone recovered by content signature, validated, and written to fresh media. |
The wording of the message does a lot of damage, because it sounds like a verdict on the contents. It is not. Windows is saying that when it tried to read the drive's directory structures it found something inconsistent and stopped. Your documents and photographs are elsewhere on the disk, in the same places they have always been, unaware that the index describing them has gone wrong.
The cause is nearly always an interrupted write. Every time a file is added, moved or deleted, the tables are updated, and that update is briefly a moment of vulnerability. A USB lead nudged, a laptop closing itself, a portable drive browning out on an underpowered port — any of them can leave the structures half-written. Which is why a drive that has behaved impeccably for years can fail during an ordinary Tuesday afternoon copy, and why nobody did anything wrong.
The important part is what not to do next, because Windows is about to make a suggestion. It will offer to format the drive, or to run a check that repairs it. Both write to the disk. A format builds a fresh empty index over the broken one; a repair pass rewrites the structures a recovery would otherwise reconstruct, and on a drive with any physical weakness it can make matters considerably worse. The bench route is to copy first — image the drive read-only — and rebuild on the copy, where every attempt is free and reversible.
It went behind a hardware write-blocker in line at once, so that no repair could happen in place and nothing on the drive could change. It imaged cleanly on DeepSpar behind PC-3000 UDMA. The filesystem was then unpicked in R-Studio from that image and the damaged directory structures rebuilt on the copy, with anything whose references had gone entirely carved out by content signature. Recovered files were opened and checked rather than merely listed before they went onto fresh media.
Imaged read-only, directory structures rebuilt from the copy, and the files recovered out onto fresh media with their folder structure largely preserved. The diagnostic cost nothing; the figure that followed was fixed, written and inclusive of VAT. Healthy hardware and a logical fault meant this ran on no fix, no fee: had the files not come back, there would have been nothing to pay. The drive itself was fine and was returned working, with the observation that a drive in daily use is a working copy rather than a backup.
Say no to the format, and keep saying no. That message means Windows cannot read the index, not that your files have gone, and both remedies it offers you — formatting and the repair pass — work by writing to the disk, straight over the structures a recovery rebuilds from. Do not run chkdsk. Do not accept any invitation to scan and fix. Unplug the drive and leave it disconnected, because a drive that is failing physically as well as logically gets worse every minute it is asked to try. Then have it imaged read-only, so that all the rebuilding happens on a copy and the original is never risked. The great majority of these come back complete, and the ones that do not are usually the ones that were repaired first.
Every case file here is written up from a real enquiry handled for households and businesses across Norwich and Norfolk, anonymised so that nobody is identifiable. Each sets out the reasoning behind the diagnosis and the method used on that particular fault, with the equipment named.
One folder, one deadline and one honest number — the fault decides the price, so the fault gets established first
The drive is fine and the index is not — which is a filing problem, and filing problems are rebuilt from a copy
Windows cannot start, which is a problem for the laptop rather than for the photographs on its drive
Diagnosis costs nothing and takes up to 2 working days from arrival, the quote is fixed in writing, and logical work runs no fix, no fee — start online or ring the freephone.