Search results

I was able to solve this by regenerating the zpool.cache file on all my pools: https://openzfs.github.io/openzfs-docs/Project%20and%20Community/FAQ.html#the-etc-zfs-zpool-cache-file

zfs storage seems to be finished before the QEMU start error. Here are some relevant log entries: Boot 83a99796caf44610950d42ff42f9ec13 Jun 27 19:12:15 pve kernel: ZFS: Loaded module v2.1.11-pve1, ZFS pool version 5000, ZFS filesystem version 5 Jun 27 19:12:21 pve systemd[1]: Starting Import...

Getting the following error when the VM tries to autostart after reboot: kvm: -drive file=/dev/zvol/ssd/vm-101-disk-0,if=none,id=drive-scsi0,discard=on,format=raw,cache=none,aio=io_uring,detect-zeroes=unmap: Could not open '/dev/zvol/ssd/vm-101-disk-0': Unknown error 512 TASK ERROR: start...

I solved it by looking up the pid of the running pvedaemon, putting it in a new /var/run/pvedaemon.pid file, and then running apt dist-upgrade again. Everything looks good now. Not sure why pvedaemon.pid was missing in the first place.

Using apt dist-upgrade: Setting up pve-manager (7.4-3) ... Job for pvedaemon.service failed. See "systemctl status pvedaemon.service" and "journalctl -xe" for details. dpkg: error processing package pve-manager (--configure): installed pve-manager package post-installation script subprocess...

I just ran into the same issue. You need to use the hostname that's used for Let's Encrypt.

I think I might have figured this out recently. The overlay2 storage driver technically doesn't support ZFS: https://docs.docker.com/storage/storagedriver/select-storage-driver/. I ended up running into other issues like certain directories couldn't be removed (similar...

Found this old thread, which explains it: https://forum.proxmox.com/threads/backup-fails-when-lxc-has-fuse-activated-and-in-use-error-code-23.101753/

It gets stuck at the snapshot stage when trying to backup an LXC container: INFO: suspend vm to make snapshot INFO: create storage snapshot 'vzdump' I have a FUSE mount (Seadrive) within the container. If I unmount it and run the backup, it works just fine and gets past that step quickly.

Not seeing this with ZFS 2.1. Any idea why that might be?

Wow, this is crazy. I think I'm still running into this bug in 2022. Is there a way to get notifications when a drive goes dead?

Last night, my CPU spiked to 100% due to System usage. When looking at syslog around the time it happened, these are the relevant lines I see: Jan 12 23:47:13 pve pvestatd[3817]: VM 102 qmp command failed - VM 102 qmp command 'query-proxmox-support' failed - got timeout Jan 12 23:48:06 pve...

Is there any timeline for getting 5.13 on Proxmox?

Now that 7.0 is out, will 6.4 still get 5.11 kernel updates through the end of its support cycle?

I think it's specifically vainfo that's out of date on Proxmox. Radeontop works fine on Proxmox host.

The version of vainfo in Proxmox is pretty old. Either go download a newer version or pass /dev/dri to an LXC (with a newer vainfo version) and try there.

Just saw this: https://www.google.com/amp/s/9to5linux.com/linux-kernel-5-11-reaches-end-of-life-users-urged-to-upgrade-to-linux-5-12/amp What's the plan for Proxmox?

Thanks for the clarifications!

Also, if I apt purge the 5.4 kernel, it also wants to remove the proxmox-ve package for some reason. root@pve:~# apt purge pve-kernel-5.4 Reading package lists... Done Building dependency tree Reading state information... Don The following...

So if I run dist-upgrade, it'll still keep me on 5.11?