Aerandir

Hi All, I've been having a weird issue recently where Unraid becomes unreachable. I'm unable to login to Unraid page, not SSH to it. The only way I have to access it is physically. I'm not entirely sure what happens, and I tried capturing the diagnostics through CLI but I keep getting those errors (screenshots attached) Even after all those errors, and that it says the diagnostics file has been created, I can't find anything there. Any idea where to start with diagnosing the issue?

Thank you for the answer. Is there anything you could suggest to troubleshoot this further?

Hi everyone, First-time poster here, so please be gentle! I've been lurking for a while and doing my research, but I've run into a bit of a head-scratcher that I couldn't find a clear answer to. Decided to try something a bit adventurous and build a home server using one of those Chinese motherboards from AliExpress. I know, I know, potential risks and all that, but I was looking for a project to keep me occupied and off the streets. The board comes with 10 SATA ports, 4 labeled as SSATA and 6 as SATA. I get that they're controlled by different controllers. The problem is, any HDDs I connect to the regular SATA ports (not the SSATA ones) are throwing UDMA CRC errors. After some digging, I tried one of the SSATA ports and it worked perfectly. I've double-checked the BIOS settings, made sure the SATA controller is set to AHCI, not RAID, and gone through everything else I could think of, but no luck so far. The weird part is, I initially plugged my cache SSD into one of the SATA ports, and it didn't show any UDMA CRC errors. However, I'm now seeing a bunch of these errors in the logs: kernel: ata10.00: status: { DRDY } kernel: ata10: hard resetting link kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310) kernel: ata10.00: configured for UDMA/133 kernel: ata10: EH complete kernel: ata10.00: exception Emask 0x50 SAct 0x80f00013 SErr 0x280900 action 0x6 frozen kernel: ata10.00: irq_stat 0x08000000, interface fatal error kernel: ata10: SError: { UnrecovData HostInt 10B8B BadCRC } kernel: ata10.00: failed command: READ FPDMA QUEUED kernel: ata10.00: cmd 60/00:00:68:67:e8/0a:00:03:00:00/40 tag 0 ncq dma 1310720 in kernel: res 40/00:b0:68:51:e8/00:00:03:00:00/40 Emask 0x50 (ATA bus error) kernel: ata10.00: status: { DRDY } kernel: ata10.00: failed command: READ FPDMA QUEUED kernel: ata10.00: cmd 60/00:08:68:71:e8/02:00:03:00:00/40 tag 1 ncq dma 262144 in kernel: res 40/00:b0:68:51:e8/00:00:03:00:00/40 Emask 0x50 (ATA bus error) kernel: ata10.00: status: { DRDY } kernel: ata10.00: failed command: WRITE FPDMA QUEUED kernel: ata10.00: cmd 61/40:20:a0:b6:e3/00:00:04:00:00/40 tag 4 ncq dma 32768 out kernel: res 40/00:b0:68:51:e8/00:00:03:00:00/40 Emask 0x50 (ATA bus error) kernel: ata10.00: status: { DRDY } kernel: ata10.00: failed command: READ FPDMA QUEUED kernel: ata10.00: cmd 60/00:a0:68:3d:e8/0a:00:03:00:00/40 tag 20 ncq dma 1310720 in kernel: res 40/00:b0:68:51:e8/00:00:03:00:00/40 Emask 0x50 (ATA bus error) kernel: ata10.00: status: { DRDY } kernel: ata10.00: failed command: READ FPDMA QUEUED kernel: ata10.00: cmd 60/00:a8:68:47:e8/0a:00:03:00:00/40 tag 21 ncq dma 1310720 in kernel: res 40/00:b0:68:51:e8/00:00:03:00:00/40 Emask 0x50 (ATA bus error) These errors don't seem to be affecting the SSD's performance, though. So, my main question is, is this likely a controller issue on the motherboard? Or could there be something else I'm missing? Any suggestions on where to look further, or should I just assume those 6 SATA ports are a lost cause? I've ordered an LSI 9305-16i (IT Mode) card which should arrive soon, hoping that'll bypass the issue if those SATA ports are indeed unusable. Any insights or advice would be greatly appreciated! Oh, and before someone asks, diagnostics are attached. Thanks in advance! magnasu-diagnostics-20240831-1057.zip