I've been using Proxmox VE 7.0.1 for about 6 months and just now ran into the second instance of the GUI not working (it starts to load but nothing is displayed & ext js errors show in browser console).
Using SSH to connect then systemctl to try and restart the UI just returned errors (sorry, I don't have them avail. now) and attempting to update complained about a read-only drive somewhere (again, no actual message avail. to share).
From the physical console I am able to reboot, but it just shows these messages:
I ran
I ran it again just to be sure and I didn't get any of the scary "count wrong" or "bitmap differences" stuff, but did get the finale FILE SYSTEM WAS MODIFIED for some reason. The console
While this does seem to have resolved my current issue (GUI & VMs work and I'm now on v7.1-10) without having to re-install, does anybody have thoughts on why this has happened to me twice now and/or how I can avoid it in the future?
Thanks.
Using SSH to connect then systemctl to try and restart the UI just returned errors (sorry, I don't have them avail. now) and attempting to update complained about a read-only drive somewhere (again, no actual message avail. to share).
From the physical console I am able to reboot, but it just shows these messages:
/dev/mapper/pve-root contains a file system with errors, check forced.
/dev/mapper/pve-root:
Inodes that were part of a corrupted orphan linked list found.
/dev/mapper/pve-root: UNEXPECTED INCONCISTENCY; RUN fsck MANUALY.
(i.e., without -a or -p options)
fsck exited with status code 54
the root filesystem on /dev/mapper/pve-root requires a manual fsck
I ran
fsck -f -c -y /dev/mapper/pve-root
and it scrolled a bunch of Free blocks count wrong
and Inode bitmap differences
messages all with a Fix? yes
following them and ultimately said /dev/mapper/pve-root: ***** FILE SYSTEM WAS MODIFIED *****
.I ran it again just to be sure and I didn't get any of the scary "count wrong" or "bitmap differences" stuff, but did get the finale FILE SYSTEM WAS MODIFIED for some reason. The console
reboot
command didn't work at that point so I did a manual power cycle.While this does seem to have resolved my current issue (GUI & VMs work and I'm now on v7.1-10) without having to re-install, does anybody have thoughts on why this has happened to me twice now and/or how I can avoid it in the future?
Thanks.