[SOLVED] How i can remove directory-entry from gui?

[ChrisDB]

Why does everything have to be half-arsed?
There are create buttons for LVM, LVM-Thin, Directory and ZFS. Why not add the delete/format buttons as well?
I can't imagine them to be much different that the create buttons. They can probably be added in 5 minutes by whomever added the create buttons.
Ugh.

 

[illuminatus]

Why does everything have to be half-arsed?
There are create buttons for LVM, LVM-Thin, Directory and ZFS. Why not add the delete/format buttons as well?
I can't imagine them to be much different that the create buttons. They can probably be added in 5 minutes by whomever added the create buttons.
Ugh.

Yeah... this raises so many frustration to me also.
Maybe paid subscription support have more job because of that

 

[hermeson]

having the same issue....

 

[ChrisDB]

This is what I ended up doing.
Every disk directory entry has a file located at /etc/systemd/system/mnt-pve-<name>.mount.
To remove it, make sure mount is not used anywhere and do:

systemctl stop mnt-pve-<name>.mount
systemctl disable mnt-pve-<name>.mount
rm /etc/systemd/system/mnt-pve-<name>.mount

And to be able to add it again remove partition with `fdisk /dev/<disk name>` or `wipefs -a /dev/<disk name>`.
Use the same /dev/ path as the one that was in the .mount file at `What` field.
You can identify disk names with `lsblk' or `df -h`, then find it in /dev/.

 

[fireon]

I have now written this article on the subject and better understanding. (German only)

 

[ferociousmilkyway]

Same issue. Added blank drive via gui, drive recently failed, removed drive. Multiple reboots later I don't see a way to remove the now missing drive and experience several minutes of delay on bootup as PVE looks for the drive.

I will follow the instructions in this thread, and am sure they will work, but I'm unsure if this is expected behavior (manual removal required) or if we've (the posters) all done something wrong.

 

[da-alb]

This bug is still here in 1.1-5 version. Manual removal works

 

[cody0922]

still happens on 7.0-11

rm /etc/systemd/system/mnt-pve-<directory_name> is still the fix

 

[da-alb]

I agree, same here

 

[wegiii]

Still present, 7.0-11.

Thanks @ChrisDB for the nipple feed.

 

[mikeinnyc]

Use shell in Proxmox
stop the service before moving ahead
To find the EXACT NAME of the Mount file(s) you need to delete
you will see something like this mnt-pve-Backups.mount

#cd /etc/systemd/system
#ls
#rm mnt-pve-Backups.mount (use your own file mount name to remove)
#rm mnt-pve-Downloads.mount (if you have more file mounts names to remove)

# ls list the files and folders again to see if removed

# nano /etc/pve/storage.cfg
delete those dir references and save

Reboot or Stop and Start a Service

#cd /etc/systemd/system
#systemctl stop pvedaemon.service
#systemctl start pvedaemon.service
#systemctl status pvedaemon.service
# systemctl stop pvestatd.service
# systemctl start pvestatd.service
# systemctl status pvestatd.service



OR Do it all in one line Restart multiple Services
#service pve-cluster restart && service pvedaemon restart && service pvestatd restart && service pveproxy restart

if you have other stopped services and can't reboot find them
#systemctl list-units --type service --all

Hope this helped

 

[khampol]

did you delete the systemd mount unit file?
/etc/systemd/system/mnt-pve-testdir.mount

Sorry bump this *old* topic in 2021.
But really hope have this function by system. Not too risky to have to do this manually ??

 

[dec]

There is now a destroy button in the more sub-menu.
But note that it works only if the device is still plugged-in (otherwise you will have this error: not a valid block device).

 

[mikeinnyc]

I came back to my notes and yes that's an awesome feature now!

 

[LaviS]

Hello together!

Here is the solution which always works.

There is now a destroy button in the more sub-menu.
But note that it works only if the device is still plugged-in (otherwise you will have this error: not a valid block device).


View attachment 37781

If you can not delete it via the GUI as in the post of "dec" works the following solution:

Open a shell.
Then navigate to the directory /etc/systemd/system.
Then do a ls -al and you should see the following:

'mnt-pve-pveXX\x2dYOURNAME.mount'.

You can delete it now, and the entry in the GUI should be gone.
I hope I could help, if you have any questions, feel free to ask me.
Greets Clemi361

 

[veks]

I did, but I still get the same error:
TASK ERROR: unable to create VM 111 - unable to activate storage 'BACKUP_proxmox' - directory is expected to be a mount point but is not mounted: '/mnt/pve/BACKUP_proxmox'
Any way to solve this?

 

[mikeinnyc]

# nano /etc/pve/storage.cfg add the mount point. next time backup or save /etc files or this file /etc/pve/storage.cfg
example:
dir: local
path /var/lib/vz
content iso,vztmpl,backup

zfspool: local-zfs
pool rpool/data
content rootdir,images
sparse 1

zfspool: SSDPool
pool SSDPool
content rootdir,images
mountpoint /SSDPool
nodes NODE1

zfspool: DASPool01
pool DASPool01
content images,rootdir
mountpoint /DASPool01
nodes NODE1

 

[qatar2022]

This is what I ended up doing.
Every disk directory entry has a file located at /etc/systemd/system/mnt-pve-<name>.mount.
To remove it, make sure mount is not used anywhere and do:

systemctl stop mnt-pve-<name>.mount
systemctl disable mnt-pve-<name>.mount
rm /etc/systemd/system/mnt-pve-<name>.mount

And to be able to add it again remove partition with `fdisk /dev/<disk name>` or `wipefs -a /dev/<disk name>`.
Use the same /dev/ path as the one that was in the .mount file at `What` field.
You can identify disk names with `lsblk' or `df -h`, then find it in /dev/.

this is really help me

 

[8192K]

Still happening in 8.2.2

 

[Dr.ive]

Still not fixed 8.2.4
I did all the systemctl stop and - disable and rm mnt-<name> thing, and the gui still shows the directory.
The destroy button shows me a "Task failed - not a valid block device" Error.
What am I missing?
I guess Proxmox is more for advanced Linux cmd people. I really struggle with stuff like this.
Thank u guys for beeing active in the forum