Recover data from dead TS-251+ with RAID-1

[solitone]

My TS-251+ died and I need to recover data from its two HDDs. The disks were set in RAID-1 configuration.

Can I just connect and mount one disk (e.g. the first) to a linux workstation? Is it possible to do that on macOS rather than linux?

Unfortunately backups are not up-to-date, so I can't use them.

Cheers

[albaraky]

I have the same problem!
I bought new nas ts464
And I installed my old drive (two drive in raid 1)
After the system rebuild the drive
The file manager only showed the public folder!!!!

[solitone]

I bought new nas ts464

I don't plan to buy a new NAS.

[FSC830]

I have the same problem!
I bought new nas ts464
And I installed my old drive (two drive in raid 1)
After the system rebuild the drive
The file manager only showed the public folder!!!!

My guess, you did something wrong. If you have followed the NAS migration guidelines, the system should have all shares without any manual interaction.
So yes, most likely just the shares are missing.

Regards

[FSC830]

I bought new nas ts464

I don't plan to buy a new NAS.

If disks are readable at a Linux (no Mac skills here) depends to configuration. If the raid1 was a pool, you are most likely cant access the data.
If the raid1 was a static volume, chances to get access are much better. QNAP did some myteries in the LVM layer which makes it nearly impossible to access data from a pool.

Actually I did never seen a thread/post where someone reports that the could retrive the data out of such a cat2 pool configuration, but many posts claiming, that the raid could be recovered, but not the LVM structure.

Regards

[solitone]

This is what I did on my debian linux PC:

Code: Select all

$ sudo apt install mdadm
$ sudo apt install lvm2

When I connect the HDD via USB, I get the following. The disk is called /dev/sdb, and the data partition is /dev/sdb3, which is automatically assembled to /dev/md1:

Code: Select all

$ sudo fdisk -l 
Disk /dev/sda: 238,5 GiB, 256060514304 bytes, 500118192 sectors
[ ... linux disk details ... ]

Disk /dev/sdb: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: USB 3.0         
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: B8C94A99-5D47-4FC7-8C4D-F30D4D2636F2

Device          Start        End    Sectors   Size Type
/dev/sdb1          40    1060289    1060250 517,7M Microsoft basic data
/dev/sdb2     1060296    2120579    1060284 517,7M Microsoft basic data
/dev/sdb3     2120584 7796248109 7794127526   3,6T Microsoft basic data
/dev/sdb4  7796248112 7797308399    1060288 517,7M Microsoft basic data
/dev/sdb5  7797308408 7814015999   16707592     8G Microsoft basic data

Disk /dev/md1: 3,6 TiB, 3990593142784 bytes, 7794127232 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

Disk /dev/md13: 448,1 MiB, 469893120 bytes, 917760 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

Disk /dev/md9: 517,6 MiB, 542769152 bytes, 1060096 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

Disk /dev/md256: 517,7 MiB, 542834688 bytes, 1060224 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

Disk /dev/md322: 6,9 GiB, 7408779264 bytes, 14470272 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

/proc/mdstat confirms it's RAID-1:

Code: Select all

$ sudo cat /proc/mdstat 
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md322 : active (auto-read-only) raid1 sdb5[0]
      7235136 blocks super 1.0 [2/1] [U_]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md256 : active (auto-read-only) raid1 sdb2[0]
      530112 blocks super 1.0 [2/1] [U_]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md9 : active (auto-read-only) raid1 sdb1[0]
      530048 blocks super 1.0 [24/1] [U_______________________]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md13 : active (auto-read-only) raid1 sdb4[0]
      458880 blocks super 1.0 [24/1] [U_______________________]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md1 : active (auto-read-only) raid1 sdb3[0]
      3897063616 blocks super 1.0 [2/1] [U_]
      
unused devices: <none>

Unfortunately, when I try and mount it I get the error unknown filesystem type 'drbd':

Code: Select all

$ sudo mount /dev/md1 /media/usb
mount: /media/usb: unknown filesystem type 'drbd'.

Is there anything I can do?

[S.Haran]

Unfortunately QNAP uses proprietary versions of some standard Linux tools. That essentially means you cannot use standard Debian Linux to mount a RAID volume that has been QNAPized.

However you may be able to repair your TS-251. Do a search on QNAP resistor fix. If you need help with the fix let me know. I have a bunch of the required 100 ohm resistors laying around.

[solitone]

Support suggested I use R-Linux from the following link: https://www.r-studio.com/free-linux-recovery/

I tested to recover a small folder and it seems to work.