during disk monitoring in virtual machines.

parashu

New Member
May 27, 2025
1
0
1
We have identified that when a disk is deleted from the top of the list (e.g., PHYSICALDRIVE0, PHYSICALDRIVE1), the serial number and name of the deleted disk get reassigned or swapped with the disk immediately below it. This results in incorrect tracking of disk identities across monitoring cycles.

However, this issue does not occur when a disk is deleted from the bottom of the list — in such cases, disk mappings remain consistent and accurate.
 
Hi @parashu , welcome to the forum.

Perhaps you can enhance your report with the following information:
PVE version (pveversion -v)
Host composition (solo, cluster)
Initial VM configuration
Exact sequence of the commands (or equivalent GUI steps)
Resulting VM configuration
Output displaying the issue (text block within CODE tags is preferred)

Cheers


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: parashu