Proxmox error storage 'local-zfs' does not exist

slew

New Member
Feb 20, 2025
1
0
1
Hi team

My system shutdown due to power outage and when it rebooted none of my VM's are booting up, it tries to but I get the error storage 'local-zfs' does not exist.
 
Hi,
please share your /etc/pve/storage.cfg as well as the output of pveversion -v, zpool status -v and zfs list. Is this a stand-alone node or in a cluster?
 
Hi,
please share your /etc/pve/storage.cfg as well as the output of pveversion -v, zpool status -v and zfs list. Is this a stand-alone node or in a cluster?
I am having the exact same issue. Here is the data:
root@pve2:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,vztmpl,backup

dir: PiHole2
path /mnt/PiHole2
content images,rootdir
prune-backups keep-all=1
shared 0

root@pve2:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-3-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-3
proxmox-kernel-6.8.12-3-pve-signed: 6.8.12-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.5
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.2.4
pve-cluster: 8.0.8
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.14-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
root@pve2:~# zpool status -v
pool: rpool
state: ONLINE
scan: scrub repaired 0B in 00:01:24 with 0 errors on Sun Mar 9 00:25:25 2025
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-CT500MX500SSD1_2408E8996262-part3 ONLINE 0 0 0
ata-CT500MX500SSD1_2408E89954C3-part3 ONLINE 0 0 0

errors: No known data errors
root@pve2:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 23.2G 426G 104K /rpool
rpool/ROOT 2.19G 426G 96K /rpool/ROOT
rpool/ROOT/pve-1 2.19G 426G 2.19G /
rpool/data 17.7G 426G 96K /rpool/data
rpool/data/vm-100-disk-0 96K 426G 96K -
rpool/data/vm-100-disk-1 17.7G 426G 17.7G -
rpool/var-lib-vz 3.24G 426G 3.24G /var/lib/vz
root@pve2:~#
 
Hi,
I am having the exact same issue. Here is the data:
root@pve2:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,vztmpl,backup

dir: PiHole2
path /mnt/PiHole2
content images,rootdir
prune-backups keep-all=1
shared 0
Your storage configuration doesn't declare the storage.
root@pve2:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-3-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-3
proxmox-kernel-6.8.12-3-pve-signed: 6.8.12-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.5
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.2.4
pve-cluster: 8.0.8
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.14-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
root@pve2:~# zpool status -v
pool: rpool
state: ONLINE
scan: scrub repaired 0B in 00:01:24 with 0 errors on Sun Mar 9 00:25:25 2025
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-CT500MX500SSD1_2408E8996262-part3 ONLINE 0 0 0
ata-CT500MX500SSD1_2408E89954C3-part3 ONLINE 0 0 0

errors: No known data errors
root@pve2:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 23.2G 426G 104K /rpool
rpool/ROOT 2.19G 426G 96K /rpool/ROOT
rpool/ROOT/pve-1 2.19G 426G 2.19G /
rpool/data 17.7G 426G 96K /rpool/data
rpool/data/vm-100-disk-0 96K 426G 96K -
rpool/data/vm-100-disk-1 17.7G 426G 17.7G -
rpool/var-lib-vz 3.24G 426G 3.24G /var/lib/vz
root@pve2:~#
If you joined a cluster, you will need to re-add the storage definition: https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_join_node_to_cluster You also need to restrict in the configuration on which nodes the storage is actually available.

If you didn't join a cluster, you should be able to simply re-add the storage too Datacenter > Storage > Add > ZFS