So I bought a new 2TB Samsung evo (same model). After copying all the data from the old one via ddrescue and getting my system setup again I thought I was past this issue. However... the SAME error is popping up for my brand new 1 week old SSD!
See below
Code: Select all
[1227765.345170] ata8.00: exception Emask 0x10 SAct 0x7c200 SErr 0x0 action 0x6 frozen
[1227765.345176] ata8.00: irq_stat 0x08000000, interface fatal error
[1227765.345178] ata8.00: failed command: READ FPDMA QUEUED
[1227765.345179] ata8.00: cmd 60/08:48:80:cd:2a/00:00:35:00:00/40 tag 9 ncq dma 4096 in
res 40/00:88:f8:6b:29/00:00:35:00:00/40 Emask 0x10 (ATA bus error)
[1227765.345184] ata8.00: status: { DRDY }
[1227765.345186] ata8.00: failed command: WRITE FPDMA QUEUED
[1227765.345187] ata8.00: cmd 61/10:70:50:6b:29/00:00:35:00:00/40 tag 14 ncq dma 8192 out
res 40/00:88:f8:6b:29/00:00:35:00:00/40 Emask 0x10 (ATA bus error)
[1227765.345191] ata8.00: status: { DRDY }
[1227765.345192] ata8.00: failed command: WRITE FPDMA QUEUED
[1227765.345193] ata8.00: cmd 61/38:78:90:6b:29/00:00:35:00:00/40 tag 15 ncq dma 28672 out
res 40/00:88:f8:6b:29/00:00:35:00:00/40 Emask 0x10 (ATA bus error)
[1227765.345196] ata8.00: status: { DRDY }
[1227765.345197] ata8.00: failed command: WRITE FPDMA QUEUED
[1227765.345198] ata8.00: cmd 61/10:80:e0:6b:29/00:00:35:00:00/40 tag 16 ncq dma 8192 out
res 40/00:88:f8:6b:29/00:00:35:00:00/40 Emask 0x10 (ATA bus error)
[1227765.345202] ata8.00: status: { DRDY }
[1227765.345203] ata8.00: failed command: WRITE FPDMA QUEUED
[1227765.345204] ata8.00: cmd 61/08:88:f8:6b:29/00:00:35:00:00/40 tag 17 ncq dma 4096 out
res 40/00:88:f8:6b:29/00:00:35:00:00/40 Emask 0x10 (ATA bus error)
[1227765.345207] ata8.00: status: { DRDY }
[1227765.345208] ata8.00: failed command: READ FPDMA QUEUED
[1227765.345209] ata8.00: cmd 60/08:90:48:cd:cd/00:00:35:00:00/40 tag 18 ncq dma 4096 in
res 40/00:88:f8:6b:29/00:00:35:00:00/40 Emask 0x10 (ATA bus error)
[1227765.345212] ata8.00: status: { DRDY }
[1227765.345215] ata8: hard resetting link
[1227765.805161] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1227765.805390] ata8.00: supports DRM functions and may not be fully accessible
[1227765.805751] ata8.00: disabling queued TRIM support
[1227765.808022] ata8.00: supports DRM functions and may not be fully accessible
[1227765.808376] ata8.00: disabling queued TRIM support
[1227765.810456] ata8.00: configured for UDMA/133
[1227765.810472] sd 7:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
[1227765.810474] sd 7:0:0:0: [sdd] tag#9 Sense Key : Illegal Request [current]
[1227765.810476] sd 7:0:0:0: [sdd] tag#9 Add. Sense: Unaligned write command
[1227765.810479] sd 7:0:0:0: [sdd] tag#9 CDB: Read(10) 28 00 35 2a cd 80 00 00 08 00
[1227765.810481] blk_update_request: I/O error, dev sdd, sector 891997568 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[1227765.810498] ata8: EH complete
[1227765.810557] ata8.00: Enabling discard_zeroes_data
Code: Select all
sdd 8:48 0 1.8T 0 disk
└─systemvms 253:18 0 1.8T 0 crypt /mnt/systemvms
Not sure if its relevant but the ssd is a LUKS volume as can be seen above. The params are
Code: Select all
/dev/mapper/systemvms is active and is in use.
type: LUKS2
cipher: aes-xts-plain64
keysize: 512 bits
key location: keyring
device: /dev/sdd
sector size: 512
offset: 32768 sectors
size: 3906996400 sectors
mode: read/write
flags: discards
Whether that chance is high enough to speculatively replace the board, I can't say. I suggest you wait for other posters to comment on this before committing to the purchase of new hardware.
