How to access data on eSATA stored as RAID 1

shepaldo

Commendable
Feb 2, 2017
1
0
1,510
Hi everyone,

I have a QNAP NAS drive and have installed 2x2TB Hitachi eSATA drives arranged as RAID 1. Something happened recently (not sure what...) and the NAS stopped communicating over the network. Further investigation with the QNAP team confirmed that one of the eSATA drives has failed (makes a clicking noise and is unreadable) and the other "has some IO issues". Something must also have happened within the NAS unit as for some reason the IP address changed, although the QNAP guys say it is all OK now.

Anyway, in an effort to see if I can recover at least part of the data from the second eSATA drive, I have purchased an eSATA to USB adapter cable. When I connect up to the eSATA drive, the disk is not visible within My Computer, but is visible within My Computer > Management > Disk Management as a series of partitions within the Disk. I am unable to assign a letter to the partitions. The disk is visible using cmd > diskpart > list disks. But it is not visible using cmd > diskpart > list volumes. The disk is also visible within Control Panel > System and I have checked that the drivers are all up to date.

I have two laptops one with Windows XP and the other with Windows 10.

Any ideas? Thanks!
 
Solution
Hi there,
QNAP's use Reiser/XFS File System. You can try UFS Explorer to read a Reiser drive and as you seem to know, this won't work if both drive are not responding or have some damage.

Anyway, the safe approach here would be to image drives first and work on the file system problem afterwards.

MHDD is a free tool that could diagnose the problem with your drives.
If you know how to use Linux, ddrescue can image drive backwards (avoid cache issue and limitation), essential when it comes to recovery.

Hope this helps.


John7128

Commendable
Feb 5, 2017
46
0
1,560
Hi there,
QNAP's use Reiser/XFS File System. You can try UFS Explorer to read a Reiser drive and as you seem to know, this won't work if both drive are not responding or have some damage.

Anyway, the safe approach here would be to image drives first and work on the file system problem afterwards.

MHDD is a free tool that could diagnose the problem with your drives.
If you know how to use Linux, ddrescue can image drive backwards (avoid cache issue and limitation), essential when it comes to recovery.

Hope this helps.


 
Solution