[SOLVED] Proxmox like dead after unexpected shutdown
- Thread starter prox_noob
- Start date
hi,
please run
if you can SSH to your server then you can check the journals for any apparent error messages.
please run
journalctl -b0 > journal.txt and attach your journal here if you need help, along with the output from pveversion -v on your server.
seems like
excerpt from your log:
the error mentions that the mountpoint is not empty, it's talking about the cluster filesystem that's normally mounted in
so it seems like you might have some files on there.
you could do the following to take a backup of the directory and restart the service to see if it helps:
if that works you should be able to restart the rest of the services
hope this helps
[0]: https://pve.proxmox.com/pve-docs/chapter-pmxcfs.html
pve-cluster service is not running correctly, that's why the other services aren't coming up either.excerpt from your log:
Code:
1258 Jun 22 10:27:24 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
1259 Jun 22 10:27:24 pve pmxcfs[1087]: fuse: mountpoint is not empty
1260 Jun 22 10:27:24 pve pmxcfs[1087]: fuse: if you are sure this is safe, use the 'nonempty' mount option
1261 Jun 22 10:27:24 pve pmxcfs[1087]: [main] crit: fuse_mount error: File exists
1262 Jun 22 10:27:24 pve pmxcfs[1087]: [main] notice: exit proxmox configuration filesystem (-1)
1263 Jun 22 10:27:24 pve pmxcfs[1087]: [main] crit: fuse_mount error: File exists
1264 Jun 22 10:27:24 pve pmxcfs[1087]: [main] notice: exit proxmox configuration filesystem (-1)
1265 Jun 22 10:27:24 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
1266 Jun 22 10:27:24 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
1267 Jun 22 10:27:24 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.the error mentions that the mountpoint is not empty, it's talking about the cluster filesystem that's normally mounted in
/etc/pve/ directory [0].so it seems like you might have some files on there.
you could do the following to take a backup of the directory and restart the service to see if it helps:
Code:
tar czvf /root/etc-pve.tar.gz /etc/pve # create a backup archive of the directory contents
systemctl stop pve-cluster # stop the service just in case
rm -rf /etc/pve # clean it up
systemctl start pve-clusterif that works you should be able to restart the rest of the services
hope this helps
[0]: https://pve.proxmox.com/pve-docs/chapter-pmxcfs.html
when i paste that code and enter I only get this:
root@pve:~# tar tf /root/etc-pve.tar.gz
etc/pve/
etc/pve/pve-root-ca.pem
Idk if thats what you where looking for..
I think I tried it ´casue I was looking for solutions but in the end the code from oguz worked.
Is that a common issue if everything gets shut down all of the sudden or could that be because of something else..?
A hard reset of a server is never good and you will loose more or less data, especially if you got consumer SSDs and so one without a powerloss protection. So its always a good idea to put your server behind a UPS (useful ones start at 50$) that gracefully shutdowns your server on an power outage so such problems won't happen in the first place.