Opnsense VM, sata disk boot fail, waiting for cam.

[matslunnegren]

Hi
Kinda a newbie on this forum. If this is the wrong section, feel free to move the post.
Have been running proxmox with opnsense as a vm for about 2 years now, updating the system weekly.
I got an power outage yesterday and when the power got back my opnsense vm could not longer boot.
First the console was spammed by a message
"root mount waiting for cam" And later With the error message "solaris notice cannot find pool label"
Didnt worry to much but just reinstalled proxmox and vms from backup.
Then today i updated proxmox to the latest version via apt and rebooted and got the same errror. Hmm bug?
Then i saw this reddit post and tried to detach my drive mounted as sata and instead mount it as ide and sucess! It booted again.
https://www.reddit.com/r/OPNsenseFirewall/comments/17xm5eo/root_mount_waiting_for_cam/
So what has changed?
H/W info. Dell r720, 2x2667v2.160 gb ram. 2x1tb mirrored raid in btrfs.

 

[fiona]

Hi,
this is a bug in the current QEMU package and will be fixed in pve-qemu-kvm >= 8.1.2-3. See here for more information: https://forum.proxmox.com/threads/p...t-version-of-proxmox-8-0-4.136617/post-606770

 

[EagleBBS]

Same thing on lots of VMs. Since last update, some VMs refuse unexpectedly to start. Opnsense, Truenas are concerned for example.

 

[fiona]

Same thing on lots of VMs. Since last update, some VMs refuse unexpectedly to start. Opnsense, Truenas are concerned for example.

FYI, the QEMU package with the fix pve-qemu-kvm = 8.1.2-3 is available on the no-subscription repository already. If your VMs have an IDE or SATA disk (empty CD ROM drive also can cause the issue), please upgrade and the issue should go away. If it doesn't, please provide the output of pveversion -v and qm config <ID> replacing <ID> with the actual ID of an affected VM.

 

[EagleBBS]

Thx i was effetively informed that it was a bug. Remediation applyed successufly with the fix. Thx