HDD now showing as RAW instead of NTFS

Hello all I've currently run into an issue on my bulk storage HDD on my work computer.

I'm running Win 7 Pro with an i7-4790K and an Asus sabretooth mobo. The C: drive is a Samsung 850 pro 256GB and the mass storage drive is a WD Red 6TB.

According to the event log the drive started showing errors a few days ago and this morning it would only let me access certain directories the others all giving me an error code to the tune of drive corruption. I tried some simple things I saw online to no avail such as re-installing the disks drivers or changing the drive letter.

The major problem is the drive is showing up as RAW now so I can't access anything at all and windows wants me to reformat. Can anyone recommend a recovery software to get the data off of this there's close to 4TB of stuff on here that I really really don't want to lose and have to do again as it would take months.

The software can be Linux, Mac, or Windows based I just need to recover this partition. It was just bulk storage not a boot disk of any type.

I'm currently running easeUS on it to see if it will at least find some files.

This is now the 2nd WD Red 6TB that has failed in our office in under a week has anyone had similar bad luck with these drives? The first seems like the internal motor simply won't spin the platters as we can see the drive mounted in Linux but can't access the data on it. Any suggestions for that drive would be appreciated as well.

I don't have personal experience with the larger drives my 2TB reds have been running fine for almost 2 years 24/7 in my nas.
and my 1TB red has been running in my server for just over 2 years.

Looking at reviews, the larger capacities seem to have a lot more failures.

as for a recovery tool, I cant help there.

You can try just plugging it into linux and see what that does.
Do you have a spare 6TB drive?

if so then do this
dd if=/dev/sdaX of =/dev/sdaX -noerrors
if being the bad drive
of being the spare
X being variable between drives use fdisk -l to find your numbers
noerrors meaning that it continues even after an error.
That will basically get the raw data onto a known good drive

You can try swapping the pcb to the other drive you mentioned at the end of the post and see if that will work.

1 Like

I'm running a program called testdisk right now trying to recover the partition table if it fails I'm going to pull the drive and copy it on one of our Linux machines with dd. Our IT guy said hes used it before it just takes forever especially on a drive this large. Thank you so much for the help, I truly appreciate it all.

The longer you delay doing what will work with something that might work lowers the chances of the former actually working