GUI inaccessible and /etc/pve empty after hostname change

[Snowylicious]

Hello everybody,

I've tried following the instruction given by this by first changing the hostname at /etc/hosts, then in /etc/hostname and then using the move commands to change it from /etc/pve/nodes/saraprox to /etc/pve/nodes/c1-7090. I thankfully made a backup of the old node saraprox in the root folder and have all the contents of it including qemu-server and all the VMs installed in it. But after rebooting it, not only does the pve-service fail to start and spews a lot of errors, but the /etc/pve folder is now empty. The output of the journalctl gives this result out and i dont know what to do anymore. I thought changing the hostname back to saraprox would make it work again, but the error persists.

-- Boot 6dfc9ef7b44e4262868bd4f21e7f6b8b --
Jul 19 23:06:55 saraprox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Jul 19 23:06:55 saraprox pmxcfs[900]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:55 saraprox pmxcfs[900]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:55 saraprox pmxcfs[900]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:55 saraprox pmxcfs[900]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:55 saraprox pmxcfs[900]: [database] crit: DB load failed
Jul 19 23:06:55 saraprox pmxcfs[900]: [database] crit: DB load failed
Jul 19 23:06:55 saraprox pmxcfs[900]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:55 saraprox pmxcfs[900]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:55 saraprox pmxcfs[900]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:55 saraprox pmxcfs[900]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 19 23:06:55 saraprox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
Jul 19 23:06:55 saraprox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:55 saraprox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Jul 19 23:06:55 saraprox pmxcfs[1013]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:55 saraprox pmxcfs[1013]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:55 saraprox pmxcfs[1013]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:55 saraprox pmxcfs[1013]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:55 saraprox pmxcfs[1013]: [database] crit: DB load failed
Jul 19 23:06:55 saraprox pmxcfs[1013]: [database] crit: DB load failed
Jul 19 23:06:55 saraprox pmxcfs[1013]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:55 saraprox pmxcfs[1013]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:55 saraprox pmxcfs[1013]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:55 saraprox pmxcfs[1013]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 19 23:06:55 saraprox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
Jul 19 23:06:55 saraprox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:55 saraprox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Jul 19 23:06:55 saraprox pmxcfs[1015]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:55 saraprox pmxcfs[1015]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:55 saraprox pmxcfs[1015]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:55 saraprox pmxcfs[1015]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:55 saraprox pmxcfs[1015]: [database] crit: DB load failed
Jul 19 23:06:55 saraprox pmxcfs[1015]: [database] crit: DB load failed
Jul 19 23:06:55 saraprox pmxcfs[1015]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:55 saraprox pmxcfs[1015]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:55 saraprox pmxcfs[1015]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:55 saraprox pmxcfs[1015]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 19 23:06:55 saraprox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 19 23:06:55 saraprox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
Jul 19 23:06:56 saraprox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:56 saraprox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Jul 19 23:06:56 saraprox pmxcfs[1020]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:56 saraprox pmxcfs[1020]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:56 saraprox pmxcfs[1020]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:56 saraprox pmxcfs[1020]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:56 saraprox pmxcfs[1020]: [database] crit: DB load failed
Jul 19 23:06:56 saraprox pmxcfs[1020]: [database] crit: DB load failed
Jul 19 23:06:56 saraprox pmxcfs[1020]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:56 saraprox pmxcfs[1020]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:56 saraprox pmxcfs[1020]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:56 saraprox pmxcfs[1020]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 19 23:06:56 saraprox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
Jul 19 23:06:56 saraprox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:56 saraprox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Jul 19 23:06:56 saraprox pmxcfs[1024]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:56 saraprox pmxcfs[1024]: [main] notice: resolved node name 'saraprox' to '192.168.2.200' for default node IP address
Jul 19 23:06:56 saraprox pmxcfs[1024]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:56 saraprox pmxcfs[1024]: [database] crit: missing directory inode (inode = 000000000076D4B8)
Jul 19 23:06:56 saraprox pmxcfs[1024]: [database] crit: DB load failed
Jul 19 23:06:56 saraprox pmxcfs[1024]: [database] crit: DB load failed
Jul 19 23:06:56 saraprox pmxcfs[1024]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:56 saraprox pmxcfs[1024]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 19 23:06:56 saraprox pmxcfs[1024]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:56 saraprox pmxcfs[1024]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 19 23:06:56 saraprox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jul 19 23:06:56 saraprox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jul 19 23:06:56 saraprox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jul 19 23:06:56 saraprox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.

What do...? Thank you for your patience. I'd appreciate any help I could get.

 

[Snowylicious]

 

[sw-omit]

(..) and all the VMs installed in it (...)

You might have missed a small line in the tutorial you linked:

(..) This must be done on a empty node.

Meaning, it's not really supported changing your name after you have installed VM's/CT's on it or even added it to a cluster.

That said, perhaps these topics / answers of people who went before you might help you:
https://forum.proxmox.com/threads/changing-name-of-nodes-in-cluster.136623/
https://forum.proxmox.com/threads/rename-node.109846/

 

[Snowylicious]

I see... So how do I revert everything to it working again?

 

[sw-omit]

If you indeed want to revert the name (for now at least), I would suggest to start by reverting everything you changed (but also keeping those copies you had safe too) and rebooting, just to see what then does and does not work. So basically the same steps but replacing the c1-7090 with saraprox.

But like I said, if you do want to continue with the rename, take a good look through the threads linked before, and see if there are any steps you missed / did differently in your original attempt.

Third method would be to re-install with the new name and import your VM-Backups (if you already made those, else look at a guide how to export them first) and config-backups after that.

 

[Snowylicious]

The thing is that I did revert it all, and these are the errors coming out of it.

 

[sw-omit]

Ah...
You didn't happen to have made a backup of /var/lib/pve-cluster/config.db beforehand too, did you?
Cause /etc/pve isn't a "real" folder, but a database that presents itself as a folder-structure (FUSE) [1]
Looking around some, I also came across this topic with staff-replies, you might want to at least take a look at it (don't blatantly copy-past though) [2]

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_pmxcfs
[2] https://forum.proxmox.com/threads/“...rom-mistakenly-executing-this-command.139972/