Hard Drive or SSD Turned RAW? Don’t Click Format! (Free Fix with TestDisk)
Windows says the disk “needs to be formatted”, but your files are usually still there. Step by step with TestDisk (free and open source) to rebuild the partition table and the boot sector — plus plan B with PhotoRec.
The rescue in 5 lines:
- Don’t format and don’t save anything to the RAW drive — that’s what makes the recovery possible.
- RAW usually means the partition table or boot sector got corrupted; the data itself is still on the disk.
- TestDisk (free): Create → pick the disk → Analyse → Quick Search → press P to list files → Write.
- If the list fails: Advanced → Boot → Rebuild BS rebuilds the boot sector.
- Plan B: PhotoRec (same package) extracts the files to another drive, even without the partition table.
- What is RAW?
- Before Anything Else
- Confirming That the Drive Really Is RAW
- When TestDisk Is NOT the Solution
- Downloading TestDisk
- Starting the Rescue: Understanding the “Black Screen”
- The Trick: Rebuilding the Boot Sector
- If TestDisk Can’t Rebuild the Table
- Common Errors and How to Fix Them
- After the Recovery
- Frequently Asked Questions
💾 What Really Happened to Your Drive
You plug in the external drive, USB stick or SSD and, instead of your work folders or family photos, Windows throws the classic, terrifying message: “You need to format the disk in drive E: before you can use it.” Or you open Disk Management and see that the partition has lost its file system (NTFS, exFAT or FAT32) and now shows up bare, as RAW.
What got corrupted is the drive’s “index” — the partition table and the boot sector, the map that tells the operating system where each partition and each file begins and ends. It happens when a cable is unplugged at the wrong moment, after a power cut, or because of a logical system failure. Windows has simply lost the map and no longer knows where your data blocks are — so it panics and asks you to draw a brand-new map from scratch (that is, format).
The good news: in the vast majority of RAW cases caused by a logical failure, the data is still physically intact on the disk. Only the index pointing to it is gone. That index is exactly what we’re going to rebuild.
⚠️ Before Anything Else
This also covers the basics people overlook: don’t use that same drive to save downloads, don’t create new folders on it “just to test”, and never install recovery programs directly onto the problem drive. Download and run the tool from the drive where Windows is installed.
And one very common mistake: don’t run CHKDSK on a RAW drive. Windows itself refuses (“The type of the file system is RAW. CHKDSK is not available for RAW drives.”), and forcing “fixes” on a drive with a broken structure can make things worse. My guide CHKDSK: when to use it and when NOT to explains why.
🔎 Confirming That the Drive Really Is RAW
Before starting, confirm the diagnosis in 30 seconds — without writing anything to the disk:
| Where to look | How | What indicates RAW |
|---|---|---|
| Disk Management | Win + X → Disk Management (or diskmgmt.msc in Win + R) | The partition shows RAW in the file system column |
| PowerShell | Get-Volume | The volume appears with an empty or Unknown FileSystemType, or listed as RAW |
| File Explorer | Double-click the drive letter | The “you need to format the disk” message |
If the drive doesn’t show up anywhere — not even in Disk Management — the problem is different, and so is the path: see the next section and my guide on an external drive that is no longer recognized.
🔍 When TestDisk Is NOT the Solution
It’s important to tell two very different scenarios apart before starting, because one of them can’t be solved with software:
| Sign | Likely cause | What to do |
|---|---|---|
| Drive shows up, but as RAW | Logical failure in the partition table | TestDisk solves it — follow this guide |
| Drive doesn’t appear anywhere (not even in Disk Management) | Could be the electronics, the cable or the connector | Try another cable/port before any software |
| Clicking, scraping, or the motor doesn’t spin | Physical mechanical failure (common in hard drives, not in SSDs) | Turn it off immediately and look for professional clean-room recovery — keeping it powered makes the damage worse |
| SSD not detected after a power cut | Possible internal controller failure | TestDisk may not help; consider specialized recovery |
If you want to know whether the drive itself is healthy before trusting it again, run the 4 commands that reveal your PC’s real health.
⬇️ Downloading TestDisk
TestDisk is a free, open-source tool maintained by CGSecurity, and it’s what I use day to day on the workbench to rebuild corrupted partition tables. Download it straight from the official source: cgsecurity.org — TestDisk & PhotoRec (100% free, no affiliation, no paid version).
- Download the Windows 64-bit version.
- Extract the .ZIP to a folder on the Windows drive (never onto the RAW drive).
- Right-click testdisk_win.exe and choose Run as administrator. Without that, the program isn’t allowed to read the hardware at a low level.
🛠️ Starting the Rescue: Understanding the “Black Screen”
Make sure the corrupted drive is firmly connected. Avoid cheap USB hubs at this point; plug it straight into the motherboard (a rear USB port on a desktop) to guarantee clean power and communication.
When you run TestDisk as administrator, you’ll face a black command-prompt-style screen. Don’t be scared — this rustic interface is what lets the software bypass Windows’ locks and talk straight to the hardware. Use the arrow keys to move and Enter to confirm.
| Step | Screen | What to choose |
|---|---|---|
| 1 | Log file | Create — just records a history of what you do |
| 2 | Disk list | Your corrupted drive, identified by size (GB/TB) and brand → Proceed |
| 3 | Partition table type | The option TestDisk pre-selects: usually Intel (older/MBR drives) or EFI GPT (modern drives) |
| 4 | Main menu | Analyse → Quick Search |
| 5 | Partitions found | Select the lost partition and press P to list its files |
| 6 | File list OK? | Q to leave the list → Enter → Write → confirm with Y |
About step 4: if the quick search shows nothing in green, or the right partition isn’t there, don’t panic. TestDisk offers Deeper Search, which scans the drive sector by sector. It takes much longer, but it finds partitions given up for dead.
About step 5: the found partition usually appears highlighted. Don’t press Enter right away — press P. If your folders, photos and documents appear: bingo, the data is there, intact, and Write saves the repaired map back to the disk.
🔥 The Trick: Rebuilding the Boot Sector
What if you pressed P and got an error saying the file system is damaged, or the partition simply lists nothing? That’s where the workbench secret comes in. The problem may not be the whole table, but only the boot sector of that specific volume. Let’s force the rebuild:
- Press Q until you’re back at TestDisk’s main menu.
- Instead of Analyse, choose Advanced.
- Select the problematic (RAW) partition and go to Boot at the bottom of the screen.
- If the next screen says “Boot sector: Bad”, we found the villain. Select Rebuild BS and press Enter.
- TestDisk recreates that vital piece from scratch, based on the file system’s own information. At the end, choose Write to save the fix and close the program.
On NTFS partitions there’s often a shortcut: if the backup boot sector is healthy, TestDisk shows the Backup BS option, which copies the backup over the damaged main sector.
🧩 If TestDisk Can’t Rebuild the Table
Sometimes the corruption is too extensive to rebuild the partition table — even with Deeper Search and Rebuild BS. That’s not the end of the road: the TestDisk package ships with PhotoRec, a sister tool that works in a completely different way.
Instead of trying to fix the map, PhotoRec ignores the partition table entirely and scans the disk byte by byte, recognizing the characteristic headers of each file type (a JPEG photo, a PDF or an MP4 video have their own signatures at the start of the data). It then extracts those files, one by one, to another drive.
| TestDisk | PhotoRec | |
|---|---|---|
| What it repairs | The partition table and boot sector | Repairs nothing — it copies files out |
| Original names and folders | Kept (the drive comes back as it was) | Lost: files come out as f0001234.jpg in numbered folders |
| When to use it | First attempt | When TestDisk fails or the drive was formatted |
| Where the data goes | Stays on the same drive | Always to another drive |
It’s laborious to organize afterwards, but it’s often the last line of defense before paying for professional recovery. For accidentally deleted files (a different problem from RAW), see my full guide to recovering RAW or corrupted drives.
🔧 Common Errors and How to Fix Them
| Problem | Solution |
|---|---|
| Drive doesn’t even appear in TestDisk’s list | Try another cable and another USB/SATA port. If it persists, it may be a hardware failure — see “When TestDisk is NOT the solution” |
| Quick Search doesn’t find the partition | Use Deeper Search — slower, but more thorough |
| Boot sector still “Bad” after Rebuild BS | Restart the process choosing the other partition table type (Intel/EFI GPT), or consider that there may be physical damage |
| Write doesn’t save / permission error | Make sure TestDisk was run as administrator from the start |
| After Write, Windows still asks to format | Restart the computer completely and reconnect the drive to another port before testing again |
| The process freezes or is very slow | Normal on large drives during Deeper Search — it can take several hours. Avoid interrupting it |
✅ After the Recovery
Once you’ve written the fix (Write) and restarted the computer, your drive should be recognized by Windows again, with its drive letter in This PC and all data intact, just as it was before the failure.
- Copy everything immediately to another drive or to the cloud — today, not later.
- Check the drive’s health: a drive that suffered logical corruption once is more likely to repeat it, especially if S.M.A.R.T. shows wear. The 2-minute SSD test helps.
- Only then, with the data safe, is it worth running CHKDSK on the recovered drive to tidy up the file system.
- Don’t trust that drive as your only storage from now on.
FAQ
Does TestDisk work on Mac and Linux too?
Yes, it’s cross-platform. The logic of the steps is the same; only the way you run the executable changes on each system.
Is it safe to run it on the drive where Windows is installed?
The tool itself is safe, but extra care is needed: if you select the wrong drive in step 2 and write changes to it, you can damage the operating system itself. Always confirm by size and manufacturer before proceeding.
How long does Deeper Search take?
It depends on the size of the drive — from a few minutes to several hours on multi-terabyte drives. Let it run without interrupting.
Does TestDisk recover files I deleted by accident?
That’s a different problem from RAW. Deleted files (even from the Recycle Bin) are better handled by PhotoRec, which comes in the same package, or by software made specifically for deleted files.
Is it really free, with no catch?
Yes. TestDisk and PhotoRec are open-source projects maintained by CGSecurity, with no paid version and no feature limits.
Can I run CHKDSK to fix a RAW drive?
No. Windows itself says CHKDSK is not available for RAW drives, and forcing repairs before rebuilding the structure can make recovery harder. Use CHKDSK only after the data is safe.
Does it work on USB sticks and memory cards?
Yes. TestDisk and PhotoRec work with hard drives, SSDs, USB sticks and SD cards, as long as the device is recognized by the computer.
What should I do after recovering?
Copy everything to another drive or to the cloud immediately. A drive that has shown logical corruption once is more likely to repeat it — don’t use it as your only storage.
🎮 How much did you learn?
Once you pick an answer it locks in — reload the page to try again.
1. What should you NEVER do with a drive that turned RAW?
2. What usually gets corrupted when a drive turns RAW?
3. Which TestDisk key lists the files of a found partition?
4. Which option rebuilds a damaged boot sector?
5. Where does PhotoRec save the recovered files?
Esse conteúdo ajudou você?
Compartilha com alguém que também vai curtir — é rapidinho e ajuda muito o nosso trabalho a chegar em mais gente.
Conhecimento só tem valor quando compartilhado.
Manter essa estrutura de laboratórios funcionando e produzir conteúdos de engenharia de forma totalmente gratuita e acessível exige tempo e dedicação diária à bancada. Esse guia salvou os seus arquivos? Você pode contribuir diretamente para manter o nosso trabalho independente forte. Apoie doando qualquer valor!
Quer apoiar a nossa bancada independente?
[email protected]
