services masked after ifupdown2 uninstall.

Nov 10, 2021
7
1
23
46
Hello all.

Well. It seems that I have kinda screwed up my proxmox install (definitely not an expert). I was messing around in my network setting in the gui, and was tired of rebooting. I am on the enterprise repo without a sub, and I install ifupdown2 from the command line. I get some error about it not being the correct version or something, so I apt remove it and reboot. Now no network. I finally get the networking back up after an hour or so, but now have a new problem: pve isnt staring up. systemctl status brings up that it is masked. So I do a systemctl list-unit-files and there are a lot of things that are masked. The output is attached in a txt file. Now, my question: Obviously If I set the pve related stuff back to the unmasked as shown in the table, I assume that will bring me back up. What I am unsure of is did the ifupdown2 BS mask the other things such as hwclock.service and cryptdisks.service? Should I put everything back to vendor preset? Thanks in advance.
 

Attachments

I tried looking around for some answers, but couldnt find much. I did a configuration backup early last month, so I decided to try to enable everything. It didnt go well. Pve and qemu were no longer there. I swapped over to the non-sub repo and did a dist-upgrade as as last ditch effort before reinstall, and it seems to have worked. I did have to manually install pve-manager, but I had to do that when I upgraded to 7 for some reason. It all appears to be working as intended, and as a added bonus ifupdown2 installed during the upgrade which I what I was trying to do in the first place. I have no idea why it all blew up in my face, but I am hoping that it is fixed now.