Deleted directory shows up under node

fw116

Member
Apr 24, 2024
37
2
8
Hi,

after some testing i have a strange behavior.

i created and deleted some disks , lvm and directories, but the ones i deleted are still visible in the web interface after i deleted them.

i think the web interface in in an early stage and that's also the reason, why i can't create and change the LVM settings over the web interface.

i guess the old directory mount points are still in the database and are not deleted. the question is why.
would be also a + if you can change that via the web interface
 
Last edited:
Hi,
how did you delete the disks? If you go to e.g. [Your Node] > Disks > Directory > More > Destroy you can already select that the systemd mount unit and storage configuration are cleaned up too.
 
Please check the log for the Directory websrv.storage - Remove task then. It should indicate why removal failed. You can just disable and remove the systemd unit manually to get rid of it:
Code:
systemctl stop mnt-pve-websrv.storage.mount
systemctl disable mnt-pve-websrv.storage.mount
rm /etc/systemd/system/mnt-pve-websrv.storage.mount
 
And it seems you also have it still in the storage configuration. Are you sure the Cleanup Storage Configuration checkbox was ticked during removal? You can go to Datacenter > Storage and remove the left-over there.
 
  • Like
Reactions: Occy
I have the same issue. Removed via Datacenter. The entry was removed from /etc/pve/storage.cfg but the list entry, mount point and systemd unit remain.
I stopped and disabled the systemd unit so I could remove the physical disk.
Now if I try to Destroy via the node I get Error: not a valid block device.
 
Hi,
I have the same issue. Removed via Datacenter. The entry was removed from /etc/pve/storage.cfg but the list entry, mount point and systemd unit remain.
I stopped and disabled the systemd unit so I could remove the physical disk.
Now if I try to Destroy via the node I get Error: not a valid block device.
you need to deselect the Cleanup Disks checkbox, because otherwise, it will try to access the disk that's not present anymore.
 
  • Like
Reactions: eblucas