I recently tried to install Proxmox VE 5.3 on an older SuperMicro Node:
The Problem: Proxmox wouldn't boot, neither the installer nor a finished install from another node (Blackscreen and complete server crash a few seconds after proxmox started booting)
I found several threads from people with the same problem:
At least in my case I found a fix and I wanted to share it here:
It seems that after updating the SuperMicro H8SGL-F Motherboard to the newest version, "something" in the bios configuration is set in a wrong way (probably related to the Matrox G200E iGPU) and only the "Failsafe Defaults" fix this. A CMOS reset will probably have the same effect.
It might have something to do with jumping from a very old BIOS version to the newest one in just one step - at least that's what I did before running into this problem.
Anyway, I hope this will help someone in the future.
- SuperMicro H8SGL-F Motherboard with integrated Matrox G200E Graphics
- AMD Opteron 6348
- 128GB DDR3 ECC Ram
The Problem: Proxmox wouldn't boot, neither the installer nor a finished install from another node (Blackscreen and complete server crash a few seconds after proxmox started booting)
I found several threads from people with the same problem:
- https://forum.proxmox.com/threads/supermicro-h8sgl-f-motherboard.35036/
- https://forum.proxmox.com/threads/monitor-schaltet-ab-blackscreen.51919/ (Same Matrox iGPU)
At least in my case I found a fix and I wanted to share it here:
- Update Bios to newest version (3.5b).
- Go into Bios and "Reset to Failsafe Defaults". It's not enough to use "Reset to Optimized Defaults" - don't ask me why.
- At this point the Proxmox installer should boot up fine. You can now reenter the Bios and configure everything to your liking. The Proxmox installer should still boot up after your changes.
It seems that after updating the SuperMicro H8SGL-F Motherboard to the newest version, "something" in the bios configuration is set in a wrong way (probably related to the Matrox G200E iGPU) and only the "Failsafe Defaults" fix this. A CMOS reset will probably have the same effect.
It might have something to do with jumping from a very old BIOS version to the newest one in just one step - at least that's what I did before running into this problem.
Anyway, I hope this will help someone in the future.
Last edited: