Hi all.
I am running a few VMs under proxmox 5.2-2.
I find from time to time a very puzzling set of log messages inside the VMs:
These lines can appear from a few times a day to a few times a hour.
I am also encountering some virtual disk image inconsistencies where the initial part of the image gets corrupted and made un-bootable.
If I restore the partition table I can mount the filesystem, but cannot boot it.
I cannot prove the two things are related, but I "feel" it's so.
As the disk is virtual, I am really puzzled by such events.
What I'd like to know is:
1. Should I worry about those events? ( I would say so).
2. As the disk is virtual, is this a bug in qemu-kvm?
3. Can this type of event be the cause of the disk inconsistencies?
4. Anyone here with the same issues?
5. Can this thing be "fixed" by me?
If you need more details, please ask.
I am running a few VMs under proxmox 5.2-2.
I find from time to time a very puzzling set of log messages inside the VMs:
Code:
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
These lines can appear from a few times a day to a few times a hour.
I am also encountering some virtual disk image inconsistencies where the initial part of the image gets corrupted and made un-bootable.
If I restore the partition table I can mount the filesystem, but cannot boot it.
I cannot prove the two things are related, but I "feel" it's so.
As the disk is virtual, I am really puzzled by such events.
What I'd like to know is:
1. Should I worry about those events? ( I would say so).
2. As the disk is virtual, is this a bug in qemu-kvm?
3. Can this type of event be the cause of the disk inconsistencies?
4. Anyone here with the same issues?
5. Can this thing be "fixed" by me?
If you need more details, please ask.