ZFS issues with disk images after reboot

[AxelTwin]

same error here, vm still down after PVE reboot.
If anyone has a tip I'll be gratefull !

 

[stefan.kraus]

Same Problem:

TASK ERROR: timeout: no zvol device link for 'vm-103-disk-0' found after 300 sec found.

or sometimes

TASK ERROR: timeout: no zvol device link for 'vm-100-disk-1' found after 300 sec found



for i in $(ls -1 /dev/zd* |grep -v '/dev/zd[0-9]*p[0-9]*'); do udevadm trigger $i; done

helped without reboot but powered off VMs


pve-manager/7.3-3/c3928077 (running kernel: 5.15.74-1-pve)
root@pve:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

 

[gelcom]

I’m still facing the same problems just after any reboot.

 

[senbax]

Same here, i fixed it with a @reboot cron entry:

crontab -e

@reboot /root/fix-mounts.sh

/root/fix-mounts.sh

#!/bin/bash
for i in $(ls -1 /dev/zd* |grep -v '/dev/zd[0-9]*p[0-9]*'); do udevadm trigger $i; done

 

[masupilamie]

Having the same issue after upgrading to pve version 8.0.3

A single vm did not want to start with error:

TASK ERROR: timeout: no zvol device link for 'vm-106-disk-0' found after 300 sec found.

Implementing the workaround (cron @reboot script) provided by @senbax above fixed the issue for me

 

[elmarconi]

Updated today: Same issue.

root@pve3:~# pveversion -v proxmox-ve: 8.0.2 (running kernel: 6.2.16-15-pve) pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390) pve-kernel-6.2: 8.0.5 proxmox-kernel-helper: 8.0.3 pve-kernel-5.15: 7.4-4 proxmox-kernel-6.2.16-15-pve: 6.2.16-15 proxmox-kernel-6.2: 6.2.16-15 proxmox-kernel-6.2.16-14-pve: 6.2.16-14 proxmox-kernel-6.2.16-12-pve: 6.2.16-12 proxmox-kernel-6.2.16-10-pve: 6.2.16-10 pve-kernel-5.15.108-1-pve: 5.15.108-1 ceph-fuse: 16.2.11+ds-2 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown: 0.8.41 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-4 libknet1: 1.26-pve1 libproxmox-acme-perl: 1.4.6 libproxmox-backup-qemu0: 1.4.0 libproxmox-rs-perl: 0.3.1 libpve-access-control: 8.0.5 libpve-apiclient-perl: 3.3.1 libpve-common-perl: 8.0.9 libpve-guest-common-perl: 5.0.5 libpve-http-server-perl: 5.0.4 libpve-rs-perl: 0.8.5 libpve-storage-perl: 8.0.2 libqb0: 1.0.5-1 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 5.0.2-4 lxcfs: 5.0.3-pve3 novnc-pve: 1.4.0-2 proxmox-backup-client: 3.0.3-1 proxmox-backup-file-restore: 3.0.3-1 proxmox-kernel-helper: 8.0.3 proxmox-mail-forward: 0.2.0 proxmox-mini-journalreader: 1.4.0 proxmox-offline-mirror-helper: 0.6.2 proxmox-widget-toolkit: 4.0.9 pve-cluster: 8.0.4 pve-container: 5.0.4 pve-docs: 8.0.5 pve-edk2-firmware: 3.20230228-4 pve-firewall: 5.0.3 pve-firmware: 3.8-2 pve-ha-manager: 4.0.2 pve-i18n: 3.0.7 pve-qemu-kvm: 8.0.2-6 pve-xtermjs: 4.16.0-3 qemu-server: 8.0.7 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.1.13-pve1

running /root/fix-mounts.sh without reboot permitted start of the VM