Thanks for pointing into the right direction!
I had to put the zvol again to the zpool.cache file.
zpool set cachefile=/etc/zfs/zpool.cache pool1
Seems that since one of the last updates the pool wasn't part anymore of the configuration file.
Hi everyone,
I have the problem that one container in my pve environment does not start anymore via autostart for some months now.
The container has some external bind mounts from a external zfs pool. This is my container configuration:
arch: amd64
cores: 4
debug: 1
features: nesting=1...
This way doesn't work for me.
My workaround:
1. Create a container from a template in proxmox with the same os and unprivileged.
2. Go to the volume
cd /rpool/data/subvol-104-disk-0
3. Delete all data from template
rm -rf *
4. Extract image from lxd/lxc-container
tar xzvf icinga2.tar.gz
5...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.