Upgrading from 5.4 -> 6.2 zvol linking fails

rotor-head

New Member
Jul 10, 2020
3
0
1
55
Completed the upgrade from 5.4 to 6.2. After rebooting, attempted to add a new VM. The raw disk image is created successfully, however, the link fails to create:

TASK ERROR: unable to create VM 102 - timeout: no zvol device link for 'vm-102-disk-0' found after 300 sec found.
The contents for the zvol.rules is as follows:
# Persistent links for zvol
# persistent disk links: /dev/zvol/dataset_name
# also creates compatibility symlink of /dev/dataset_name
KERNEL=="zd*" SUBSYSTEM=="block" ACTION=="add|change" PROGRAM="/lib/udev/zvol_id $tempnode" SYMLINK+="zvol/%c %c"


Not sure if there is a missing hook file/action or a file system permissions blocking the creation of the link. Perhaps something else.

I'm at a loss for the next steps in identifying the underlying issue here and looking for guidance to resolve the problem.

What are the steps to troubleshoot and resolve this issue?
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!