On tailing vmkernel.log in one of my ESXi I found this:
==> vmkernel.log <==
2018-11-30T15:54:06.108Z cpu27:33482)<6>ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2018-11-30T15:54:06.432Z cpu27:33482)<6>ata14.00: configured for UDMA/66
2018-11-30T15:54:06.432Z cpu27:33482)<6>ata14: EH complete
2018-11-30T15:54:06.458Z cpu27:33482)<3>ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
2018-11-30T15:54:06.458Z cpu27:33482)<3>ata14.00: irq_stat 0x40000001
2018-11-30T15:54:06.458Z cpu27:33482)<3>ata14.00: cmd a0/00:00:00:00:01/00:00:00:00:00/a0 tag 0 pio 255 in
cdb 1a 00 08 00 ff 00 00 00 00 00 00 00 00 00 00 00
res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
2018-11-30T15:54:06.781Z cpu27:33482)<6>ata14: soft resetting link
2018-11-30T15:54:06.987Z cpu27:33482)<6>ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
==> vmkernel.log <==
2018-11-30T15:54:07.311Z cpu27:33482)<6>ata14.00: configured for UDMA/66
2018-11-30T15:54:07.311Z cpu27:33482)<6>ata14: EH complete
2018-11-30T15:54:07.338Z cpu27:33482)<3>ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
2018-11-30T15:54:07.338Z cpu27:33482)<3>ata14.00: irq_stat 0x40000001
2018-11-30T15:54:07.338Z cpu27:33482)<3>ata14.00: cmd a0/00:00:00:00:01/00:00:00:00:00/a0 tag 0 pio 255 in
cdb 1a 00 08 00 ff 00 00 00 00 00 00 00 00 00 00 00
res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
2018-11-30T15:54:07.644Z cpu31:33188)<6>ahci_scsi_abort: cmd 0x1a (0x43bd8c4d8240), entering...
2018-11-30T15:54:07.644Z cpu31:33188)<7>ata14: ahci_port_reset, entering...
2018-11-30T15:54:07.660Z cpu27:33482)<6>ata14: soft resetting link
2018-11-30T15:54:07.660Z cpu27:33482)<6>ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
==> vmkernel.log <==
2018-11-30T15:54:07.983Z cpu27:33482)<6>ata14.00: configured for UDMA/66
2018-11-30T15:54:07.983Z cpu27:33482)<6>ata14: EH complete
2018-11-30T15:54:08.086Z cpu31:33188)<6>ata14: ahci_port_reset: SUCCEEDED
2018-11-30T15:54:08.086Z cpu31:33188)<6>ahci_scsi_abort: cmd 0x1a (0x43bd8c4d8240), SUCCEEDED
If you notice logs were showing HSM violation and then it stopped this error.
Can anybody help me to understand what happened over here?
P.S Reason I am concerned about these logs is that it's possible these may somehow be contributing to my ESXi going down at regular intervals.