RAW Partition / RAW Drive

RAW is a status, not a file system. Windows uses “RAW” as a label in Disk Management when it tries to read a partition‘s file system metadata and can’t recognize what it finds. Every file system stores a signature in known locations on the partition: NTFS keeps its boot sector at logical block 0 with the signature “NTFS “; FAT32 keeps the BPB (BIOS Parameter Block) at the same location; exFAT uses its own volume header. When Windows reads those locations and finds the signature missing, corrupted, or unrecognizable, it has no way to interpret the rest of the partition and labels the file system column as RAW.¹

Three things RAW status doesn’t mean

• RAW doesn’t mean the data is gone. The actual file content sectors typically remain physically intact on the drive; only the metadata that tells Windows how to interpret them has been damaged.
• RAW doesn’t mean the partition is unformatted. The partition almost certainly was formatted at some point with NTFS, FAT32, exFAT, or another file system; what’s broken is just the file system’s catalog structures.
• RAW doesn’t mean physical drive failure. RAW is a logical-level problem with the file system metadata. Physical drive issues like bad sectors can cause RAW status, but RAW itself is a software-level diagnosis.

Disambiguation: three different uses of “RAW”

The word RAW gets used in storage in three different ways. The recovery-relevant meaning is the first one:²

• RAW partition / RAW drive (this entry): Windows status indicating an unrecognized file system on a partition. The recovery scenario.
• Raw disk access (database/Oracle term): a low-level disk access mode where applications read and write directly to disk sectors, bypassing the file system. Used historically by databases for performance; not relevant to consumer recovery.
• RAW image file (camera term): an image format produced by digital cameras containing minimally-processed sensor data. Completely unrelated to RAW partitions.

RAW from the OS’s perspective

When Windows mounts a partition, it reads the first few sectors looking for a recognizable file system signature. If found, Windows loads the appropriate file system driver (NTFS.sys, FAT.sys, or similar) and the partition becomes accessible normally. If not found, Windows still recognizes that a partition exists (because the partition entry is in the GPT or MBR partition table) but has no way to make the partition’s contents accessible. The result is a partition that shows up in Disk Management with a size and a drive letter, but with the file system column displaying RAW and any attempt to access it triggering the format prompt.³

Windows signals RAW status through several specific behaviors. If you’re seeing any of these on a drive that previously worked normally, the partition is RAW.⁴

The format prompt is the clearest signal

The “You need to format the disk before you can use it” prompt is the most common way users discover RAW status. It appears the moment Windows detects the unrecognized file system, often immediately when an external drive is plugged in or when accessing a drive after a system reboot following corruption. This prompt is the single most dangerous moment in a RAW partition recovery scenario, because the obvious user response (clicking Format to make the drive work) is exactly the action that complicates recovery. Cancel the prompt every time, even if you’re 100% sure there’s no important data on the drive; you can format later, but you can’t unformat.

Confirming RAW via diskpart

If you want certainty about the partition’s status, the diskpart command-line tool gives a definitive answer:

RAW status results from damage to the file system’s metadata structures. The damage comes from several typical causes, ordered roughly by frequency:⁵

Improper unmount or power loss

The most common cause. When an external drive is unplugged while Windows is in the middle of writing to it, or when a desktop loses power during a file operation, the file system’s metadata structures end up in an inconsistent state. NTFS journals make this less common than it once was, but it still happens with FAT32 and exFAT (which have no journaling) and with NTFS when corruption hits in the wrong place at the wrong time.

Malware and ransomware

Some malware specifically targets file system metadata to make data inaccessible without paying a ransom. Other malware corrupts metadata as a side effect of its main behavior. Either way, the result on the user’s end is the same: a previously-working drive starts showing RAW status, and the data is logically inaccessible until either the malware is removed or recovery is performed.

Bad sectors hitting metadata regions

When bad sectors develop in the regions of the drive where the file system catalog is stored (the NTFS MFT, FAT directory table, exFAT cluster bitmap), the OS can’t read those sectors and loses access to the partition’s structure. Bad sectors elsewhere on the drive cause file-level read errors but typically don’t trigger RAW status; bad sectors in the metadata regions specifically can take the entire partition offline.⁶

Cross-platform incompatibility

Windows doesn’t natively support Linux’s ext4, macOS’s APFS, or older Mac HFS+ file systems. If you plug a drive formatted on Linux or macOS into a Windows machine, the partition will show as RAW not because anything is broken, but because Windows simply doesn’t speak that file system. The fix in this scenario is to plug the drive back into the OS that originally formatted it; the data is fine. Third-party drivers (Paragon, MacDrive) can give Windows read access to these file systems if needed.

Interrupted formatting or partition operations

If a format or partition resize operation is interrupted (system crash, power loss, force-quit), the file system can be left half-converted. The boot sector may be from the new file system but the rest of the metadata from the old; Windows recognizes neither and labels the partition RAW. This is rarer than power-loss corruption but distinctive in its origin: the drive was working fine before the user-initiated operation began.

Partition table corruption

When the GPT or MBR partition table gets damaged but the partition’s actual file system is still intact, Windows may misread where the partition starts and ends. If it reads from the wrong offset, the file system signature won’t be where Windows expects it, and the partition gets labeled RAW. TestDisk is the standard tool for repairing partition table issues; it can often recover the correct partition geometry without touching the file system itself.

Severe NTFS, FAT32, or exFAT corruption

Sometimes the file system version is correct, but the metadata is so badly corrupted that Windows can’t find a valid signature anywhere. NTFS stores backup copies of its boot sector and MFT; if both copies are corrupted, the partition shows RAW. FAT32 stores two copies of the FAT itself; if both are damaged, same result. The recovery path here is typically file carving rather than file system repair, because the catalog is too damaged to fix.

Recovery from a RAW partition follows a specific order of operations. Skipping any step risks making the data harder or impossible to recover.⁷

Step 1: Stop using the drive

Cancel the format prompt if it’s still showing. Don’t write to the drive. Don’t try CHKDSK yet. Don’t try to repair anything. Every operation against a RAW drive risks damaging recoverable data; the only safe thing to do at this stage is image the drive and work from the image.

Step 2: Image the drive

Create a sector-level disk image of the entire drive before doing anything else. This preserves the current state and gives you something to fall back to if any recovery attempt makes things worse. Tools that work for this:

• ddrescue (Linux, free): the gold standard for imaging from drives that may have bad sectors. Three-pass workflow: fast skip pass, retry pass, then trim pass. Output is a sector-perfect copy of the source drive.
• HDD Raw Copy Tool (Windows, free): GUI tool for sector-level imaging on Windows. Works for healthy drives; less robust than ddrescue when the source has bad sectors.
• Built-in imaging in recovery software (EaseUS, Disk Drill, R-Studio): most modern recovery suites include an imaging feature. Convenient when the recovery software is going to do the recovery anyway.

Step 3: Run recovery against the image

Once you have an image, run recovery software against it. Use Deep Scan or signature-based recovery; not Quick Scan. Quick Scan tries to read the file system catalog, which is the very thing that’s broken on a RAW partition; it won’t find anything useful. Deep Scan performs file carving across the raw bytes of the disk and finds files based on their signatures, ignoring the broken file system entirely.

Recovery tools that handle RAW partitions effectively:

• EaseUS Data Recovery Wizard: automatically falls back to Deep Scan when Quick Scan finds nothing, which is the right behavior for RAW partitions. Polished UI, good preview support.
• Disk Drill: dedicated Partition Recovery mode designed specifically for RAW and lost partitions. Strong signature database for file carving.
• R-Studio: enterprise-grade tool with explicit RAW recovery mode. Handles complex scenarios well; less polished UI but more powerful.
• PhotoRec (free): pure file carving tool, file-system-agnostic by design. Recovers content with generic names but works on any RAW partition regardless of original file system.
• Wondershare Recoverit: mainstream recovery suite with RAW recovery support. Auto-fallback from Quick to Deep Scan.

Step 4: Save recovered files to a different drive

Never recover files back to the same drive they came from. Saving to the original drive risks overwriting other recoverable data that hasn’t been listed in the recovery results yet. Use a different physical drive (external HDD, second internal drive, or another partition on a different drive). For large recoveries, an external HDD is the standard destination.

In some cases, repairing the file system structure is possible and preferable to file carving recovery, because repair preserves file names and folder structure. Repair is only safe to attempt against a disk image, not the original drive; failed repair attempts can make data harder to recover.⁸

When repair is worth attempting

• The file system signature is just slightly damaged, and the rest of the metadata (MFT for NTFS, directory table for FAT) is intact. Repair tools can rebuild the boot sector from a backup copy.
• The partition table is damaged but the file system is fine; TestDisk can rewrite the partition table to point to the correct offsets and the partition becomes mountable again.
• You need original file names and folder structure, and file carving’s generic-name output isn’t acceptable.
• The drive has a complex layout (multiple partitions, dynamic disks, RAID member) that file carving would struggle with.

TestDisk for partition recovery

TestDisk (free, cross-platform, by CGSecurity) is the standard tool for repairing damaged partition tables and corrupted file system signatures. It can rewrite NTFS boot sectors from the backup copy NTFS keeps at the end of the partition, and similarly for FAT32 from its backup FAT. The workflow is text-based but well-documented; running TestDisk against a disk image and letting it search for partitions and rewrite signatures is often the difference between a successful repair and unrecoverable file carving.

CHKDSK with /f flag

Once a partition has a recognizable file system signature again (after TestDisk repair, or in cases where the signature was always intact), CHKDSK with the /f flag can repair file system errors and restore normal access. Run CHKDSK only against an image of the drive, not the original; CHKDSK can make data harder to recover if it fails partway through. The command is straightforward: chkdsk X: /f where X is the drive letter of the imaged partition.

When repair fails: fall back to file carving

If TestDisk can’t find a recognizable file system structure and CHKDSK refuses to run, the metadata is too damaged to repair and recovery has to proceed by file carving instead. The data isn’t lost; the only loss is the original file names and folder organization. Run file carving-based recovery (Deep Scan in any consumer tool, or PhotoRec for free) and accept that recovered files will have generic names.

👥 Researched & Reviewed By

Marcus Whitfield

Data Recovery Software Analyst & Senior Writer

All Articles X (Twitter)

Marcus has evaluated data recovery tools for more than six years across Windows, macOS, and Linux, from free utilities to enterprise-grade platforms. He writes the technical reference content on Data Recovery Fix, with particular focus on the user-facing scenarios where the right initial action determines whether recovery succeeds or fails. RAW partition recovery is the scenario where this matters most, because the obvious user response (clicking Format) is the destructive one.

B.Sc. Computer Science 6+ years data recovery evaluation RAW recovery testing

Rachel Dawson

Technical Approver · Data Recovery Engineer

All Articles X (Twitter)

Rachel brings over twelve years of cleanroom data recovery experience, with extensive hands-on work on RAW partition recovery scenarios across all the typical causes: improper unmount, malware, bad sectors hitting metadata, partition table corruption. Her work spans both file system repair using TestDisk and disk-editor-level reconstruction, and file carving recovery when repair isn’t feasible. She has seen every variant of the user-facing RAW prompt and the conversations that follow.

12+ years data recovery engineering PC-3000 certified RAW partition specialist