[D5-300] Just lost a 64TB RAID5 array. HELP!

[Jacketbg]

Please help me. I have a D5-300 unit. I initially set it up from MacOS Ventura as a RAID5 setup. 5 x Seagate Exos X18 x 16TB hard drives. All went well and I connected it to my Debian 12 Linux Mini PC. Today I upgraded my Mini PC. I simply swapped the internal NVME, so everything ran well on the PC, but I saw that the TDAS volume is no longer present. Instead, I was presented with 5x16TB separate hard drives. I immediately connected my unit to my Macbook and noticed the same thing. 5 independent uninitialized drives. Also for some reason the Raid Manager does not detect my unit on MacOS. Nothing changed on the unit, it wasn't even power cycled when this happened.

Please help me restore the RAID5 configuration on the unit. I don't want to loose all my data. Any data that I need to send, please let me know.

[Jacketbg]

Here's how Raid Manager looks on MacOS:

Screenshot 2023-07-31 at 17.19.01.png

As you can see there is no entry for deletion of the RAID, but it is practically reset. Please help me get my data back

[Jacketbg]

When I attach the TDAS unit to my Linux server, here's what I get in dmesg:

Code: Select all

[Mon Jul 31 16:39:33 2023] usb 2-4: new SuperSpeed USB device number 4 using xhci_hcd
[Mon Jul 31 16:39:33 2023] usb 2-4: New USB device found, idVendor=152d, idProduct=0576, bcdDevice=71.02
[Mon Jul 31 16:39:33 2023] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Jul 31 16:39:33 2023] usb 2-4: Product: TDAS
[Mon Jul 31 16:39:33 2023] usb 2-4: Manufacturer: JMicron
[Mon Jul 31 16:39:33 2023] usb 2-4: SerialNumber: 202207223AFD
[Mon Jul 31 16:39:33 2023] usb-storage 2-4:1.0: USB Mass Storage device detected
[Mon Jul 31 16:39:33 2023] scsi host3: usb-storage 2-4:1.0
[Mon Jul 31 16:39:34 2023] scsi 3:0:0:0: Direct-Access     ST16000N M001J-2TW113     7102 PQ: 0 ANSI: 6
[Mon Jul 31 16:39:34 2023] scsi 3:0:0:1: Direct-Access     ST16000N M001J-2TW113     7102 PQ: 0 ANSI: 6
[Mon Jul 31 16:39:34 2023] scsi 3:0:0:2: Direct-Access     ST16000N M000J-2TW103     7102 PQ: 0 ANSI: 6
[Mon Jul 31 16:39:34 2023] scsi 3:0:0:3: Direct-Access     ST16000N M000J-2TW103     7102 PQ: 0 ANSI: 6
[Mon Jul 31 16:39:34 2023] scsi 3:0:0:4: Direct-Access     ST16000N M000J-2TW103     7102 PQ: 0 ANSI: 6
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: Attached scsi generic sg3 type 0
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: [sdc] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: Attached scsi generic sg4 type 0
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: [sdd] Very big device. Trying to use READ CAPACITY(16).
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: Attached scsi generic sg5 type 0
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: [sdc] Write Protect is off
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: [sdc] Mode Sense: 47 00 00 08
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: [sdd] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: [sdd] 4096-byte physical blocks
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: Attached scsi generic sg6 type 0
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: [sde] Very big device. Trying to use READ CAPACITY(16).
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: [sdd] Write Protect is off
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: [sdd] Mode Sense: 47 00 00 08
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: [sdf] Very big device. Trying to use READ CAPACITY(16).
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: [sde] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: [sde] 4096-byte physical blocks
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: Attached scsi generic sg7 type 0
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: [sdg] Very big device. Trying to use READ CAPACITY(16).
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: [sdf] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: [sdf] 4096-byte physical blocks
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: [sde] Write Protect is off
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: [sde] Mode Sense: 47 00 00 08
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: [sdg] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: [sdg] 4096-byte physical blocks
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: [sdf] Write Protect is off
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: [sdf] Mode Sense: 47 00 00 08
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: [sdg] Write Protect is off
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: [sdg] Mode Sense: 47 00 00 08
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Mon Jul 31 16:39:34 2023] sd 3:0:0:1: [sdd] Attached SCSI disk
[Mon Jul 31 16:39:34 2023] sd 3:0:0:2: [sde] Attached SCSI disk
[Mon Jul 31 16:39:34 2023] sd 3:0:0:3: [sdf] Attached SCSI disk
[Mon Jul 31 16:39:34 2023] sd 3:0:0:4: [sdg] Attached SCSI disk
[Mon Jul 31 16:39:34 2023] sd 3:0:0:0: [sdc] Attached SCSI disk

[Jacketbg]

Just found a similar thread: viewtopic.php?t=3385
Absolutely the same issue.

If I try to assemble a new RAID5 volume with the Raid Manager, will it destroy all my current data on the disks? I suspect it will, so I'm afraid to do it...
Please if you have any tools that can recover my data, they will be invaluable here.

[TMzethar]

Hello, the RAID5 mode created by the D5-300 through the RAID Manager will not be deleted for no reason. Only if you manually delete the RAID through the RAID Manager, or create a new RAID by other means and replace the computer, will you lose your RAID group.

In addition, D5-300 products have been on the market for more than 10 years, and there is no customer feedback about losing the RAID group mode.

If your data is important, please find a data recovery company to restore the data.
From the information you posted on the forum, we found that you have manually deleted the RAID5 mode record.

[Jacketbg]

I know how it should be in theory, but I have NOT manually deleted the raid group. I simply reconnected the USB cable from one (already shut down) PC to another (while not even booted up). See the attached screenshot carefully and notice the timestamps! The first deletions are when I tested different RAID setups. After that I settled on RAID5 and never even started the Raid Manager app anymore.

[Gremlin]

{L_BUTTON_AT}TMzethar

Looking at the screenshot posted by @Jacketbg it seems to be saying that the last (visible) message is that:

"Raid Controller is unplugged".

I'm not sure how you would achieve that on one of your devices apart from physically dismantling it. [Given that is states it has a HARDWARE raid controller.]