Quote

Jun 18 01:14:41 Server1 kernel: ata14.00: failed command: FLUSH CACHE EXT
Jun 18 01:14:41 Server1 kernel: ata14.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 10
Jun 18 01:14:41 Server1 kernel:         res 51/04:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)
Jun 18 01:14:41 Server1 kernel: ata14.00: status: { DRDY ERR }
Jun 18 01:14:41 Server1 kernel: ata14.00: error: { ABRT }
Jun 18 01:14:41 Server1 kernel: ata14.00: configured for UDMA/33
Jun 18 01:14:41 Server1 kernel: ata14.00: device reported invalid CHS sector 0
Jun 18 01:14:41 Server1 kernel: ata14: EH complete
Jun 18 01:14:41 Server1 kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 18 01:14:41 Server1 kernel: ata14.00: irq_stat 0x40000001

The log is filled with this for days, then its fine for weeks, then it has this again.

 

What exactly does this mean?

 

I only took a look at the log because one drive got kicked off with one error.

Edited June 18, 20233 yr by TheGleaner

Please post the diagnostics.

23 minutes ago, JorgeB said:

Please post the diagnostics.

 

Edited July 5, 2025Jul 5 by TheGleaner

Looks more like a cable problem, replace the SATA cable.

16 hours ago, JorgeB said:

Looks more like a cable problem, replace the SATA cable.

Which one?

disk20