Hi all.
I am running QEmu v2.11.1 under Debian Linux kerne v4.15.17
and I am getting these error messages inside an Ubuntu Linux Server
16.04.4 VM running kernel 4.4.0-128-generic:
Jun 20 05:07:09 tfg kernel: [497807.524612] ata3.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 20 05:07:09 tfg kernel: [497807.524651] ata3.00: failed command: WRITE DMA
Jun 20 05:07:09 tfg kernel: [497807.524677] ata3.00: cmd
ca/00:08:38:b8:f9/00:00:00:00:00/ec tag 27 dma 4096 out
Jun 20 05:07:09 tfg kernel: [497807.524677] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 20 05:07:09 tfg kernel: [497807.524746] ata3.00: status: { DRDY }
Jun 20 05:07:09 tfg kernel: [497807.524771] ata3: hard resetting link
Jun 20 05:07:29 tfg kernel: [497827.720611] ata3: SATA link up 1.5
Gbps (SStatus 113 SControl 300)
Jun 20 05:07:29 tfg kernel: [497827.720854] ata3.00: configured for UDMA/100
Jun 20 05:07:29 tfg kernel: [497827.720859] ata3.00: device reported
invalid CHS sector 0
Jun 20 05:07:29 tfg kernel: [497827.720865] ata3: EH complete
Of course, there's no such error in the physical host and the guest is
running the QEmu guest agent.
I have been told that the SATA interface should be used only when
compatibility is needed:
https://forum.proxmox.com/threads/ata3-00-failed-command-write-dma.44772/
I am going to replace SATA with SCSI-virtio in any case.
I am actually puzzled by such a message as I've never seen it and
would like to understand more about it.
Any hint?
Thanks in advance.
--
Vincenzo Romano - NotOrAnd.IT
Information Technologies
--
NON QVIETIS MARIBVS NAVTA PERITVS
