[SOLVED] Proxmox stuck after pve kernel reboot
- Thread starter Jannoke
- Start date
Have you verified that it gets indeed stuck? Have you tried to connect to the machine via network, e.g. ssh to it or just ping it?
Maybe just the display output freezes.
Should work the same here as for the installer, as you are also booting with GRUB2.
Maybe just the display output freezes.
Since you are using a Nvidia card, please try setting the
nomodeset kernel parameter: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#nomodeset_kernel_paramShould work the same here as for the installer, as you are also booting with GRUB2.
Thanks. this was it "indeed stuck" made me rethink everything.
Switched to AMD 6600XT as it was quick way to find out and it worked straight away. There was additional problem going on - after installing pve kernel my network adapter changed from ens7s0 to ens6s0. This was the reason for no lan as it did not get activated anymore. I understood that naming was made so adapter names would be more consistent, but I have often disabled it and went ahead with eth0 etc. especially machines with single lan.
Looking back there was a hint, that something works in there as pressing power switch took 2-3s to turn off machine meaning there was proper shutdown procedure going on - hence machine WAS indeed working.
After adding "nomodereset" it worked on nvidia also. i have done around 15 nvidia installs and never got this problem. Also this disk actually came from nvidia proxmox machine. Just moved over disk so i don't need to reinstall. And it "did not boot" also. so made a clean install and hit the same wall. Could've saved some hours if I googled a little better. But i guess no lan threw me off too fast.
Switched to AMD 6600XT as it was quick way to find out and it worked straight away. There was additional problem going on - after installing pve kernel my network adapter changed from ens7s0 to ens6s0. This was the reason for no lan as it did not get activated anymore. I understood that naming was made so adapter names would be more consistent, but I have often disabled it and went ahead with eth0 etc. especially machines with single lan.
Looking back there was a hint, that something works in there as pressing power switch took 2-3s to turn off machine meaning there was proper shutdown procedure going on - hence machine WAS indeed working.
After adding "nomodereset" it worked on nvidia also. i have done around 15 nvidia installs and never got this problem. Also this disk actually came from nvidia proxmox machine. Just moved over disk so i don't need to reinstall. And it "did not boot" also. so made a clean install and hit the same wall. Could've saved some hours if I googled a little better. But i guess no lan threw me off too fast.