FourH3ad

Hey All, It all seems to be in order. It went through parity check. Today I installed a new motherboard and everything is still working. I will keep this open for a couple days just in case but this is most likely solved by getting a new motherboard.

New cables finally arrived after delay. Parity is currently running with all drives connected through hbas. I ended up doing a memtest but found no errors. So here's hoping it's the motherboard lol. Otherwise the only part left is the cpu but I highly doubt this can be the issue. Also I have no idea why memtest says slot 2 and 3 for my ram they are inserted correctly. (Old photo so no these sata cables aren't there anymore)

I have not. However xmp/expo is disabled and the ram is running at its native speed, so I'm not quite sure if this can cause the issue. I will keep this in mind though. Thanks!

No splitters are in use currently. Before changing the psu i did have them. Current plan is as follows. Grab an extra hba card i have and swap out the nic for this one. (no spare pcie ports left) Connect all 8 drives to the two hbas with current sata cables. If no problems then it's the motherboard controller. If problem is still there it could still be the cables and i replace those. (i ordered them this morning so they should arrive tomorrow). Thanks for looking into my problem. I will report back. Edit: I'm going to have to wait for the new cables as the current ones aren't long enough to reach the hba

Hello all, I must say i have no idea anymore. I've been battling server issues for a good 2 weeks now. Started out innocent enough, a read error on the array. Fair enough you know maybe a bad drive no problem. I changed the drive reran parity and boom read errors again. Hmm well ok maybe it's the sata cable. Changed that and plugged this drive into my sata hba, same issue but now the server also reboots. Alright maybe a power supply issue as i did use a splitter. Installed a new powersupply 1000 watts very much overkill using 4 sata psu cables to all different drives. Once again read errors during parity. No reboot this time though so that's good news i suppose? Almost every time tho it's a different drive thats throwing these errors. Always starts with emask 0x0 0x6 And it tries to soft and hardreset the sata link. This however fails and puts the drive in the disabled state. Well ok maybe its a filesystem issue so i said F it and wiped the filesystem by using the "new config" feature in unraid keeping my ssd pool config. These btw have not thrown an error once only the actual array devices seem to have this issue. Changed my filesystem to zfs as well to see if this makes a difference. Sadly yet again the same emask error but this time on 2 disks at once. I attached all my diagnostic logs during the entire "adventure". Hopefully someone can pinpoint me in a good direction. I have ordered 6 new sata cables to sanity check myself and i will do a memtest on the ram once i'm home later today. My last idea is the motherboard? Before this all started i did not have any array device connected to my non-raid sata hba only the two ssd pool devices. All of them were connected directly to the motherboard. HDD temperatures are fine all in the low to mid 30s. These read errors are likely a followup error from the emask errors. The emask errors always appear during the parity rebuild. It has succesfully done the rebuild once. This was straight after changing the psu This is when i updated unraid to 7.2.2 since i felt that the issue was fixed. Then i tried to put the original "broken" 20tb drive back in and once again it spits out the same errors. Fair enough maybe it actually is defective so i remove it and put the known good 4tb drive back in. And here we are currently one new drive and an existing drive throwing the same errors. Another thing worth mentionning is that after a reboot the disabled drives are picked up by unraid ready to be re added to the array. Ofcourse they are disabled so i would have to stop the array, remove them, start array, stop array, re add them and start array. This will work as it has done this multiple times. I'm however not doing so now untill the new sata cables arrive and after the memtest. Thanks for reading this very long message. I am completely lost Here is the newest log where you can see multiple ata drives pretty much fail at once, 2 of these are directly on the motherboard and 1 on my hba Dec 2 00:13:56 FourH3adServer kernel: ata6.00: exception Emask 0x0 SAct 0x7ff0000 SErr 0x0 action 0x6 frozen Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/78:80:50:0f:42/01:00:42:05:00/40 tag 16 ncq dma 192512 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/78:88:c8:10:42/01:00:42:05:00/40 tag 17 ncq dma 192512 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/38:90:40:12:42/01:00:42:05:00/40 tag 18 ncq dma 159744 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/18:98:78:13:42/01:00:42:05:00/40 tag 19 ncq dma 143360 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/88:a0:90:14:42/02:00:42:05:00/40 tag 20 ncq dma 331776 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/68:a8:18:17:42/01:00:42:05:00/40 tag 21 ncq dma 184320 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/50:b0:80:18:42/01:00:42:05:00/40 tag 22 ncq dma 172032 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/48:b8:d0:19:42/01:00:42:05:00/40 tag 23 ncq dma 167936 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/28:c0:18:1b:42/02:00:42:05:00/40 tag 24 ncq dma 282624 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/08:c8:40:1d:42/02:00:42:05:00/40 tag 25 ncq dma 266240 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata6.00: cmd 60/00:d0:48:1f:42/01:00:42:05:00/40 tag 26 ncq dma 131072 in Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata6.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata6: hard resetting link Dec 2 00:13:56 FourH3adServer kernel: ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6 frozen Dec 2 00:13:56 FourH3adServer kernel: ata1.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata1.00: cmd 61/e8:10:68:0e:42/00:00:42:05:00/40 tag 2 ncq dma 118784 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata1.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata1: hard resetting link Dec 2 00:13:56 FourH3adServer kernel: ata2.00: exception Emask 0x0 SAct 0x1fc0 SErr 0x0 action 0x6 frozen Dec 2 00:13:56 FourH3adServer kernel: ata2.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata2.00: cmd 61/30:30:48:00:42/04:00:42:05:00/40 tag 6 ncq dma 548864 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata2.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata2.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata2.00: cmd 61/10:38:78:04:42/01:00:42:05:00/40 tag 7 ncq dma 139264 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata2.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata2.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata2.00: cmd 61/e0:40:88:05:42/01:00:42:05:00/40 tag 8 ncq dma 245760 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata2.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata2.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata2.00: cmd 61/a8:48:68:07:42/02:00:42:05:00/40 tag 9 ncq dma 348160 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata2.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata2.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata2.00: cmd 61/c8:50:10:0a:42/02:00:42:05:00/40 tag 10 ncq dma 364544 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata2.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata2.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata2.00: cmd 61/90:58:d8:0c:42/01:00:42:05:00/40 tag 11 ncq dma 204800 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata2.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata2.00: failed command: WRITE FPDMA QUEUED Dec 2 00:13:56 FourH3adServer kernel: ata2.00: cmd 61/e8:60:68:0e:42/00:00:42:05:00/40 tag 12 ncq dma 118784 out Dec 2 00:13:56 FourH3adServer kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 2 00:13:56 FourH3adServer kernel: ata2.00: status: { DRDY } Dec 2 00:13:56 FourH3adServer kernel: ata2: hard resetting link Dec 2 00:14:02 FourH3adServer kernel: ata6: link is slow to respond, please be patient (ready=0) Dec 2 00:14:06 FourH3adServer kernel: ata1: softreset failed (1st FIS failed) Dec 2 00:14:06 FourH3adServer kernel: ata1: hard resetting link Dec 2 00:14:06 FourH3adServer kernel: ata2: softreset failed (1st FIS failed) Dec 2 00:14:06 FourH3adServer kernel: ata2: hard resetting link Dec 2 00:14:06 FourH3adServer kernel: ata6: found unknown device (class 0) fourh3adserver-diagnostics-20251202-0759.zip fourh3adserver-diagnostics-20251124-1012.zip fourh3adserver-diagnostics-20251118-2101.zip

Did you ever get this fixed? I am currently experiencing the exact same issues I have also changed the drive itself, psu, sata cable and use a different sata port. I am absolutely at my whits end