Case notes · Logical & corruption · EDR-2025-2932
Pulled Out While the Essay Was Still Saving.
Nine o’clock, the evening class packs up, and the stick came out while my essay was still saving
. By morning every file kept its name yet reported 0 bytes
, the type column offered a blank File
, and the tutor’s advice — stop clicking on them
— came one open too late. At stake: a term of Access-course work.
Sound familiar? Talk to us.
0800 6890668
In plain English.
A file that keeps its name but forgets its size has a paperwork problem, not a contents problem. FAT records each file in a directory table — name, attributes, size, first cluster — kept apart from the data it describes. Interrupt the stick while that table is being rewritten and the update dies halfway: sizes zeroed, type information lost, while the clusters holding the actual essays sit further along the chip, finished and unvisited. Windows then repeats whatever the broken table tells it, so a full folder reports itself empty with complete sincerity.
The tools this job took.
See how your case runs →| System | The part it played | Why we rate it |
|---|---|---|
| PC-3000 Flash | Copied the stick sector by sector, ignoring the filesystem’s confused account | Reads the memory chips themselves, matching each one against an up-to-date identification library |
| R-Studio Technician | Rebuilt the damaged records, leaning on the duplicate structures FAT keeps | Handles most filesystems; dependable RAID reassembly |
| UFS Explorer Professional Recovery | Format-signature carving for the handful of entries past repair | Handles the harder filesystems well — APFS, ReFS, XFS, ZFS and Btrfs |
On the bench.
A full copy first, before anything else touches it
Every remount is an invitation for the stick’s controller to housekeep, and its tidying takes no account of which clusters a recovery might want. So it went straight onto the imager for a sector-level read, and from the moment that fixed copy existed, no experiment could cost her anything.
Repair what the duplicate tables still remember
FAT stores two copies of its allocation table, and the damage had fallen unevenly between them. Wherever the sounder copy and the surviving directory structures agreed, records were rebuilt entire — name, size and cluster chain restored as a set, which is what separates a named file from an educated guess.
Let the last few identify themselves
A few records were past mending. Their files were traced instead through internal format markers — Word and PDF signatures spotted in the clusters, contents reassembled in sequence, and plausible names reattached only where a header or the text itself gave grounds.
How it ended.
Most of the term’s work opened normally under its own name; a small remainder carried carved names and needed sorting by eye. Everything went back on fresh media, and saving now finishes before the packing-away starts.
More like this in the casebook.
More cases filed under Logical & corruption.
Sound like your drive?
Every case here points the same way: power the device down, take the free diagnosis, then make your decision.