I'm new to Proxmox and things had been going well. I have 2 Linux Mint VMs running and a Windows 11 VM which is not running. VM ID 102 (a Linux Mint VM) stopped booting and goes into Emergency mode instead (the other VMs work fine). So that puts me out of my wheelhouse as far as understanding how to (hopefully) fix this hence I need some help.
I did a journalctl -xb as it instructed which showed 600+ lines. I don't know how to export those log lines but I did some screenshots (attached) and copied the red text as below. Emergency mode is functional in the Proxmox console for the VM. I.e. I can run simple commands and an external USB drive is automatically mounted and usable. The network interface is not active though.
Immediately before this happened I edited the VM's /etc/fstab to change the mount point for an external USB drive. In emergency mode this drive is mounted to the correct mount point so I think the fstab is fine. Proxmox version is 8.1.4. Your guidance would be highly appreciated.
The first red line is
Being a complete n00b I don't know if that is a fatal error and my attempts to search for this error failed.
A few other red line snippets
I did a journalctl -xb as it instructed which showed 600+ lines. I don't know how to export those log lines but I did some screenshots (attached) and copied the red text as below. Emergency mode is functional in the Proxmox console for the VM. I.e. I can run simple commands and an external USB drive is automatically mounted and usable. The network interface is not active though.
Immediately before this happened I edited the VM's /etc/fstab to change the mount point for an external USB drive. In emergency mode this drive is mounted to the correct mount point so I think the fstab is fine. Proxmox version is 8.1.4. Your guidance would be highly appreciated.
The first red line is
acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration
Being a complete n00b I don't know if that is a fatal error and my attempts to search for this error failed.
A few other red line snippets
device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Feb 20 07:44:07 River kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Feb 20 07:44:07 River kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
sd 2:0:0:0: Power-on or device reset occurred