Search results

I did update the zfs cache-file as you instructed on all my pools and that fixed it - ssd2 now got mounted during boot and containers would automatically start again. Thanks for your support, much appreciated!

Yes: dir: local path /var/lib/vz content iso,vztmpl,backup zfspool: local-zfs pool rpool/data content images,rootdir sparse 1 dir: BackupWD path /BackupWD content vztmpl,iso,backup,rootdir,snippets,images maxfiles 50...

I think I found the problem. The containers where using a ZFS dataset which was not mounted. When I manually mounted them - my containers started as normal. However, why my ZFS dataset is not automatically mounted is unknown to me. But that is something for another topic :)

It is mounted now - since I did a restore currently so I can at least run my containers. Inside the file /etc/debian_version I see: buster/sid

I'm having the exact same problem and indeed it says: Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 104 lxc pre-start produced output: unable to detect OS distribution I did a restore of a backup I had of the container and it started. Unfortunately, after a reboot of the proxmox-host...