HELP! - Disk Missing Marked as RAW

[bzowk]

Hey Guys - 

I have a big issue I need help with, please.

I've used DrivePool without major issue for a couple of years now.  My pool is run in Windows 10 x64 and consists of 10 disks including an SSD.  About an hour ago, I got some malware which I had to clean off using Malwarebytes in safe mode - nothing larger than quarantining files and restarting.  Once done, I got alerts that a disk was missing from my pool.  I've run into this issue previously if a cable is loose but after reseating everything and powering back on, I noticed that the disk is present.

This specific disk is one I had two NTFS partitions on.  One was used for the pool and the other for backups.  The backups partition still shows as NTFS in Windows and works fine so I know the hardware seems ok.  The other partition used for the pool is now labeled RAW in Disk Management, though. (see screenshot)

Any suggestions you have for how to resolve this and retain data would be invaluable.  Thanks!

[bzowk]

UPDATE

I ran chkdsk against it without "/f" and got results stating:

The type of the file system is NTFS.

The first NTFS boot sector is unreadable or corrupt.

Reading second NTFS boot sector instead.

 

I ran with a "/f" and it recovered it to NTFS.  Restarting the DrivePool service kicked it back into the pool as well.

 

Now the big question:  Is this usually a software issue that causes this to occur or is it due to hardware failure?  I had Scanner working and it was checking during last status, but currently not reporting any SMART errors.  I'm afraid to scan it again as if hardware i don't want to make the issue worse, yet want to verify it if still good - know what I mean?

 

Below's the result from chkdsk /f:

C:\WINDOWS\system32>chkdsk j: /f

The type of the file system is NTFS.

The first NTFS boot sector is unreadable or corrupt.

Reading second NTFS boot sector instead.

Volume label is Disk 13.

 

Stage 1: Examining basic file system structure ...

  751616 file records processed.

File verification completed.

  2425 large file records processed.

  0 bad file records processed.

 

Stage 2: Examining file name linkage ...

  1486 reparse records processed.

  927082 index entries processed.

Index verification completed.

  0 unindexed files scanned.

  0 unindexed files recovered to lost and found.

  1486 reparse records processed.

 

Stage 3: Examining security descriptors ...

Security descriptor verification completed.

  87734 data files processed.

CHKDSK is verifying Usn Journal...

  1208077872 USN bytes processed.

Usn Journal verification completed.

 

Windows has made corrections to the file system.

No further action is required.

 

   3765317 MB total disk space.

   3721416 MB in 411211 files.

    325552 KB in 87735 indexes.

         0 KB in bad sectors.

   2116455 KB in use by the system.

     65536 KB occupied by the log file.

  42513400 KB available on disk.

 

      4096 bytes in each allocation unit.

 963921407 total allocation units on disk.

  10628350 allocation units available on disk.

 

Thanks

[Christopher (Drashna)]

You posted this in a ticket, as well.

You should be safe to run CHKDSK on the system, and that may recover the partition, in most cases.

If not, then you may need to run something like TestDisk or Recuva to regain access of the drive/data.