You check a misbehaving drive in Disk Management and where it used to say NTFS, it now says RAW. Windows offers to format it. File Explorer either shows nothing or throws “the volume does not contain a recognized file system.”
RAW isn’t a file system, and it isn’t “blank.” It’s Windows saying: there’s a volume here, but I can’t identify how it’s organized. Your files are almost always still in place — the structures that identify the file system are what’s damaged.
How a drive goes RAW
Every NTFS volume starts with a boot sector and critical metadata (the Master File Table, which is the index of every file on the volume). Windows reads those structures to know what it’s dealing with. Damage the first few sectors — or key MFT records — and Windows can’t identify the volume at all, so it reports RAW.
The common causes:
- Unsafe removal or power loss mid-write. The metadata was being updated when power vanished.
- Developing bad sectors. If the sectors holding the boot record or MFT go bad, the volume goes RAW even though 99.9% of the drive reads fine. This one matters, because it means RAW is sometimes the first visible symptom of a physically degrading drive.
- Partition table damage from a crash, a buggy tool, or an OS install gone sideways.
- Encryption confusion. A BitLocker volume can show RAW on a machine that doesn’t recognize it. If the drive might be BitLocker-encrypted, stop — recovery without the key is a different conversation.
The CHKDSK warning
The internet’s standard advice for RAW drives is chkdsk /f. Please don’t. CHKDSK on a RAW volume usually just refuses (“CHKDSK is not available for RAW drives”) — but on a volume it can partially read, it will attempt repairs, and CHKDSK repairs a file system by discarding what it can’t reconcile. On a corrupted MFT, that can mean converting thousands of intact files into anonymous fragments in a found.000 folder.
The same caution applies to any repair-in-place tool. The correct order of operations is always: image first, repair the copy. If the underlying cause turns out to be bad sectors, working on the original also means racing a failing drive with no safety net.
Free evaluation. Firm quote before any work begins.
What recovery looks like
At my bench, a RAW drive gets imaged sector-by-sector first — bad sectors handled carefully, originals untouched. Then the file system gets rebuilt from the image. NTFS keeps a mirror copy of critical boot data and the MFT is often largely intact, so these recoveries frequently come back complete: filenames, folder structure, everything. RAW recoveries are logical work — typically 2 to 5 business days and the lower end of my $150–$500 range — unless the evaluation shows the drive is physically degrading, in which case I’ll tell you exactly what changed and quote accordingly before doing anything.
The bottom line
RAW means “unidentified,” not “erased.” The two moves that most often turn a clean recovery into a messy one are running CHKDSK and clicking Format. Skip both, power the drive down, and get it imaged. The odds are on your side if the first tool that touches that drive isn’t trying to fix it in place.
Drive showing RAW right now? Start a case — mention whether Windows also reported any errors before this happened, because that detail changes the diagnosis.