deaerator Posted January 11, 2019 Share Posted January 11, 2019 I recently added a WD Elements Shucked drive and have a temp replacement SSD for my cache drive. I noticed my log starting to show this. Jan 11 12:27:23 Tower kernel: ata3.00: exception Emask 0x0 SAct 0xffffffff SErr 0x0 action 0x6 frozen Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/30:00:d8:53:19/05:00:59:00:00/40 tag 0 ncq dma 679936 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:08:08:59:19/05:00:59:00:00/40 tag 1 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:10:60:b7:fa/01:00:02:00:00/40 tag 2 ncq dma 131072 in Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:18:50:5e:19/05:00:59:00:00/40 tag 3 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:20:90:63:19/05:00:59:00:00/40 tag 4 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/38:28:d0:68:19/00:00:59:00:00/40 tag 5 ncq dma 28672 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:30:08:69:19/05:00:59:00:00/40 tag 6 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:38:50:6e:19/05:00:59:00:00/40 tag 7 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:40:90:73:19/05:00:59:00:00/40 tag 8 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/38:48:d0:78:19/00:00:59:00:00/40 tag 9 ncq dma 28672 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/68:50:78:7e:19/05:00:59:00:00/40 tag 10 ncq dma 708608 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/28:58:e0:83:19/05:00:59:00:00/40 tag 11 ncq dma 675840 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/58:60:08:89:19/05:00:59:00:00/40 tag 12 ncq dma 700416 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/c0:68:60:8e:19/06:00:59:00:00/40 tag 13 ncq dma 884736 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/e8:70:20:95:19/03:00:59:00:00/40 tag 14 ncq dma 512000 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:78:08:99:19/05:00:59:00:00/40 tag 15 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/60:80:48:9e:19/05:00:59:00:00/40 tag 16 ncq dma 704512 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/58:88:a8:a3:19/05:00:59:00:00/40 tag 17 ncq dma 700416 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:90:60:b8:fa/01:00:02:00:00/40 tag 18 ncq dma 131072 in Jan 11 12:27:23 Tower kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/08:98:68:60:5a/00:00:01:00:00/40 tag 19 ncq dma 4096 in Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/08:a0:70:64:fd/00:00:3b:00:00/40 tag 20 ncq dma 4096 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:a8:08:29:19/05:00:59:00:00/40 tag 21 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:b0:48:2e:19/05:00:59:00:00/40 tag 22 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:b4:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:b8:88:33:19/05:00:59:00:00/40 tag 23 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:c0:c8:38:19/00:00:59:00:00/40 tag 24 ncq dma 32768 out Jan 11 12:27:23 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/78:c8:08:39:19/05:00:59:00:00/40 tag 25 ncq dma 716800 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/40:d0:80:3e:19/05:00:59:00:00/40 tag 26 ncq dma 688128 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/48:d8:c0:43:19/05:00:59:00:00/40 tag 27 ncq dma 692224 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/80:e0:08:49:19/05:00:59:00:00/40 tag 28 ncq dma 720896 out Jan 11 12:27:23 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/50:e8:88:4e:19/05:00:59:00:00/40 tag 29 ncq dma 696320 out Jan 11 12:27:23 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 60/00:f0:88:c1:ad/03:00:1e:00:00/40 tag 30 ncq dma 393216 in Jan 11 12:27:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jan 11 12:27:23 Tower kernel: ata3.00: cmd 61/70:f8:08:79:19/05:00:59:00:00/40 tag 31 ncq dma 712704 out Jan 11 12:27:23 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jan 11 12:27:23 Tower kernel: ata3.00: status: { DRDY } Jan 11 12:27:23 Tower kernel: ata3: hard resetting link Jan 11 12:27:23 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 11 12:27:23 Tower kernel: ata3.00: configured for UDMA/133 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3.00: device reported invalid CHS sector 0 Jan 11 12:27:23 Tower kernel: ata3: EH complete Diagnostics is attached. Curious what is causing this? And is it serious? tower-diagnostics-20190111-1346.zip Quote Link to comment
JorgeB Posted January 11, 2019 Share Posted January 11, 2019 Looks more like a connection problem with the SSD, replace cables, if problems persist it could be the SSD. Quote Link to comment
RHartings Posted May 30, 2020 Share Posted May 30, 2020 I have a very similar problem. I run a linux CENTOS 8, fully updated system. I have many, many lines like: WARNING: Kernel Errors Present ata1.00: cmd 60/00:80:d8:8f:7b/0a:00:1b:00:00/40 tag 16 ncq dma 1310720 in#012 res 40/00:d8:b0:34:ca/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 60/00:88:d8:99:7b/06:00:1b:00:00/40 tag 17 ncq dma 786432 in#012 res 40/00:d8:b0:34:ca/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 60/00:90:d8:9f:7b/0a:00:1b:00:00/40 tag 18 ncq dma 1310720 in#012 res 40/00:d8:b0:34:ca/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 60/00:98:d8:a9:7b/06:00:1b:00:00/40 tag 19 ncq dma 786432 in#012 res 40/00:d8:b0:34:ca/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 61/00:20:e8:55:f2/0a:00:1b:00:00/40 tag 4 ncq dma 1310720 ou#012 res 40/00:18:a8:4f:f2/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 61/00:28:e8:5f:f2/06:00:1b:00:00/40 tag 5 ncq dma 786432 out#012 res 40/00:18:a8:4f:f2/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 61/00:d8:b0:34:ca/06:00:1b:00:00/40 tag 27 ncq dma 786432 out#012 res 40/00:d8:b0:34:ca/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 61/01:78:02:86:a3/00:00:18:00:00/40 tag 15 ncq dma 512 out#012 res 40/00:70:c0:45:4f/00:00:14:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 61/01:98:02:e2:b1/00:00:0f:00:00/40 tag 19 ncq dma 512 out#012 res 40/00:60:e0:36:45/00:00:0b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 61/01:b8:01:10:39/00:00:0b:00:00/40 tag 23 ncq dma 512 out#012 res 40/00:d8:08:86:a3/00:00:18:00:00/40 Emask 0x1 (device error) ...: 1 Time(s) ata1.00: cmd 61/01:c8:02:b4:2a/00:00:14:00:00/40 tag 25 ncq dma 512 out#012 res 40/00:c0:80:92:d4/00:00:0f:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: cmd 61/02:c8:01:e2:b1/00:00:0f:00:00/40 tag 25 ncq dma 1024 out#012 res 40/00:e0:38:e2:b1/00:00:0f:00:00/40 Emask 0x1 (device error) ...: 1 Time(s) ata1.00: cmd 61/08:10:40:c1:03/00:00:05:00:00/40 tag 2 ncq dma 4096 out#012 res 40/00:10:40:c1:03/00:00:05:00:00/40 Emask 0x1 (device error) ...: 1 Time(s) ... ... ata1.00: cmd 61/c0:10:e8:45:f2/09:00:1b:00:00/40 tag 2 ncq dma 1277952 ou#012 res 40/00:18:a8:4f:f2/00:00:1b:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata1.00: irq_stat 0x08000000, interface fatal error ...: 12 Time(s) ata2.00: cmd 61/00:00:08:fc:19/06:00:17:00:00/40 tag 0 ncq dma 786432 out#012 res 40/00:00:08:fc:19/00:00:17:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:08:08:02:1a/0a:00:17:00:00/40 tag 1 ncq dma 1310720 ou#012 res 40/00:00:08:fc:19/00:00:17:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:10:08:0c:1a/06:00:17:00:00/40 tag 2 ncq dma 786432 out#012 res 40/00:00:08:fc:19/00:00:17:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:18:08:12:1a/0a:00:17:00:00/40 tag 3 ncq dma 1310720 ou#012 res 40/00:00:08:fc:19/00:00:17:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:20:08:1c:1a/06:00:17:00:00/40 tag 4 ncq dma 786432 out#012 res 40/00:00:08:fc:19/00:00:17:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:28:08:22:1a/0a:00:17:00:00/40 tag 5 ncq dma 1310720 ou#012 res 40/00:00:08:fc:19/00:00:17:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:90:e8:3f:e7/06:00:1b:00:00/40 tag 18 ncq dma 786432 out#012 res 40/00:28:50:d8:f8/00:00:0a:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:98:e8:45:e7/0a:00:1b:00:00/40 tag 19 ncq dma 1310720 ou#012 res 40/00:28:50:d8:f8/00:00:0a:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:a0:e8:4f:e7/06:00:1b:00:00/40 tag 20 ncq dma 786432 out#012 res 40/00:28:50:d8:f8/00:00:0a:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:a8:e8:55:e7/0a:00:1b:00:00/40 tag 21 ncq dma 1310720 ou#012 res 40/00:28:50:d8:f8/00:00:0a:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:b0:e8:5f:e7/06:00:1b:00:00/40 tag 22 ncq dma 786432 out#012 res 40/00:28:50:d8:f8/00:00:0a:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:b8:e8:65:e7/0a:00:1b:00:00/40 tag 23 ncq dma 1310720 ou#012 res 40/00:28:50:d8:f8/00:00:0a:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/00:c0:e8:6f:e7/06:00:1b:00:00/40 tag 24 ncq dma 786432 out#012 res 40/00:28:50:d8:f8/00:00:0a:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/02:e8:01:86:a3/00:00:18:00:00/40 tag 29 ncq dma 1024 out#012 res 40/00:a0:40:db:4e/00:00:14:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/02:f0:10:08:35/00:00:0b:00:00/40 tag 30 ncq dma 1024 out#012 res 40/00:80:60:94:c2/00:00:0f:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/06:90:b1:81:2c/00:00:14:00:00/40 tag 18 ncq dma 3072 out#012 res 40/00:b0:00:bf:a6/00:00:18:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) ata2.00: cmd 61/08:10:d0:dd:c3/00:00:18:00:00/40 tag 2 ncq dma 4096 out#012 res 40/00:b0:00:bf:a6/00:00:18:00:00/40 Emask 0x10 (ATA bus error) ...: 1 Time(s) I have two ssd drives (ata1 and ata2; Samsung SSD 860 EVO 250GB (MZ-76E250B/EU)). The "dma 4096" varies a bit as you see - different numbers form time to time. Both drives are relatively new Samsung drives (6 months old). The errors came not directly after I installed them, replacing two drives that completely failed after 4,5 year (probably due a power surge - as my RAM in another computer were severly damaged and needed to be replaced too at the same time). The CENTOS 8-forum guys advised me too to changed cables, which I did, I even replaced the motherboard, but nothing helped. At one time, the kernel was updated and the notifications vanished..... Then lateron, another kernel update, and the problem returned. I really don't understand what the cause is, but I am not sure this is really hardware related. For now, I just let it go. The server works fine and there are no other issues. Quote Link to comment
JorgeB Posted May 31, 2020 Share Posted May 31, 2020 20 hours ago, RHartings said: I run a linux CENTOS 8, fully updated system. This is an Unraid support forum, not general Linux. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.