Wow, I think I just seriously screwed up while testing a BASH script that was meant to disable/mask all of my orphaned ceph services. I thought I had the actual systemctl command commented out, but alas...I was wrong. I ended up passing 'pve' to it instead, trying to test with something that would have multiple services returned, and it masked etc-pve.mount. I tried unmasking but I think I may have inadvertently made it worse. The box is online and reachable, but dead in the WUI. Is there anything I can do, short of a reinstall, to recover from this blunder?
![proxmox-etc-pve.mount.png proxmox-etc-pve.mount.png](https://forum.proxmox.com/data/attachments/16/16169-e40df7fff0e1eb4b0e600b6cb2d2c687.jpg)
Code:
root@box02:~# ./mask-services-with-name-like.sh pve
Are you 100% sure you want to stop, disable, and mask the hell out of etc-pve.mount? (y/n)y
Answer: y
Let's mask some stuff!
masking and stopping: etc-pve.mount
Created symlink /etc/systemd/system/etc-pve.mount → /dev/null.
Are you 100% sure you want to stop, disable, and mask the hell out of mnt-pve-backups.mount? (y/n)^C
root@box02:~# vim mask-services-with-name-like.sh
[1]+ Stopped vim mask-services-with-name-like.sh
root@box02:~# systemctl --now unmask etc-pve.mount
Removed /etc/systemd/system/etc-pve.mount.
root@box02:~# systemctl enable etc-pve.mount
Failed to enable unit: Unit file etc-pve.mount does not exist.
![proxmox-etc-pve.mount.png proxmox-etc-pve.mount.png](https://forum.proxmox.com/data/attachments/16/16169-e40df7fff0e1eb4b0e600b6cb2d2c687.jpg)
Last edited: