How to restore RAW to NTFS file system

I'm not entirely sure how it happened, but the drive I use for photos now shows (in Disk Management) to have a RAW files system instead of the expected NTFS.  Windows 10 does not recognize RAW file system, so I can see no files on the 4T drive.  My guess the problem occurred when I changed the drive letter in Disk Management.  I do have several backup drives containing most of the unprocessed CR2 files, so I'm not quite in tears.  But, ....

I Googled the issue and find a wide range of suggestions, mostly from folks wanting to sell their recovery program.  Does anyone have experience with such an issue?  I'm willing to spend some money for a reliable program, but I hopeful someone will be able to offer me some unbiased advice.

Check that again, there is no such thing as a RAW file system. Please post a screen shot of your Disk Management screen...

Also, I'm assuming you tried a reboot already...

E.J. Peiker wrote:Check that again, there is no such thing as a RAW file system.  Please post a screen shot of your Disk Management screen...

Also, I'm assuming you tried a reboot already...

Always reboot first! Now, all is well. It looked like the computer ran Chkdsk when it boot up.

Thanks again EJ for you invaluable help. In this case, at least $40 for one of the programs that I saw advertised to address my RAW problem.

I searched google for Windows 10 raw partition

https://www.google.com/search?client=sa ... 8&oe=UTF-8

It came back with this

https://www.m3datarecovery.com/raw-to-n ... ws-10.html

The title of the article seems good. You might want to read through several articles and then decide on an approach.

Anthony Medici wrote:I searched google for Windows 10 raw partition

https://www.google.com/search?client=sa ... 8&oe=UTF-8

It came back with this

https://www.m3datarecovery.com/raw-to-n ... ws-10.html

The title of the article seems good. You might want to read through several articles and then decide on an approach.

Rebooting solved the problem. I din't want to do anything that might do something unwanted, so i did not renoot until suggested by EJ. 

Chalk it up for now, to some confused electrons.

E.J. Peiker wrote:Chalk it up for now, to some confused electrons.

And to a confused operator...

My guess that the issue resulted from me changing with Disk Management the name of the drive letter of that drive from W: to F:.  Interesting, the other drive (the one that was already named F:) was not affected when I changed its name to K:.

I've changed drive letters like that hundreds of times and never had that happen - weird science!