Proxmox & Startlvm : error on removing disk when canceling HDD Move Storage
Posted: Fri Sep 25, 2026 9:08 am
Hello,
I'm using
PVE : 9.2.20
Starlvm starwind-proxmox-plugin-pve9 : 1.1.41
NAS : Synology
VM 101 before
On VM ID 101, I do a "move storage" on disk and while task is still running I cancel it.
Target datastore is on a Starlvm storage.
At this stage, task is already cancelled, but HDD on target datastore are still here
Move HDD to Starlvm storage : NO OK
There is no "Task OK" or "Task Error" at the end of log...
And orphaned HDD can't be remove as there are linked to VM ID 101
But no orphaned HDD on VM 101
Then I was able to remove orphaned HDD.
But there is really a bug as moving HDD to local storage does NOT create an orphaned HDD
I'm using
PVE : 9.2.20
Starlvm starwind-proxmox-plugin-pve9 : 1.1.41
NAS : Synology
VM 101 before
- before.png (4.89 KiB) Viewed 1031 times
Target datastore is on a Starlvm storage.
At this stage, task is already cancelled, but HDD on target datastore are still here
- after.png (7.65 KiB) Viewed 1031 times
Code: Select all
ransferred 2.4 GiB of 80.0 GiB (3.00%)
transferred 3.2 GiB of 80.0 GiB (4.00%)
transferred 4.0 GiB of 80.0 GiB (5.00%)
transferred 4.8 GiB of 80.0 GiB (6.01%)
transferred 5.6 GiB of 80.0 GiB (7.01%)
transferred 6.4 GiB of 80.0 GiB (8.01%)
transferred 7.2 GiB of 80.0 GiB (9.01%)
transferred 8.0 GiB of 80.0 GiB (10.01%)
transferred 8.8 GiB of 80.0 GiB (11.01%)
transferred 9.6 GiB of 80.0 GiB (12.01%)
transferred 10.4 GiB of 80.0 GiB (13.01%)
transferred 11.2 GiB of 80.0 GiB (14.01%)
transferred 12.0 GiB of 80.0 GiB (15.01%)
transferred 12.8 GiB of 80.0 GiB (16.02%)
transferred 13.6 GiB of 80.0 GiB (17.02%)
transferred 14.4 GiB of 80.0 GiB (18.02%)
transferred 15.2 GiB of 80.0 GiB (19.02%)
transferred 16.0 GiB of 80.0 GiB (20.02%)
transferred 16.8 GiB of 80.0 GiB (21.02%)
transferred 17.6 GiB of 80.0 GiB (22.02%)
transferred 18.4 GiB of 80.0 GiB (23.02%)
unsupported storage of vg 'swvgLUN4thin'
deleting vm-101-disk-0 from swvgLUN4thin/lvmth-101And orphaned HDD can't be remove as there are linked to VM ID 101
- Orphaned HDD.png (21.51 KiB) Viewed 1031 times
Code: Select all
root@pve-2:~# qm disk rescan
rescan volumes...
unsupported storage of vg 'swvgBIGBIGlun'
unsupported storage of vg 'swvglunbd'
unsupported storage of vg 'swvgBACKUP'
unsupported storage of vg 'swvgLUN4thin'
VM 101 add unreferenced volume 'swvgLUN4thin:vm-101-disk-0' as 'unused0' to config
VM 107 add unreferenced volume 'swlunBD:vm-107-disk-0' as 'unused0' to config
VM 107 add unreferenced volume 'swlunBD:vm-107-disk-1' as 'unused1' to config
VM 107 add unreferenced volume 'swvgLUN4thin:vm-107-disk-0' as 'unused2' to configBut there is really a bug as moving HDD to local storage does NOT create an orphaned HDD