Data Recovery Case File · Portable Drives · An Absence, Not a Format
Raw Means the System Cannot Tell What It Is
His enquiry uses a term the system supplied and it is worth unpacking. A 3TB external drive that stopped connecting: "I've had a look into it and found out the drive data is raw. I have been unable to retrieve any data back myself, which is very disapp"ointing. That word looks like a diagnosis and functions like one, so people treat it as a state the drive has entered. It is not a filesystem and not a condition — it is what the system reports when it cannot identify one at all.
| Media | 3TB external hard drive of two to three years — volume present and reported as having no identifiable filesystem; owner's recovery attempts unsuccessful |
| Reported situation | Drive of two to three years ceasing to connect usefully · volume reported by the host as raw · owner unable to retrieve data using consumer tools · contents required |
| Fault class | Filesystem descriptor unreadable with the partition intact — content present; volume not mountable and therefore not scannable by tools requiring one |
| Equipment used | No format permitted · imaged write-blocked before any reconstruction · filesystem descriptors located from surviving backup copies on the image · signature carving alongside · files validated by opening |
The decode: what the system means by it
How a computer decides what a volume is: it reads a small descriptor at the start of the partition that states the filesystem type and its key parameters. That descriptor is how everything else follows — where the directory lives, how big the allocation units are, where the records begin. Without it, the system has a partition and no idea what to do with it.
So what "raw" reports: exactly that. The partition table is intact and lists a partition; the descriptor inside it could not be read or made sense of; and the system has no name for what it found. Raw is the label for "unidentified", not a type of formatting, and it says nothing whatever about the data occupying the rest of the partition.
Why that is a good position rather than a bad one: the damage is to a structure measured in kilobytes at the front of a 3TB volume. Everything behind it is untouched. Filesystems also keep backup copies of that descriptor and of their key structures at known positions away from the start — which is precisely what a rebuild works from, and which a raw report does not disturb.
Why his own attempts found nothing, and it is not evidence of loss: most consumer recovery applications work through the operating system and require a mountable volume to scan. Where nothing mounts, they have nothing to enumerate and report accordingly. Tools that read the device directly are a different class, and the failure of the first kind says nothing about whether the data survives.
What the system will offer, and why it must be refused: a raw volume prompts an offer to format, worded as making the drive usable. Accepting writes a fresh descriptor and a new empty directory over the region a rebuild reads — turning a straightforward reconstruction into a carving job. That prompt will appear every time the drive is connected.
What causes it: most commonly an interrupted write to that region — an unclean disconnection, a crash, or a power loss while the volume was being updated. Sometimes the beginning of a physical read problem in exactly that area, which is why the drive is assessed rather than assumed healthy.
What to do meanwhile: disconnect it, and run nothing further against it.
On the bench
No format was permitted, a raw volume prompting one on every connection and acceptance writing a fresh descriptor over the region a rebuild reads. The drive was imaged write-blocked before any reconstruction, and filesystem descriptors located from their surviving backup copies on the image — filesystems maintaining duplicates at known positions away from the start, which a raw report leaves untouched. Signature carving ran alongside and files were validated by opening.
The outcome
The format refused, the drive imaged before any reconstruction and the descriptors recovered from their surviving copies. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: raw is not a filesystem and not a state your drive entered. It is what a system reports when it reads the small descriptor at the start of a partition and cannot identify what it describes — a structure measured in kilobytes on a 3TB volume, with everything behind it untouched.
Volume showing as raw
Refuse the format — that prompt will appear every time you connect the drive, and accepting it writes a fresh descriptor over exactly the region a rebuild reads. Take the word less seriously than it sounds. Raw isn't a filesystem and isn't a state your drive has entered: a computer identifies a volume by reading a small descriptor at the start of the partition stating its type and parameters, and raw is simply the label for "I couldn't identify this". It's a structure measured in kilobytes at the front of your drive, with everything behind it untouched, and filesystems keep backup copies of it elsewhere. Your own tools finding nothing isn't evidence either — most need a mountable volume to scan and there isn't one.
Don't format it — call Guildford Data Recovery on 01483 901310; imaged write-blocked before any reconstruction, descriptors recovered from their surviving backup copies, files checked by opening.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.