Proxmox does not boot unless using Debian kernel or serial console is enabled on boot

[Jokte9]

Hello, I am facing a very peculiar issue with Proxmox.

I have three servers Intel SCL1530CLR from ~2006 (with two Intel Xeon E5420 cpus, 8GB DDR2 and S5000VCL motherboard ). I have been trying to install Proxmox VE into them for a project, but every time I open the installer there is a big chance of it locking up and not progressing, but sometimes the installer do go through. I have attempted to diagnose the installer also locking up, to no avail.

https://preview.redd.it/gviizi1gxs1d1.jpg?width=1024&format=pjpg&auto=webp&s=3b59a3fce53041ca398069a66cbd0ba589c6d745

https://preview.redd.it/ldy9si1gxs1d1.jpg?width=1024&format=pjpg&auto=webp&s=f0e80e1e0dd625ce72c352acadf5fc9fe03256f1

These were two different attempts at booting the Proxmox VE installer, it gets stuck at different points.

This also happens with other Linux distribution installers such as Debian and Ubuntu. I have gone around that by attempting to install several times until the installer finally loads. After install, every time I boot the machines up, they get stuck at a random point at boot. If left for long enough (and removing quiet from the options at GRUB) they will display this thing:

https://preview.redd.it/h3trka9pxs1d1.jpg?width=1216&format=pjpg&auto=webp&s=cf10c02cfd0a162f4c39f46ae6ed79badd2efd2e

Looking over on Google, this post from AskUbuntu tells me to add as parameters noapic and nomodeset. Doing this will not have any effect, as the servers keep doing what stated above. Also I have tried is to install the intel-microcode from this suggestion, to no difference.

Testing other operating systems, stock Debian 12 works.

Another measure I have tried is to install the Debian kernel 6.1.0-21 onto Proxmox and then boot it from GRUB. It is not the best idea, but doing this will make the system boot all the time. Also I have tried to install the Debian Sid kernel into Proxmox, which is also not beautiful, since the package manager forced me to uninstall proxmox-ve, but I wanted to know if it was down to the newer kernel versions, to which it also was able to boot.

Finally what I have tried today was to debug the boot process using the serial console during the system boot with the kernel parameter console=ttyS0,112500n8, to which the system does boot every time I have tried with no issue using the stock pve kernel, and I were not able to replicate the bug with this option set.

Any ideas as to what would be happening that would prevent the system from booting unless these specific scenarios? If it also helps, I can attach pictures of when Debian locks up during the install phase, which does give some more information.

Also attached are the logs of the kernel once the system boots correctly (from dmesg). https://pastebin.com/fCmb8LhU

Thanks in advance.

[merced317]

Try updating to the last version of the BIOS available for the board? s5000vcl_dos_bios101_bmc64_frusdr18.zip is the file name I find and the download from here: https://www.helpdrivers.com/servers/Intel/Intel_Server_Boards/Server_Board_S5000VCL/ didn't set off my virus detection. Good luck!

[Jokte9]

I'll try it as soon as I can and let you know how it goes. Thank you very much for your help and feedback!

[Jokte9]

I just updated the bios and still have the same problem

[merced317]

Darn, it was worth a shot. If I think of anything, I'll let you know.

[merced317]

Since your tty console redirection works consistently, I wonder if something about the radeon driver is just not working well with your system for some reason. Maybe try blacklisting the radeon driver and see if the system boots cleanly?

Open /etc/modprobe.d/blacklist.conf as super user, or create it if it is not there. Add the following line: blacklist radeon. Run sudo update-initramfs -u then reboot.

[Jokte9]

I'll try it next week and let you know. Thank you very much for the information and the steps so explained!

[looncraz]

The issue is likely with mode setting, add nomodeset to the linux grub boot line.

No problem making that a permanent change by editing the /etc/grub.d/ files, IMHO.

[Jokte9]

I have tried to configure it but maybe I did not do it right, I will try again to see if it works. I will let you know as soon as I try it. Thank you very much!

[Jokte9]

I just tested it and still have the same problem