I have a proxmox node that automatically powers on every night for backups. The node hosts a Truenas VM, that is configured with two disks in passthrough mode.
After a ~week of failing backups, I noticed that the VM was stuck at boot trying to access the 2 scsi disks. The problem seems to happen only when using kernel 6.5.13-1-pve. Reverting back to the latest 6.5.11 version solves the problem.
This is the config of the VM.
Strangely enough with the latest kernel, if I try accessing the disk e.g. with cfdisk while the vm is booting, the problem can be circumvented.
Possibly related thread:
https://forum.proxmox.com/threads/p...ade-from-6-5-11-8-pve-to-6-5-13-1-pve.142810/
After a ~week of failing backups, I noticed that the VM was stuck at boot trying to access the 2 scsi disks. The problem seems to happen only when using kernel 6.5.13-1-pve. Reverting back to the latest 6.5.11 version solves the problem.
This is the config of the VM.
YAML:
agent: 1
balloon: 1024
boot: order=sata0;scsi0
cores: 4
cpu: kvm64,flags=+aes
hotplug: 0
memory: 8192
meta: creation-qemu=6.2.0,ctime=1657136780
name: nas
net0: virtio=1A:96:70:0F:28:1F,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
protection: 1
sata0: none,media=cdrom
scsi0: local-lvm:vm-103-disk-0,size=15G
scsi1: /dev/disk/by-id/ata-XXX,aio=threads,backup=0,iothread=1,scsiblock=1,size=3907018584K
scsi2: /dev/disk/by-id/ata-YYY,aio=threads,backup=0,iothread=1,scsiblock=1,size=3907018584K
scsihw: virtio-scsi-single
smbios1: uuid=0a976e16-bf12-4b0c-8496-3896c10631f4
sockets: 1
tablet: 0
vmgenid: 3c28400b-397a-40d3-8d2c-28afec5ba55d
vmstatestorage: local-lvmStrangely enough with the latest kernel, if I try accessing the disk e.g. with cfdisk while the vm is booting, the problem can be circumvented.
Possibly related thread:
https://forum.proxmox.com/threads/p...ade-from-6-5-11-8-pve-to-6-5-13-1-pve.142810/
Last edited: