Unraid 6.9.1 data corrupted after component swap

[TachibanaOchiba]

Hi all,

 

I had unraid 6.9.1 running on an E3 1230 v2 platform. It worked fine except that read speed is a bit slow capped at around 30MB/s.

The array has 6 data drives, 1 parity (serial 6KBM), and 1 NVMe cache.

 

One day the Mobo died and I swapped it for a E5  2683v4 platform.

 

After I restarted unraid on the new platform one of the data drive (NVHK) failed.

 

I tested all drives on unraid using badblocks and none of the disks has any bad sectors; All SMART drives also looked fine.

I also extracted the NVHK drive from the unraid server and tested it on a windows based machine, it worked fine.

So I put the NVHK back, and put another drive (V28G) as a second parity and tried to rebuild the array.

 

One night later the webUI indicated that the rebuild was done, but data in the array seemed to be corrupted.

After a server reboot, webUI indicated that the original parity (6KBM) and the corrupted data drive (NVHK) failed.

Data was also corrupted.

 

I tired to remove both V28G and NVHK, but had no luck recovering data.

 

My first priority would be to get the data on the arraies back. Please advise what shall I do.

Thanks.

yamato-diagnostics-20210411-1130.zip

Edited April 11, 2021 by TachibanaOchiba

[JorgeB]

The HBA dropped offline and was re-detected, causing all disks connect there to be inaccessible:

 

pr 11 19:22:48 YAMATO kernel: md: disk1 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk2 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk3 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk5 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk6 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk29 read error, sector=0

 

Rebooting should fix it but it might happen again, make sure it's well seated, sufficiently cooled, you can also try a different slot.

[TachibanaOchiba]

15 minutes ago, JorgeB said:

The HBA dropped offline and was re-detected, causing all disks connect there to be inaccessible:

 

pr 11 19:22:48 YAMATO kernel: md: disk1 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk2 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk3 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk5 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk6 read error, sector=0
Apr 11 19:22:48 YAMATO kernel: md: disk29 read error, sector=0

 

Rebooting should fix it but it might happen again, make sure it's well seated, sufficiently cooled, you can also try a different slot.

Thanks.

 

I had tried to reboot but the array is still corrupt

[JorgeB]

If any rebuild was done after the controller dropping that disk will be corrupt, GUI would show errors on multiple disks, and you'd be notified if system notifications are enable.