Many ata1 and ata2 kernel issues reported

[ralf]

Hi,

I have a newly installed (up-to-date) centos8 server, and Logwatch is telling me on a daily base:

WARNING: Kernel Errors Present
RAS: Correctable Errors collector initi ...: 1 Time(s)
ata1.00: cmd 61/00:70:00:60:57/0a:00:0a:00:00/40 tag 14 ncq dma 1310720 ou#012 res 40/00:00:a8:64:4b/00:00:0a:00:00/40 Emask 0x1 (device error) ...: 1 Time(s)
ata1.00: cmd 61/00:78:00:6a:57/06:00:0a:00:00/40 tag 15 ncq dma 786432 out#012 res 40/00:00:a8:64:4b/00:00:0a:00:00/40 Emask 0x1 (device error) ...: 1 Time(s)
ata1.00: cmd 61/02:d8:01:0c:02/00:00:05:00:00/40 tag 27 ncq dma 1024 out#012 res 40/00:e0:08:0c:02/00:00:05:00:00/40 Emask 0x1 (device error) ...: 1 Time(s)

.......many of such lines.......

ata1.00: error: { ABRT } ...: 5 Time(s)
ata1.00: irq_stat 0x08000000, interface fatal error ...: 6 Time(s)
ata2.00: cmd 61/01:68:01:86:a3/00:00:18:00:00/40 tag 13 ncq dma 512 out#012 res 40/00:68:01:86:a3/00:00:18:00:00/40 Emask 0x1 (device error) ...: 1 Time(s)
ata2.00: cmd 61/02:a8:01:0c:02/00:00:05:00:00/40 tag 21 ncq dma 1024 out#012 res 40/00:c0:58:df:03/00:00:05:00:00/40 Emask 0x1 (device error) ...: 1 Time(s)
ata2.00: cmd 61/02:c8:01:0a:82/00:00:07:00:00/40 tag 25 ncq dma 1024 out#012 res 40/00:f0:b8:a7:82/00:00:07:00:00/40 Emask 0x1 (device error) ...: 1 Time(s)
ata2.00: cmd 61/04:d0:b7:85:2b/00:00:14:00:00/40 tag 26 ncq dma 2048 out#012 res 40/00:80:d8:6e:07/00:00:0a:00:00/40 Emask 0x1 (device error) ...: 1 Time(s)

....many of such lines.....


I checked my SSD disks (ata1/ata2) ATA Samsung SSD 860 with SMART drive test,
First drive /dev/sda ( in Raid 1 with the second SSD, /dev/sdb):

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 359 -
# 2 Short offline Completed without error 00% 358 -

Second Drive (/dev/sdb):

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 361 -

Both disks seems OK.
I also did a RAM memory test, using MEMTEST86 (extended version) and no errors were reported.

So, are the reported issuse in the Logwatch daily report in your opinion kernel issues, or in reality hardware issues?

Any recommendations?

/Ralf

[TrevorH]

I would suggest that you post the rest of the messages around one of those occurrences as you have missed out a bunch of useful info that should be there. You may need to extract those direct from /var/log/messages.

[ralf]

Thanks Trevor!

Here is a section regarding ata1 from today at 3 consecutive occasions (@ 04.05, @ 05.45 and @ 09.43):

# more /var/log/messages | grep ata1
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: exception Emask 0x10 SAct 0x800001 SErr 0x0 action 0x6 frozen
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: cmd 61/34:00:43:2a:2c/00:00:14:00:00/40 tag 0 ncq dma 26624 out#012 res 40/00:b8:08:86:a3/00:00:18:00:00/40 Emask 0x10 (ATA bus error)
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: cmd 61/10:b8:08:86:a3/00:00:18:00:00/40 tag 23 ncq dma 8192 out#012 res 40/00:b8:08:86:a3/00:00:18:00:00/40 Emask 0x10 (ATA bus error)
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 04:05:00 server1-hartings-se kernel: ata1: hard resetting link
Oct 31 04:05:00 server1-hartings-se kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: configured for UDMA/133
Oct 31 04:05:00 server1-hartings-se kernel: ata1: EH complete
Oct 31 04:05:00 server1-hartings-se kernel: ata1.00: Enabling discard_zeroes_dataOct 31 05:10:01 server1-hartings-se kernel: ata1: log page 10h reported inactive tag 29
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: exception Emask 0x1 SAct 0x40000000 SErr 0x0 action 0x0
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: irq_stat 0x40000008
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: cmd 61/08:f0:10:47:98/00:00:1b:00:00/40 tag 30 ncq dma 4096 out#012 res 40/00:f0:10:47:98/00:00:1b:00:00/40 Emask 0x1 (device error)
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: configured for UDMA/133
Oct 31 05:10:01 server1-hartings-se kernel: ata1: EH complete
Oct 31 05:10:01 server1-hartings-se kernel: ata1.00: Enabling discard_zeroes_data
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: exception Emask 0x1 SAct 0x80ffc001 SErr 0x0 action 0x6 frozen
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: irq_stat 0x40000001
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/20:00:80:bc:c3/00:00:18:00:00/40 tag 0 ncq dma 16384 out#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/40:70:c0:f8:4d/00:00:14:00:00/40 tag 14 ncq dma 32768 out#012 res 40/00:70:c0:f8:4d/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/20:78:80:fc:4d/00:00:14:00:00/40 tag 15 ncq dma 16384 out#012 res 41/04:78:80:fc:4d/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY ERR }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: error: { ABRT }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/20:80:80:d5:4e/00:00:14:00:00/40 tag 16 ncq dma 16384 out#012 res 41/04:78:80:fc:4d/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY ERR }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: error: { ABRT }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/20:88:60:db:4e/00:00:14:00:00/40 tag 17 ncq dma 16384 out#012 res 41/04:78:80:fc:4d/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY ERR }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: error: { ABRT }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/20:90:80:91:58/00:00:14:00:00/40 tag 18 ncq dma 16384 out#012 res 41/04:78:80:fc:4d/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY ERR }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: error: { ABRT }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/40:98:80:7f:59/00:00:14:00:00/40 tag 19 ncq dma 32768 out#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/02:a0:01:86:a3/00:00:18:00:00/40 tag 20 ncq dma 1024 out#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/10:a8:08:86:a3/00:00:18:00:00/40 tag 21 ncq dma 8192 out#012 res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/08:b0:20:86:a3/00:00:18:00:00/40 tag 22 ncq dma 4096 out#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x5 (timeout)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/20:b8:00:3e:b5/00:00:18:00:00/40 tag 23 ncq dma 16384 out#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x5 (timeout)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: cmd 61/20:f8:c0:3e:b5/00:00:18:00:00/40 tag 31 ncq dma 16384 out#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x5 (timeout)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: status: { DRDY }
Oct 31 09:43:50 server1-hartings-se kernel: ata1: hard resetting link
Oct 31 09:43:50 server1-hartings-se kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: configured for UDMA/133
Oct 31 09:43:50 server1-hartings-se kernel: ata1: EH complete
Oct 31 09:43:50 server1-hartings-se kernel: ata1.00: Enabling discard_zeroes_data

There are no other events reported just before or after these occurrences in /var/log/messages.

For ata2 at two consecutive occasions @ 06.33 and @ 17.15 :

Oct 31 06:33:34 server1-hartings-se kernel: ata2: log page 10h reported inactive tag 27
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: exception Emask 0x1 SAct 0xf0000000 SErr 0x0 action 0x0
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: irq_stat 0x40000008
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: cmd 61/30:e0:88:96:68/00:00:0b:00:00/40 tag 28 ncq dma 24576 out#012 res 40/00:f8:38:c8:4e/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: cmd 61/08:e8:c0:32:4a/00:00:0b:00:00/40 tag 29 ncq dma 4096 out#012 res 40/00:f8:38:c8:4e/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: cmd 61/18:f0:c8:ce:52/00:00:14:00:00/40 tag 30 ncq dma 12288 out#012 res 40/00:f8:38:c8:4e/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: cmd 61/08:f8:38:c8:4e/00:00:14:00:00/40 tag 31 ncq dma 4096 out#012 res 40/00:f8:38:c8:4e/00:00:14:00:00/40 Emask 0x1 (device error)
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: supports DRM functions and may not be fully accessible
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: supports DRM functions and may not be fully accessible
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: configured for UDMA/133
Oct 31 06:33:34 server1-hartings-se kernel: ata2: EH complete
Oct 31 06:33:34 server1-hartings-se kernel: ata2.00: Enabling discard_zeroes_data
Oct 31 17:15:28 server1-hartings-se kernel: ata2: log page 10h reported inactive tag 27
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: exception Emask 0x1 SAct 0x700003c0 SErr 0x0 action 0x0
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: irq_stat 0x40000008
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: cmd 61/20:30:a0:4c:03/00:00:05:00:00/40 tag 6 ncq dma 16384 out#012 res 40/00:48:c0:b2:03/00:00:05:00:00/40 Emask 0x1 (device error)
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: cmd 61/08:38:18:4e:03/00:00:05:00:00/40 tag 7 ncq dma 4096 out#012 res 40/00:48:c0:b2:03/00:00:05:00:00/40 Emask 0x1 (device error)
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: cmd 61/40:40:80:4e:03/00:00:05:00:00/40 tag 8 ncq dma 32768 out#012 res 40/00:48:c0:b2:03/00:00:05:00:00/40 Emask 0x1 (device error)
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: cmd 61/20:48:c0:b2:03/00:00:05:00:00/40 tag 9 ncq dma 16384 out#012 res 40/00:48:c0:b2:03/00:00:05:00:00/40 Emask 0x1 (device error)
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: cmd 61/40:e0:40:32:93/00:00:02:00:00/40 tag 28 ncq dma 32768 out#012 res 40/00:48:c0:b2:03/00:00:05:00:00/40 Emask 0x1 (device error)
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: cmd 61/02:e8:01:0c:02/00:00:05:00:00/40 tag 29 ncq dma 1024 out#012 res 40/00:48:c0:b2:03/00:00:05:00:00/40 Emask 0x1 (device error)
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: cmd 61/20:f0:08:0c:02/00:00:05:00:00/40 tag 30 ncq dma 16384 out#012 res 40/00:48:c0:b2:03/00:00:05:00:00/40 Emask 0x1 (device error)
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: status: { DRDY }
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: supports DRM functions and may not be fully accessible
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: supports DRM functions and may not be fully accessible
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: configured for UDMA/133
Oct 31 17:15:28 server1-hartings-se kernel: ata2: EH complete
Oct 31 17:15:28 server1-hartings-se kernel: ata2.00: Enabling discard_zeroes_data

There are no other events reported just before or after these occurrences in /var/log/messages.

For comparison, for ata3 (nothing reported today in /var/log/messages):

[root@server1-hartings-se log]# more messages | grep ata3
Oct 28 15:32:08 server1-hartings-se kernel: ata3: SATA max UDMA/133 abar m1024@0xfe30b000 port 0xfe30b200 irq 19
Oct 28 15:32:08 server1-hartings-se kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 28 15:32:08 server1-hartings-se kernel: ata3.00: ATA-9: WDC WD1003FZEX-00MK2A0, 01.01A01, max UDMA/133
Oct 28 15:32:08 server1-hartings-se kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Oct 28 15:32:08 server1-hartings-se kernel: ata3.00: configured for UDMA/133
Oct 29 17:44:53 server1-hartings-se kernel: ata3: SATA max UDMA/133 abar m1024@0xfe30b000 port 0xfe30b200 irq 19
Oct 29 17:44:53 server1-hartings-se kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 29 17:44:53 server1-hartings-se kernel: ata3.00: ATA-9: WDC WD1003FZEX-00MK2A0, 01.01A01, max UDMA/133
Oct 29 17:44:53 server1-hartings-se kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Oct 29 17:44:53 server1-hartings-se kernel: ata3.00: configured for UDMA/133
Oct 30 10:33:43 server1-hartings-se kernel: ata3: SATA max UDMA/133 abar m1024@0xfe30b000 port 0xfe30b200 irq 19
Oct 30 10:33:43 server1-hartings-se kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 30 10:33:43 server1-hartings-se kernel: ata3.00: ATA-9: WDC WD1003FZEX-00MK2A0, 01.01A01, max UDMA/133
Oct 30 10:33:43 server1-hartings-se kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Oct 30 10:33:43 server1-hartings-se kernel: ata3.00: configured for UDMA/133
[root@server1-hartings-se log]#

The "WRITE FPDMA QUEUED" could perhaps be due to speed limits? (I found a similar link https://bbs.archlinux.org/viewtopic.php?id=218390).
My motherboard says SATA 6GB/s for all six SATA data ports.
Could it be cable issues ,as suggested i the referred post? Why than on two different cables? I did unplug and plugged in the cables a week ago, when I first saw these messages, but I noticed no difference after unplugging/plugging in the cables.
Any other comments/suggestions?

Many thanks!

[George99]

I had similar problems on a Debian system with an old motherboard (ASUS M3A78-EM) when switching from my old SATA-SSD to the new one - both Samsung (830 and 860 PRO). Lots of link down / link up messages apeared at random times in the log. Changing cables didn't help. Finally I bought a recent AM4 motherboard (ASUS Prime B450M-A) and the messages disappeared.

[BShT]

I had similar problems too, an old fedora 4 or so, using dual boot

if i started windows first then reboot to linux i had a lot of disk errors

[TrevorH]

I would start by changing the SATA cables. Cheap, easy to do, might possibly be the problem.

You can also pass kernel parameters to restrict it from negotiating higher SATA rates to see if they go away at lower speeds. From my system I use libata.force=11:3.0G,9:1.5G - my example there has ata11 set to 3Gbps (an eSATA attached SSD in a case that says it's rated for eSATA 3Gbps but the system insists on trying to run it at 6Gbps with similar results to yours. I think ata9 is my DVD drive, has a similar problem but that one has to run at 1.5Gbps.

[ralf]

Thanks Trevor!
I did exchanged some cables before (sata 1 <-> 4 and sata 2 <-> 3), when my SSD disks started to fail, but that did have any effect as far as I remember, but I did not look into printer issues at that time....
I'll try it again with new ones (cheap check as you say). If that doesn't help, I will set speed limits as you propose.
Last way out will be to exchange the motherboard, though I am thinking of this more today than before, because of my persistent printing problems. Though these can be due to centos8 itself? I never had those printing problems with the same printer, server, and clients on centos7/macos.

[ralf]

@ Trevor:

I replaced the two ata1 and ata2 cables as you recommended, but same result. Still those errors for both drives.
Then I tried to reduce the speed with the command you gave:

libata.force=

But this is not installed on my centos8 system and I couldn't find the rpm which provides this.
Can you point me to the right rpm?

Thanks!

[TrevorH]

It's not part of any package. It's a kernel parameter that needs to be added to the kernel command line, either by interrupting the boot process at the grub menu and editing the parameters that get passed (that's a one-time thing, works only for the time you do it) or by changing grub.cfg to include it. For example, looking in /proc/cmdline on my system shows that I used this:

Code: Select all

BOOT_IMAGE=/vmlinuz-3.10.0-1062.4.1.el7.x86_64 root=/dev/mapper/...  ...LANG=en_GB.UTF-8 crashkernel=0@0 libata.force=11:3.0G,9:1.5G 

[ralf]

Mmm. I think this is beyond where I feel comfortable to experiment.
Sounds a bit too risky to do this on a running web/mail server or when doing off-line, losing the whole server for some time.
I think my only option left is to look for another motherboard.

My printing issues are very weird (see updated post posting.php?mode=reply&f=48&t=72277) and can either be due to a bug in the centos8 server packages, or it is hardware also related to the server hardware, in particular the motherboard, as I cannot find anything wrong with the SSD's nor the RAM.
As I cannot find anything similar to my problem with centos8, I think I need to conclude that it is hardware related.

My home was exposed to 3 subsequent outages within 15 sec (and probably over-voltages) some weeks ago and I lost 2 SSD's on the server (now replaced and loaded with centos8 instead of centos7 before)), all RAM in my iMac (now replaced) and my RAID1 on the iMac was out of order too (back in business again. My guess is that something is wrong with the server motherboard too, though I hoped it would not be damaged....

Thanks for your help!