How to Convert RAW to NTFS Without Losing Data?

#1 · February 12, 2026, 9:38 am

Hey everyone,
I’m hoping for some guidance. I have an external hard drive that suddenly now shows up as RAW( RAW drive shows in Disk Management but won’t open).
This drive used to be NTFS and it has… or had a lot of important data on it. From what I understand, I’m dealing with a RAW partition/RAW volume. Windows keeps suggesting formatting it,but obviously I don’t want to do that. How to convert RAW to NTFS without losing data? Please help!

#2 · February 12, 2026, 9:52 am

You can’t really convert RAW to NTFS without data loss. RAW is not a file system. It just means Windows can’t recognize the file system that used to be there (NTFS in your case). Once a drive shows as RAW, the NTFS structures Windows relies on are already damaged (or missing). There’s nothing for Windows to “convert” at that point.

So realistically you need to recover your data from tthat drive first using proper RAW disk recovery software (i’d suggest Disk Drill). Just scan your drive with it, and after your data is saved somewhere else, format the drive and create a fresh NTFS file system. Copy your data back if the drive turns out to be healthy (you can check its health in the same Disk Drill [SMART monitoring in main menu] - a drive that suddenly turns RAW sometimes has underlying issues, not always though, could be a one-off file system corruption).

webdev_blog and shieran have reacted to this post.

#3 · February 12, 2026, 10:09 am

Hello @shieran, welcome to our forum 👋

Our team already has a step-by-step guide that walks through this exact situation.

👉 How to сonvert RAW to NTFS without losing data (this guide)

The guide covers all realistic paths, including when not to try a fix and recover first. Specifically, it explains:

What a RAW partition / RAW drive actually means
Why does NTFS turn RAW in the first place (power loss, unsafe removal, controller errors, bad sectors, etc.)
Which fixes are safe
How to use data recovery tools correctly before formatting
How DiskPart RAW partition commands work
Command Prompt disk repair options
PowerShell disk commands and what they can/can’t do

Most “RAW to NTFS without formatting” advice online is either outdated or dangerously incomplete. The guide focuses on preserving recovery chances first, then fixing the file system the right way.

If you’re unsure which path applies to your drive, start with this guide before running any commands.

shieran has reacted to this post.

#4 · February 12, 2026, 11:53 am

Thanks everybody for the tips, really appreciate it. I’ll try it.

@DataRecoverExpert I opened the SMART info and it shows “Good” with a bunch of parameters. That means my drive is actually fine right? Then why would it suddenly turn RAW in the first place??

#5 · February 12, 2026, 11:54 am

I’ve had a couple cases where CHKDSK brought a RAW drive back to NTFS. If the damage is minor it can sometimes rebuild the file system.

If you want to try it, this is how you do it:

(1) Open Command Prompt as Administrator

(2 ) Type: chkdsk X: /f (Replace X: with the drive letter of the drive as shown in Disk Management)

(3 ) Press Enter and let it run

#6 · February 12, 2026, 12:19 pm

@JustMike Nah if the volume is RAW CHKDSK won’t even start. In most cases it just throws “CHKDSK is not available for RAW drives” .

CHKDSK needs a recognizable file system. On a RAW volume, those structures are already gone or unreadable, so there’s nothing for CHKDSK to repair. Just check this Reddit thread where multiple people tried the same thing and hit the exact same wall.

#7 · February 12, 2026, 12:19 pm

@JustMike You’re mostly right - in the majority of cases, if a volume shows up as RAW, CHKDSK won’t even start.

That said, there are a few edge cases where it's not true.When a drive that was NTFS becomes RAW because the NTFS boot sector is damaged, the rest of the file system might still be intact. NTFS keeps a backup boot sector, and in those situations CHKDSK may be able to rebuild the primary boot sector from the backup and make the volume mountable again.

So if the damage is limited to the NTFS boot sector and the backup is healthy, CHKDSK CAN restore the file system. But that’s a best-case scenario. If the data on the drive is important, I’d never run CHKDSK first. Data recovery is still the safest approach.

#8 · February 12, 2026, 12:23 pm

Quote from shieran on February 12, 2026, 11:53 am

Thanks everybody for the tips, really appreciate it. I’ll try it.

@DataRecoverExpert I opened the SMART info and it shows “Good” with a bunch of parameters. That means my drive is actually fine right? Then why would it suddenly turn RAW in the first place??

If it says “Good” it usually means the drive itself is fine. But SMART only tells you about the physical side of things.

RAW doesn’t mean hardware failure- most of the time just means file system corruption. NTFS is a logical layer, and when that layer gets damaged Windows can’t read it and marks the volume as RAW.

shieran has reacted to this post.

#9 · February 12, 2026, 12:24 pm

@nikaredko I looked through the guide, thanks! It mentions Testdisk. If I understood it correctly, it can convert RAW partition to NTFS without losing data by fixing the file system. Is that safe for my files?

Has anyone here tried Testdisk on RAW drives? I downloaded it, but I can’t really make sense of it yet.

#10 · February 12, 2026, 12:41 pm

@OP Sometimes, yes. But with a big asterisk. TestDisk can work on RAW drives in specific cases- mainly when the issue is limited to damaged NTFS boot sector, broken partition table, that sort of thing. In those scenarios it may make the partition mountable again without losing data.

The catch is that TestDisk is a low-level tool. It doesn’t hold your hand and if you pick the wrong options, it can make things worse. That’s why many people skip it. If the data matters, I’d suggest doing the same. skip TestDisk and use something more forgiving and universal, like Disk Drill, R-Studio, or a similar capable freemium recovery tool.

#11 · February 12, 2026, 12:42 pm

You could try Recuva. It’s free and pretty easy to use. I used it on an external drive not that long ago when it went weird on me. Not everything came back perfect (few files recovered but wouldn’t open ) but the important stuff was fine.

#12 · February 12, 2026, 12:59 pm

Quote from Ryan404 on February 12, 2026, 12:42 pm

You could try Recuva. It’s free and pretty easy to use. I used it on an external drive not that long ago when it went weird on me. Not everything came back perfect (few files recovered but wouldn’t open ) but the important stuff was fine.

@Ryan404 Recuva is a pretty poor fit for RAW drives. It doesn’t really handle RAW - it needs working partition. Even on Recuva’s own official community threads, their team points out that Recuva isn’t designed for RAW disk recovery.

#13 · February 12, 2026, 12:59 pm

@DataRecoverExpert I figured TestDisk isn’t really my kind of software, I skipped it.

I’m trying Disk Drill now. It’s currently scanning the drive. One question though: in the guide it says it’s better to create a byte-to-byte backup first and then scan the backup. I didn’t do that and started the scan on the drive directly.

Did I mess up by skipping the backup step? Should I stop the scan and start over?

#14 · February 12, 2026, 1:01 pm

@shieran You should be fine. Since your SMART status looks good, there’s no reason to stop and start over. The byte-to-byte backup is mainly critical when a drive is flaky (disconnecting or clearly degrading). In those cases imagingfirst protects you from the drive dying mid-scan.

If your drive is stable, scanning the drive directly is OK. Just let the scan finish, recover your files to a different drive, and you’re good.

#15 · February 12, 2026, 2:44 pm

Just wanted to update the thread. Drive is NTFS again!!!!

Thanks everyone for the help, especially @DataRecoverExpert. The scan took a while and I had to free up a LOT of space on my main drive to save everything from the external one. Also ended up buying the Pro license to recover ALL files, not gonna lie that part stung a bit. But I got all my files off, formatted the external drive back to NTFS, copied everything back, and it’s working fine again.

Fingers crossed that’s the end of my troubles for this week

Thanks again everyone!