Cannot start TrueNAS VM after upgrade to 8

M

mathematics28

New Member
Feb 18, 2023
7
2
3
Hi,

I upgraded to 8 seemingly without issue. My windows VM is working fine, but I cannot start my TrueNAS core VM. I think the issue is with my 3 NVMe drives but could be wrong as my boot drive is also an NVMe drive.

Error when starting is:

"kvm: -drive file=/dev/disk/by-id/nvme-eui.6479a773c000008f,if=none,id=drive-virtio1,format=raw,cache=none,aio=io_uring,detect-zeroes=on: Could not open '/dev/disk/by-id/nvme-eui.6479a773c000008f': No such file or directory

TASK ERROR: start failed: QEMU exited with code 1"

Sys log output:

Aug 20 08:49:23 truenasboi pmxcfs[1051]: [main] crit: Unable to get local IP address


Aug 20 08:49:23 truenasboi systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION


Aug 20 08:49:23 truenasboi systemd[1]: pve-cluster.service: Failed with result 'exit-code'.


Aug 20 08:49:23 truenasboi systemd[1]: Failed to start The Proxmox VE cluster filesystem.


Aug 20 08:49:23 truenasboi systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.


Aug 20 08:49:23 truenasboi systemd[1]: Started Regular background program processing daemon.


Aug 20 08:49:23 truenasboi systemd[1]: Starting Proxmox VE firewall...


Aug 20 08:49:23 truenasboi cron[1193]: (CRON) INFO (pidfile fd = 3)


Aug 20 08:49:23 truenasboi systemd[1]: Starting PVE API Daemon...


Aug 20 08:49:23 truenasboi systemd[1]: Starting PVE Status Daemon...


Aug 20 08:49:23 truenasboi cron[1193]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)


Aug 20 08:49:23 truenasboi cron[1193]: (CRON) INFO (Running @reboot jobs)


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: Unable to load access control list: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a


Aug 20 08:49:23 truenasboi systemd[1]: pvestatd.service: Failed with result 'exit-code'.


Aug 20 08:49:23 truenasboi systemd[1]: Failed to start PVE Status Daemon.


Aug 20 08:49:23 truenasboi systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.


Aug 20 08:49:23 truenasboi systemd[1]: Stopped The Proxmox VE cluster filesystem.


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: Unable to load access control list: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi systemd[1]: Starting The Proxmox VE cluster filesystem...


Aug 20 08:49:23 truenasboi systemd[1]: pve-firewall.service: Control process exited, code=exited, status=111/n/a


Aug 20 08:49:23 truenasboi systemd[1]: pve-firewall.service: Failed with result 'exit-code'.


Aug 20 08:49:23 truenasboi systemd[1]: Failed to start Proxmox VE firewall.


Aug 20 08:49:23 truenasboi pmxcfs[1200]: [main] crit: Unable to get local IP address


Aug 20 08:49:23 truenasboi pmxcfs[1200]: [main] crit: Unable to get local IP address




vgchange -ay output is

root@truenasboi:~# vgchange -ay


8 logical volume(s) in volume group "pve" now active




Not sure what to do. I am fairly new to Proxmox.

Thanks!
 
  • Like
Reactions: drnarf
mathematics28 said:
Hi,

I upgraded to 8 seemingly without issue. My windows VM is working fine, but I cannot start my TrueNAS core VM. I think the issue is with my 3 NVMe drives but could be wrong as my boot drive is also an NVMe drive.

Error when starting is:

"kvm: -drive file=/dev/disk/by-id/nvme-eui.6479a773c000008f,if=none,id=drive-virtio1,format=raw,cache=none,aio=io_uring,detect-zeroes=on: Could not open '/dev/disk/by-id/nvme-eui.6479a773c000008f': No such file or directory

TASK ERROR: start failed: QEMU exited with code 1"

Sys log output:

Aug 20 08:49:23 truenasboi pmxcfs[1051]: [main] crit: Unable to get local IP address


Aug 20 08:49:23 truenasboi systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION


Aug 20 08:49:23 truenasboi systemd[1]: pve-cluster.service: Failed with result 'exit-code'.


Aug 20 08:49:23 truenasboi systemd[1]: Failed to start The Proxmox VE cluster filesystem.


Aug 20 08:49:23 truenasboi systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.


Aug 20 08:49:23 truenasboi systemd[1]: Started Regular background program processing daemon.


Aug 20 08:49:23 truenasboi systemd[1]: Starting Proxmox VE firewall...


Aug 20 08:49:23 truenasboi cron[1193]: (CRON) INFO (pidfile fd = 3)


Aug 20 08:49:23 truenasboi systemd[1]: Starting PVE API Daemon...


Aug 20 08:49:23 truenasboi systemd[1]: Starting PVE Status Daemon...


Aug 20 08:49:23 truenasboi cron[1193]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)


Aug 20 08:49:23 truenasboi cron[1193]: (CRON) INFO (Running @reboot jobs)


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: Unable to load access control list: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pvestatd[1196]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a


Aug 20 08:49:23 truenasboi systemd[1]: pvestatd.service: Failed with result 'exit-code'.


Aug 20 08:49:23 truenasboi systemd[1]: Failed to start PVE Status Daemon.


Aug 20 08:49:23 truenasboi systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.


Aug 20 08:49:23 truenasboi systemd[1]: Stopped The Proxmox VE cluster filesystem.


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: Unable to load access control list: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[1] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[2] failed: Connection refused


Aug 20 08:49:23 truenasboi pve-firewall[1199]: ipcc_send_rec[3] failed: Connection refused


Aug 20 08:49:23 truenasboi systemd[1]: Starting The Proxmox VE cluster filesystem...


Aug 20 08:49:23 truenasboi systemd[1]: pve-firewall.service: Control process exited, code=exited, status=111/n/a


Aug 20 08:49:23 truenasboi systemd[1]: pve-firewall.service: Failed with result 'exit-code'.


Aug 20 08:49:23 truenasboi systemd[1]: Failed to start Proxmox VE firewall.


Aug 20 08:49:23 truenasboi pmxcfs[1200]: [main] crit: Unable to get local IP address


Aug 20 08:49:23 truenasboi pmxcfs[1200]: [main] crit: Unable to get local IP address




vgchange -ay output is

root@truenasboi:~# vgchange -ay


8 logical volume(s) in volume group "pve" now active




Not sure what to do. I am fairly new to Proxmox.

Thanks!
Click to expand...
Did you find a solution to this? I am running into a similar situation with my TrueNAS Scale VM
 
You must log in or register to reply here.
Top Bottom
Back