7.0.0-Beta.2 - Failed disk with i/o errors

zdonk · September 15, 2024

Hi everyone,

Decided to try my first NAS build with old parts after a desktop upgrade. Hardware for the NAS:

MOBO: B550I AORUS PRO AX (rev. 1.3)

BIOS: Flashed to [FFc] 2024-09-04

CPU: Ryzen 3700X

RAM: Corsair Vengance LPX 2x16GB

Storage: 3 x 18TB Seagate Ironwolf Pro; 2 x 2TB Crucial MX500 SATA; 1 x 500GB Gigabyte 500GB AORUS Gen4 m.2 nvme;

GPU: Intel Arc A380

PCIE Riser Card: PCIE 4.0 Channel Splitter Expansion Riser Card 8+4+4Hyper M.2 NVMe

M.2 to SATA: M-Key PCI Express To SATA 3.0b Expansion Card Adapter

The motherboard with mitx form factor only has 4 sata ports and 1 pcie x16 slot. So to expand these i purchased a cheap m.2 to sata expansion card from aliexpress.

This is connected with the pcie 4x4x8 lane splitting riser card which gives me expansion of 2 extra m.2 slots. So i had the ssd's plugged into the mobo onboard sata ports and hdd's pluggined into the m.2 card sata ports.

As this is just a side project for me, it's only set up as media server with no critical data stored to it as yet. Decided to run beta 7 for the native intel gpu driver support.

Initially when I managed to set everything up things seemed to be running fine for maybe a week. Then one morning i woke up to see a notification with a failed disk drive and the drive showing as disabled in unraid dashboard, this was the parity drive, data drives were ok at the time. These were showing as disk write errors in the logs.

Tried to do as much research as possible to diagnose and troubleshoot. From reading some of the logged errors and googling, I thought maybe it came down to bad sata cable. Tried to rebuild the parity drive via the stop array > unmount drive > start > stop > mount > start process. But this kept failing for similar issues.

So unplugged everything, plugged the parity drive into the onboard sata ports, data drives connected to the m.2 sata card. Started everything up and managed to rebuild the parity drive. Things ran fine for a couple days and got the same issue but this time on disk1 data drive. Tried different troubleshooting steps, different sata cable, different sata ports etc, but it kept failing during the rebuild process with i/o errors and disk read errors.

So then thought maybe it's due to issues with the pcie 8x4x4 bifurcation card. So next i tried connecting the m.2 to sata card to the second onboard m.2 slot on back of the motherboard. But this failed during rebuild again with similar read errors, I/O errors in the syslogs. But I'm now suspecting issue possibly to be with the cheap m.2 to sata card. So i have a new Silverstone one on order which I'll replace and try out in a couple days when i get it.

Until then I'm hoping someone could help me with diagnostics reports and see if there are other things i should be looking at or trying?

Have attached the last diagnostic 2 reports, first one is from today when it initially failed with Buffer I/O errors during parity sync. In the diagnostic report smart files I suspect that it wasn't able to detect the drives at all:

Smartctl open device: /dev/sdf failed: INQUIRY failed

Smartctl open device: /dev/sde failed: INQUIRY failed

After a reboot (second diagnostic report), smart file has contents in it, so it was able to detect the drives. This what lead me to think that the issue is with the m.2 sata card.

But would appreciate any other help or insights anyone is able to give me. Not sure what other things it may be related to or i should be looking at. I have additional diagnostics reports I generated through various stages of the troubleshooting over the past week if needed as well.

Thanks so much for any help of guidance

jonsbo-diagnostics-20240915-1414.zip jonsbo-diagnostics-20240915-1500.zip