Proxmox stuck in /dev/mapper/pve-root: clean

D

dpksamir

New Member
Jun 21, 2024
7
0
1
Hi All,

Recently, I moved my PC with Proxmox to a different network. I had turned it off from the browser UI, and now it does not go to the login screen gets stuck, and I am unable to access the UI interface because I don’t know the LAN IP address for Proxmox.
IMG_6AA58C86-78AF-4E53-A4D5-1E410ADAC7DE.jpeg
It is starting the VM, though, I have one Windows server running, which I can connect using RDP.


When I pressed “e” and removed “quiet,” I got the following log:

IMG_CA521EB0-2EF6-40B2-ACC7-C51BBC8C027F.jpeg

Screenshot 2024-09-17 at 3.44.24 PM.jpg

Log from recovery mode:

IMG_1702.jpg
Please help me resolve this issue.
 
Last edited:
Why not disable the WiFi in your BIOS/UEFI?

(You may want to edit your title to better reflect where it really got stuck now that you had removed the quiet.)
 
esi_y said:
Why not disable the WiFi in your BIOS/UEFI?

(You may want to edit your title to better reflect where it really got stuck now that you had removed the quiet.)
Click to expand...
thank you, I tried but did not work. I have not removed "quiet", it's still there, what could be the reason?
Below is my PC configuration:

Lenovo Legion Ryzen 7 RTX 4070 Gaming Desktop. AMD Ryzen 7 7700 64GB DDR5 RAM, 4TB SSD​

 
Last edited:
You are only removing it for the current boot (which is probably fine, once you resolve your issue, you may not care for all the output).

In the same way as you removed the quiet param, can you add: modprobe.blacklist=mt7921e and boot like that?

(Have to go now, so no quick responses after this, sorry.)
 
I had this exact issue last night after upgrading my Proxmox node from 7.4.17 to 8.2. I disabled gpu passthrough so i could have console access into the node while updating. After the update, i re-enabled the passthrough options and rebooted the server. Thats when i started having this problem. Console would freeze, shell didnt work in GUI and ssh just freezes after login. if you have all these issues i have good and bad news.

Good news: It can be fixed.

Bad news: its not simple.

This was a 2 part fix:

Step1: I removed the boot drive from the proxmox node, mounted it in another node so i could access the files, then changed grub option back to just "quiet", comment out the iommou options in modprobe/modprobe.d and whatever is in vfio.conf and update the initramfs(make sure you chroot to the location of the mount before this). After this, unmount the drive and put it back in the original node. It should start up as expected and you should be able to login through console now but the network will probably still be down so no ssh or vnc.

Step2: If your network isnt up after this, it's most likely because of mismatched interface names in `/etc/networks/interfaces` . Check that file and take note of the iface names like `ensp01`. Then run `ip addr` and check if the interface names match whats in the interfaces file. After changing the names and rebooting you should be back to normal.

Not gonna lie, it was scary af because all forms of access were disabled and i couldn't even get to recovery mode or reinstall because no way to see the display. But like i said its definitely recoverable. Good Luck.
 
esi_y said:
You are only removing it for the current boot (which is probably fine, once you resolve your issue, you may not care for all the output).

In the same way as you removed the quiet param, can you add: modprobe.blacklist=mt7921e and boot like that?

(Have to go now, so no quick responses after this, sorry.)
Click to expand...
thank you, still same issue
 
kube said:
I had this exact issue last night after upgrading my Proxmox node from 7.4.17 to 8.2. I disabled gpu passthrough so i could have console access into the node while updating. After the update, i re-enabled the passthrough options and rebooted the server. Thats when i started having this problem. Console would freeze, shell didnt work in GUI and ssh just freezes after login. if you have all these issues i have good and bad news.

Good news: It can be fixed.

Bad news: its not simple.

This was a 2 part fix:

Step1: I removed the boot drive from the proxmox node, mounted it in another node so i could access the files, then changed grub option back to just "quiet", comment out the iommou options in modprobe/modprobe.d and whatever is in vfio.conf and update the initramfs(make sure you chroot to the location of the mount before this). After this, unmount the drive and put it back in the original node. It should start up as expected and you should be able to login through console now but the network will probably still be down so no ssh or vnc.

Step2: If your network isnt up after this, it's most likely because of mismatched interface names in `/etc/networks/interfaces` . Check that file and take note of the iface names like `ensp01`. Then run `ip addr` and check if the interface names match whats in the interfaces file. After changing the names and rebooting you should be back to normal.

Not gonna lie, it was scary af because all forms of access were disabled and i couldn't even get to recovery mode or reinstall because no way to see the display. But like i said its definitely recoverable. Good Luck.
Click to expand...
how do i mount it to another drive? I'm kind of new on this, i had added few lines for nvda gpu passthrough but did not complete the steps, may be that might be the reason. is there a way to reset those lines ?
 
dpksamir said:
how do i mount it to another drive? I'm kind of new on this, i had added few lines for nvda gpu passthrough but did not complete the steps, may be that might be the reason. is there a way to reset those lines ?
Click to expand...
You have to physically take the boot drive out of the system and put it in another system. Preferably one that already has Proxmox running. Luckily I had a mini pc laying around so I used that. If the secondary system has Proxmox installed you should be able to boot from the drive you took out of the first. Then just go in and undo all the passthrough options. After that, put the disk back in the original server and it should boot.
 
You must log in or register to reply here.
Top Bottom