Hi I got some strange errors just after the scheduled Trim job was started:

 

Feb 23 07:02:42 mandarin kernel: ata5.00: status: { DRDY }
Feb 23 07:02:42 mandarin kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Feb 23 07:02:42 mandarin kernel: ata5.00: cmd 61/28:68:40:6d:24/00:00:0c:00:00/40 tag 13 ncq dma 20480 out
Feb 23 07:02:42 mandarin kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 23 07:02:42 mandarin kernel: ata5.00: status: { DRDY }
Feb 23 07:02:42 mandarin kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Feb 23 07:02:42 mandarin kernel: ata5.00: cmd 61/20:70:d8:75:24/00:00:0c:00:00/40 tag 14 ncq dma 16384 out
Feb 23 07:02:42 mandarin kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 23 07:02:42 mandarin kernel: ata5.00: status: { DRDY }
Feb 23 07:02:42 mandarin kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Feb 23 07:02:42 mandarin kernel: ata5.00: cmd 61/60:78:10:7c:24/00:00:0c:00:00/40 tag 15 ncq dma 49152 out
Feb 23 07:02:42 mandarin kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 23 07:02:42 mandarin kernel: ata5.00: status: { DRDY }
Feb 23 07:02:42 mandarin kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Feb 23 07:02:42 mandarin kernel: ata5.00: cmd 61/08:80:f8:75:24/00:00:0c:00:00/40 tag 16 ncq dma 4096 out
Feb 23 07:02:42 mandarin kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 23 07:02:42 mandarin kernel: ata5.00: status: { DRDY }
Feb 23 07:02:42 mandarin kernel: ata5: hard resetting link
Feb 23 07:02:43 mandarin kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 23 07:02:43 mandarin kernel: ata5.00: supports DRM functions and may not be fully accessible
Feb 23 07:02:43 mandarin kernel: ata5.00: supports DRM functions and may not be fully accessible
Feb 23 07:02:43 mandarin kernel: ata5.00: configured for UDMA/133
Feb 23 07:02:43 mandarin kernel: ata5: EH complete
Feb 23 07:02:45 mandarin root: /mnt/cache: 163.1 GiB (175116275712 bytes) trimmed

This one also showed up:

Feb 23 07:01:09 mandarin kernel: ata5.00: exception Emask 0x0 SAct 0x7fc00003 SErr 0x0 action 0x6 frozen

 

I havent seen this before and i've also changed the cables twice.. to the disk in question(SSD).

Is this perhaps normal log output under certain circumstances and nothing to worry about?

The TRIM is scheduled once a week and i've never seen this exact output before.

 

Any guesses?

 

 

 

 

If you have definitely proved that it isn't the cable, then try the disk on a different controller port. Some Marvell-based controllers can have problems with recent unRAID versions. Other things it could be include a bad power supply or cabling or an actual faulty SSD.