ata error logs from kernel

Hi,

I have a query on below error logs. The ATA link was up and running for more than 10 hours and then failed HSM validation and eventually the link went down with below logs. I do not have sata_pmp support but my kernel have build with CONFIG_SATA_PMP.

ata1.00: ST-ATA: DRQ=0 without device error, dev_stat 0x0
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:0e:79:09:00/00:00:00:00:00/e0 tag 0 pio 7168 out
res 58/00:07:79:09:00/00:00:00:00:00/e0 Emask 0x202 (HSM violation)
ata1.00: status: { DRDY DRQ }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:06:e1:1c:00/00:00:00:00:00/e0 tag 0 pio 3072 out
res 50/00:00:e1:1c:00/00:00:00:00:00/e0 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: ST-ATA: DRQ=0 without device error, dev_stat 0x0
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:02:bf:1b:00/00:00:00:00:00/e0 tag 0 pio 1024 out
res 58/00:01:bf:1b:00/00:00:00:00:00/e0 Emask 0x202 (HSM violation)
ata1.00: status: { DRDY DRQ }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x7E
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:02:ff:16:00/00:00:00:00:00/e0 tag 0 pio 1024 out
res 58/00:01:ff:16:00/00:00:00:00:00/e0 Emask 0x3 (HSM violation)
ata1.00: status: { DRDY DRQ }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:0e:79:20:00/00:00:00:00:00/e0 tag 0 pio 7168 out
res 50/00:00:79:20:00/00:00:00:00:00/e0 Emask 0x100 (unknown error)
ata1.00: status: { DRDY }
ata1.00: configured for PIO4
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:0e:91:02:00/00:00:00:00:00/e0 tag 0 pio 7168 out
res 50/00:00:91:02:00/00:00:00:00:00/e0 Emask 0x100 (unknown error)
ata1.00: status: { DRDY }
ata1.00: configured for PIO4
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:0e:75:17:00/00:00:00:00:00/e0 tag 0 pio 7168 out
res 50/00:00:75:17:00/00:00:00:00:00/e0 Emask 0x100 (unknown error)
ata1.00: status: { DRDY }
ata1.00: configured for PIO4
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: ST-ATA: DRQ=0 without device error, dev_stat 0x0
ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:0e:7b:20:00/00:00:00:00:00/e0 tag 0 pio 7168 out
res 58/00:09:7b:20:00/00:00:00:00:00/e0 Emask 0x202 (HSM violation)
ata1.00: status: { DRDY DRQ }
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: SRST failed (errno=-16)
ata1: reset failed, giving up
ata1.00: disabled
ata1: EH complete
sd 0:0:0:0: [sda] Unhandled error code
sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 20 7b 00 00 0e 00
end_request: I/O error, dev sda, sector 8315
Aborting journal on device sda1.
sd 0:0:0:0: [sda] Unhandled error code
sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 02 59 00 00 02 00
end_request: I/O error, dev sda, sector 601
Buffer I/O error on device sda1, logical block 269
lost page write due to I/O error on sda1
journal commit I/O error
journal commit I/O error
ext3_abort called.
EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
sd 0:0:0:0: [sda] Unhandled error code
sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 77 e8 20 00 00 08 00
end_request: I/O error, dev sda, sector 7858208
Buffer I/O error on device sda2, logical block 918016
lost page write due to I/O error on sda2

Simon

ata1.00: failed command: WRITE SECTOR(S)
ata1.00: cmd 30/00:0e:79:09:00/00:00:00:00:00/e0 tag 0 pio 7168 out
res 58/00:07:79:09:00/00:00:00:00:00/e0 Emask 0x202 (HSM violation)
ata1.00: status: { DRDY DRQ }

HSM violation means bad status bits. Normally when a command completes, BSY and DRQ should both be cleared but in this case DRQ is still set. Since it's persistent across multiple commands to different sectors it seems like a bad disk.

If you are using a port multiplier, try testing the disk in a bay without it. Disks aren't designed to have a lot of timing margin, so extra components in the path can be problematic.

I tried disabling the SATA_PMP but still same result. Could the issue come if the disk is not responding fast? I see this issue occur when I write large number of messages per second to the disk.