RAW drive: avoid formatting if the files matter

For a Windows user in Poland, a RAW message is a frightening kind of half-access: the computer can see the device, but it cannot read the file system. The files may still be present, but the map that points to them - NTFS, exFAT, partition table, boot sector or MFT - is damaged, unreadable or blocked by unstable hardware.

The dangerous moment is the first prompt: "You need to format the disk before you can use it." Formatting is meant to make the drive usable again, not to recover your data. If the disk holds the only copy of documents, photos or company files, click Cancel and stop writes to the device.

RAW on HDD, SSD and external USB drives

The same RAW label does not mean the same failure on every device. On an HDD it may be a weak sector near the file-system metadata. On an SSD it may involve controller state, TRIM or firmware. On an external USB drive the enclosure or bridge board can be the weak point, even if the disk inside is still readable.

This is why the first diagnosis should identify the device type, connection path and behaviour under power. A Warsaw company archive on a USB HDD, an NVMe from a business laptop and a camera card with RAW symptoms need different handling.

Why a drive suddenly becomes RAW

The common triggers are unsafe removal, power loss, a hard reset during writing, damaged partition metadata, MFT corruption, unstable sectors or a controller that stops returning consistent reads. Sometimes the system only sees the symptom after reboot, even though the underlying damage started earlier.

Ask what happened immediately before the message appeared: a dropped laptop, a failed Windows update, interrupted copying, a NAS power cut, BitLocker unlock trouble or a slow disk that kept disconnecting.

RAW is a symptom, not a repair instruction

A RAW volume can come from a logical event, such as a damaged MFT after unsafe removal. It can also come from bad sectors, power loss, a failing USB-SATA bridge, firmware trouble or an SSD controller problem. The same message can hide very different risks.

• HDD: weak sectors can make the file system unreadable.
• SSD/NVMe: TRIM, controller state and firmware behaviour matter.
• External USB drive: cable, enclosure, bridge board and power may be involved.
• Memory card or flash drive: controller and wear can change what tools can read.

If you do not know which case fits, compare HDD recovery, SSD/NVMe recovery and external USB drive recovery before running repairs.

Why formatting and CHKDSK can make things worse

Quick format writes a new file-system structure. CHKDSK can modify indexes, remove orphaned entries and change metadata. On a healthy drive with non-critical data that may be acceptable. On a device you want to recover, it can destroy clues the lab needs.

Tools such as DMDE, R-Studio or Recuva are not automatically unsafe, but the safe professional approach is to work from a sector image. Scanning the original drive when it has read errors may push weak sectors harder and make later imaging more difficult.

• Avoid clicking Format.
• Do not initialise the disk in Disk Management.
• Do not run CHKDSK, "repair disk" or random partition-fix tools on the original.
• Do not save recovered files back to the RAW device.

What you can check without writing to the drive

Basic observation is useful. Check whether the device shows the correct model and capacity, whether it disconnects, whether folders freeze the system and whether the symptom appeared after a power cut, drop or unsafe removal.

1. Take a photo of the exact message.
2. Note the drive model, connection type and capacity shown by the system.
3. Try another cable or port only if the device is stable and quiet.
4. Stop if the drive clicks, slows badly, disappears or blocks the computer.

In a Warsaw business case, also write down whether the drive contains accounting data, project files, encrypted user profiles or a shared archive. That helps choose the priority and the correct diagnostic route.

When RAW becomes time-sensitive

RAW after a sudden disconnect may be mostly logical. RAW combined with freezing, clicking, wrong capacity, CRC errors or disappearing from BIOS/UEFI is more serious. Treat those symptoms as possible hardware failure, not as a file-system setting.

Treat the case as time-sensitive when one of these signals appears.

• The drive disappears from the system or BIOS/UEFI.
• Folders open very slowly or freeze Windows Explorer.
• The disk makes unusual sounds or repeatedly reconnects.
• The computer hangs whenever you try to open the partition.

Related scenarios: drive needs to be formatted, RAW after a power outage and RAW external USB drive.

When to report the storage device to a laboratory

Report the case early if the device contains the only copy of important data, belongs to a company process, freezes the computer, makes unusual sounds or was already scanned by repair tools. Early diagnosis is especially important when the drive holds accounting exports, project archives or documents needed for work in Poland.

A lab can decide whether the first move should be controlled imaging, logical reconstruction, enclosure diagnostics or a controller-level SSD/NVMe approach.

How to prepare a diagnostic request instead of experimenting

Write down the device model, capacity shown by the system, connection type, exact Windows message and what was already tried. If the drive is encrypted, include whether BitLocker, FileVault or another password is involved.

• Device type, model and serial number if you can read it safely.
• Capacity shown by the system and whether the correct model appears.
• Connection type: SATA, USB enclosure, NVMe adapter, NAS bay or memory card reader.
• The exact prompt, error code or message shown by Windows or macOS.
• What was already tried, including CHKDSK, formatting prompts, scans or cable changes.
• Whether encryption, passwords or company user profiles are involved.

Avoid cleaning up the case by formatting, initialising or creating a new partition. A messy but untouched device is usually better than a freshly "repaired" one.

When RAW stops being only a logical problem

RAW may start as a file-system issue, but it stops being a simple logical case when the device disappears, reports the wrong capacity, clicks, disconnects or returns read errors from multiple computers. Those signals suggest unstable media or electronics.

At that point, continuing with home scans can add damage. The safer route is to stabilise the device and image readable areas before rebuilding the file system from a copy.

What to do before recovery

If the data matters, stop using the drive and move to diagnosis. The lab can assess whether the case should start with imaging, controller-level work, logical reconstruction or service of the external enclosure. The fewer writes and failed repairs happen first, the cleaner the recovery procedure usually is.

You can submit the case through the case form, check data recovery price ranges or choose a service page by device type.