Nas Died, Issues recovering data

[KD5NSS]

I have a TS-653 pro that died. Spent 2 days on the phone with the help desk, and will be sending box in for repair. In the meantime we are trying to access the data stored on the nas. It had 4 wd red 2TB drives in raid 5. I have plugged all of the drives into a machine running linux. All disks pass SMART, and show in good health. I attempted to mount the raid volume with mdadm unsuccessfully. I discovered that at least 3 of the drives have corrupted partition tables. 3 of the drives (/dev/sd[a.b.d]) show up like this example after fdisk.

Code: Select all

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00001c20

Device     Boot Start     End Sectors   Size Id Type
/dev/sda1          40 1060289 1060250 517.7M 83 Linux

The third like this

Code: Select all

Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BCDF9FC6-E5DE-436A-A18C-E0328FFCCCE7

Device          Start        End    Sectors   Size Type
/dev/sdc1          40    1060289    1060250 517.7M Microsoft basic data
/dev/sdc2     1060296    2120579    1060284 517.7M Microsoft basic data
/dev/sdc3     2120584 3889240109 3887119526   1.8T Microsoft basic data
/dev/sdc4  3889240112 3890300399    1060288 517.7M Microsoft basic data
/dev/sdc5  3890300408 3907007999   16707592     8G Microsoft basic data

using TestDisk, I have verified the partitions are still there, and the data in the partitions readable, but without a clear picture of what the partition tables are supposed to be, I am at a loss for how to repair the tables. any help would be appreciated, as I really need to recover this data that is important to my business. I know, should have had a backup (shoots self in foot.) below is a sample of testdisks analysis of /dev/sda as an example.

Code: Select all

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/sda - 2000 GB / 1863 GiB - CHS 243201 255 63
     Partition               Start        End    Size in sectors
 D MS Data                       40    1060263    1060224
>P Linux Raid                    40    1060271    1060232 [9]
 D Linux Swap               1060288    1060303         16
 D Linux Raid               1060296    2120559    1060264 [6]
 D Linux Raid               2120584 3889239823 3887119240 [1]
 D MS Data                 16390336 3860379839 3843989504 [Backup]
 D MS Data               3889240112 3890010159     770048
 D Linux Raid            3889240112 3890157879     917768 [13]
 D Linux Swap            3890300400 3890300415         16
 D Linux Raid            3890300408 3907007871   16707464 [321]



Structure: Ok.  Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
                P=Primary  D=Deleted
Keys A: add partition, L: load backup, T: change type,
     Enter: to continue
md 1.x L.Endian Raid 1 - Array Slot : 7 (0, failed, failed, failed, failed, 5

[dolbyman]

you might want to wait for the new device (or buy a new one) or pass the drives to a data recovery service , because you still need to deal with lvm after you got the mdadm part figured out

[MrVideo]

The use of a data recovery service will cost you more than buying a new NAS (same model). Then when you get your NAS back, load it with drives and use it as a backup.

And if you do not have a UPS for the NAS, be sure and get some of those as well.