Hi all,
I've got a weird one. I've got a FreeBSD VM with several virtio drives. The FreeBSD OS drive is throwing lots of write errors that you'd normally see if your hard drive was going bad, and eventually locks up so I have to stop and reboot the VM. I'm not getting any HD errors on the proxmox host, or other VM's that use the same lvm so I assume the hard drive is fine.
Errors:
Aug 5 09:54:47 alb2samba kernel: vtbd0: hard error cmd=write 7891298-7891553
Aug 5 09:54:47 alb2samba kernel: g_vfs_done():vtbd0p2[WRITE(offset=4039802880, length=131072)]error = 5
Aug 5 09:54:47 alb2samba kernel: vtbd0: hard error cmd=write 7891554-7891809
Aug 5 09:54:47 alb2samba kernel: g_vfs_done():vtbd0p2[WRITE(offset=4039933952, length=131072)]error = 5
What would you recommend I try? If I clone the VM will I have the same write issue?
Here is the vm config, and virtio0 is the bad drive, and it's set up with Default (no cache). I have other VM's using local-lvm for drives and there are no issues.
balloon: 512
boot: cdn
bootdisk: virtio0
cores: 2
ide2: none,media=cdrom
memory: 4096
name: server
net0: bridge=vmbr1,e1000=62:66:30:66:39:35
numa: 0
onboot: 1
ostype: other
smbios1: uuid=8a139103-c211-499c-9037-b69c7bb8bb5c
sockets: 2
virtio0: local-lvm:vm-101-disk-1,size=32G
virtio1: data:vm-101-disk-1,size=460G
virtio2: backup:vm-101-disk-1,size=32G
Thanks for any help and guidance.
I've got a weird one. I've got a FreeBSD VM with several virtio drives. The FreeBSD OS drive is throwing lots of write errors that you'd normally see if your hard drive was going bad, and eventually locks up so I have to stop and reboot the VM. I'm not getting any HD errors on the proxmox host, or other VM's that use the same lvm so I assume the hard drive is fine.
Errors:
Aug 5 09:54:47 alb2samba kernel: vtbd0: hard error cmd=write 7891298-7891553
Aug 5 09:54:47 alb2samba kernel: g_vfs_done():vtbd0p2[WRITE(offset=4039802880, length=131072)]error = 5
Aug 5 09:54:47 alb2samba kernel: vtbd0: hard error cmd=write 7891554-7891809
Aug 5 09:54:47 alb2samba kernel: g_vfs_done():vtbd0p2[WRITE(offset=4039933952, length=131072)]error = 5
What would you recommend I try? If I clone the VM will I have the same write issue?
Here is the vm config, and virtio0 is the bad drive, and it's set up with Default (no cache). I have other VM's using local-lvm for drives and there are no issues.
balloon: 512
boot: cdn
bootdisk: virtio0
cores: 2
ide2: none,media=cdrom
memory: 4096
name: server
net0: bridge=vmbr1,e1000=62:66:30:66:39:35
numa: 0
onboot: 1
ostype: other
smbios1: uuid=8a139103-c211-499c-9037-b69c7bb8bb5c
sockets: 2
virtio0: local-lvm:vm-101-disk-1,size=32G
virtio1: data:vm-101-disk-1,size=460G
virtio2: backup:vm-101-disk-1,size=32G
Thanks for any help and guidance.