Proxmox GUI and System Journal Errors after VM Disk Configuration Changes

[slopez]

Hello Proxmox Community,

I am in need of some assistance with a serious issue that arose after modifying disk configurations for a VM instance in Proxmox. Following these changes, I've lost access to both the Proxmox GUI and the TrueNAS VM. The TrueNAS VM was completely inaccessible (no TrueNAS GUI and does not startup) after shutting it (TureNAS VM instance) down and before losing the Proxmox GUI.

Problem Description:
After adding what I believe were incorrect hard disks to a TrueNAS VM intended for backing up our Active Directory, I lost access to the TrueNAS GUI. I decided to restart the VM to troubleshoot this. However, the following day, I discovered that the Proxmox GUI was also unavailable. The system logs are flooded with the following error:

Failed to write entry (24 items, 6345 bytes), ignoring: Read-only file system

It appears the filesystem has been remounted as read-only, which is preventing writes to the system journal and likely affecting the GUI's functionality.

Troubleshooting Steps Taken:

• Confirmed SSH access is still possible and all VMs and containers are running.
• Attempted to restart Proxmox services without success.
• Checked for and ruled out network issues and firewall configurations.
• Inspected disk space to ensure there is no shortage.
• Considered running a filesystem check but have not yet done so due to concerns about data integrity.

Given these events, I suspect that the disk changes may have caused some system-wide issues, possibly affecting critical storage paths or system files, leading to the GUI becoming inaccessible.

Seeking Advice:
Could the disk configuration changes have caused Proxmox to lock the filesystem in a read-only state? If so, what steps can I take to safely resolve this and restore access to the GUIs without risking data loss?

I would greatly appreciate any insights or recommendations for further troubleshooting steps from anyone who may have experienced something similar or has expertise in this area.

Thank you for your time and assistance!

 

[BobhWasatch]

Probably the most common reason for the rootfs getting remounted read-only is caused by errors from the controller. Another possibility is if you were trying to pass-thru the disk and used the wrong one and that caused corruption.

Have you tried to remount it: mount -o remount,rw /? Have you tried to boot from a live CD and check it with fsck?

 

[bbgeek17]

After adding what I believe were incorrect hard disks to a TrueNAS VM intended

So you possibly passed-through a root disk to a VM and caused fs corruption?

A quick search for "debian root filesystem read only" leads to https://unix.stackexchange.com/questions/145882/read-only-root-filesystem which seems promising.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox