Getting an ata error I haven't encountered before in my syslog. I think I narrowed it down to disk 7, and in the logs for that disk I see this in red:

 

Unraid kernel: ata6.00: exception Emask 0x50 SAct 0x3f8 SErr 0xb0802 action 0xe frozen

With a bunch of other yellow warnings as well:

 

Feb  1 20:05:19 Unraid kernel: ata6.00: exception Emask 0x50 SAct 0x3f8 SErr 0xb0802 action 0xe frozen
Feb  1 20:05:19 Unraid kernel: ata6.00: irq_stat 0x00400000, PHY RDY changed
Feb  1 20:05:19 Unraid kernel: ata6: SError: { RecovComm HostInt PHYRdyChg PHYInt 10B8B }
Feb  1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb  1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:18:c8:b0:82/04:00:76:04:00/40 tag 3 ncq dma 528384 in
Feb  1 20:05:19 Unraid kernel: ata6.00: status: { DRDY }
Feb  1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb  1 20:05:19 Unraid kernel: ata6.00: cmd 60/00:20:d0:b4:82/04:00:76:04:00/40 tag 4 ncq dma 524288 in
Feb  1 20:05:19 Unraid kernel: ata6.00: status: { DRDY }
Feb  1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb  1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:28:d0:b8:82/00:00:76:04:00/40 tag 5 ncq dma 4096 in
Feb  1 20:05:19 Unraid kernel: ata6.00: status: { DRDY }
Feb  1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb  1 20:05:19 Unraid kernel: ata6.00: cmd 60/c8:30:d8:b8:82/03:00:76:04:00/40 tag 6 ncq dma 495616 in
Feb  1 20:05:19 Unraid kernel: ata6.00: status: { DRDY }
Feb  1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb  1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:38:a0:bc:82/04:00:76:04:00/40 tag 7 ncq dma 528384 in
Feb  1 20:05:19 Unraid kernel: ata6.00: status: { DRDY }
Feb  1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb  1 20:05:19 Unraid kernel: ata6.00: cmd 60/00:40:a8:c0:82/04:00:76:04:00/40 tag 8 ncq dma 524288 in
Feb  1 20:05:19 Unraid kernel: ata6.00: status: { DRDY }
Feb  1 20:05:19 Unraid kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb  1 20:05:19 Unraid kernel: ata6.00: cmd 60/08:48:a8:c4:82/00:00:76:04:00/40 tag 9 ncq dma 4096 in
Feb  1 20:05:19 Unraid kernel: ata6.00: status: { DRDY }
Feb  1 20:05:19 Unraid kernel: ata6: hard resetting link
Feb  1 20:05:25 Unraid kernel: ata6: found unknown device (class 0)
Feb  1 20:05:29 Unraid kernel: ata6: softreset failed (device not ready)
Feb  1 20:05:29 Unraid kernel: ata6: hard resetting link
Feb  1 20:05:35 Unraid kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb  1 20:05:35 Unraid kernel: ata6.00: configured for UDMA/133
Feb  1 20:05:35 Unraid kernel: ata6: EH complete

 

unraid-diagnostics-20240202-1727.zip

Yes, this is connection problem with disk7

24 minutes ago, trurl said:

Yes, this is connection problem with disk7

I just recently reseated all the sata cables to troubleshoot another issue. Could this be an issue with the hba card or power supply?

What about power connections? Any splitters?

1 minute ago, trurl said:

What about power connections? Any splitters?

Yes, I have 2 sata power splitters because I don't have enough cables for my PSU. I only have 1 splitter per full size cable though. I guess I can try replacing those. The ones I have now are pretty old from amazon.

6 hours ago, colev14 said:

Yes, I have 2 sata power splitters because I don't have enough cables for my PSU. I only have 1 splitter per full size cable though. I guess I can try replacing those. The ones I have now are pretty old from amazon.

How many ways does it split?   A SATA->SATA splitter tends to be unreliable if it is more than 2 way as the SATA connection cannot handle much current, whereas a Molex->SATA gets away with a 4 way split.

2 hours ago, itimpi said:

How many ways does it split?   A SATA->SATA splitter tends to be unreliable if it is more than 2 way as the SATA connection cannot handle much current, whereas a Molex->SATA gets away with a 4 way split.

I ordered these 4to1 sata cables. In have a define 7 XL so the extra length helps reach the drives furthest away from the psu. https://a.co/d/gthadWF

Is there another one you would recommended?

You might find something like this to be more reliable.    The problem with the ones you have is that if you connect 4 drives to them they might be subject to voltage sag when under load as the SATA connection at the host end is less robust and can carry less current than the Molex equivalent and that can cause the symptoms you are seeing.

 

Your issue could of course be something else entirely but power issues can be a bit tricky to track down at times.

Awesome, thank you. They'll be here tomorrow and I'll give them a shot.

16 hours ago, colev14 said:

Getting an ata error I haven't encountered before in my syslog.

By the way, these aren't that strange when you have looked at as many syslogs as we have. Bad connections are the cause of many of the problems that cause users to start a thread.

I purchased the molex to sata connectors and that seems to have solved the problem. Thank you!