[Help] Proxmox Startup Issues
1d 2h ago by adultswim.fan/u/village604 in selfhosted
Recently, when I reboot my Proxmox hardware, I'm greeted with this message after the bootloader splash screen. It won't progress any further, even after letting it sit overnight.
But restarting it 5-10 times will eventually get past it.
I suspect it might have something to do with me passing a physical disk and the whole GPU to a Windows VM (my temp solution for TV gaming until I can get Sunshine issues ironed out) but I'm not sure where to start looking for the issue.
I thought it might be freezing when the VM tries to take control of the GPU, but with a continuous ping to both the server and the VM, I never get a response. That makes me think the issue is happening before the VM is started.
I'm basically just hoping someone could point me to a log that might have a related error message.
Edit your bootloader config and turn off quiet / splash so you actually get a useful boot log.
This seems like a hardware problem. Hardware freezes would not be caused by hardware pass through to VMs. Test your RAM. Check for loose PCI cards, etc.
this can't be a hardware problem other than the power supply, because judging by the screenshot, the disks have already been initialized, which means the entire kernel has loaded into RAM and even libraries have started loading. first you need to read dmesg and check exactly where the log stopped. rather than testing everything.
Are you sure you're passing your gpu through correctly? This didn't happen to me, but a buddy of mine didn't do iommu and tried to pass the gpu through to a VM, and he couldn't boot either. If you boot rescue and change the VM to not start-up on boot? I would definitely post your grub boot line.
Respectfully, you and I are basing our feedback on incomplete information. That being said, it absolutely could be a hardware problem because the further get into the boot process, more data is loaded from disk into RAM. There isn’t some point beyond which hardware is no longer a concern.
Your point about dmesg is a valid one, provided you can even get to a login prompt. Otherwise, you’re captive to the terminal output on boot.
I reserve the right to be wrong, but my money is on bad RAM. If one wants to test the hardware without taking things apart, booting to a live USB/CD is a good option.
try read dmesg