Hey folks! I'm in the process of building a lightweight server intended to run Proxmox and handle a few virtualized services. I've run into a frustrating issue where the server powers on but gets stuck during the PEI phase, which means I can't even reach the BIOS.
Here's the setup:
- **CPU:** ThinkSystem Xeon Silver 4410Y 2GHz
- **Motherboard:** Supermicro X13SEI-TF LGA 4677
- **RAM:** 2x Lenovo ThinkSystem 32GB TruDDR5 5600MHz RDIMM
The screen lights up, but after a few reboots, it stops and displays a debug code 09 along with the error message "PEI MEMORY NOT FOUND." This indicates an issue detecting the RAM. I've come across some suggestions that Lenovo RAM might have custom firmware that makes it incompatible with non-Lenovo motherboards.
I'm also considering updating the BIOS using remote configuration to see if that helps.
I've already tried resetting the CMOS and ensuring the RAM is correctly seated in the DIMMA1 and DIMMG1 slots, along with reseating the CPU and testing with a single DIMM. Interestingly, I've faced a similar issue on a different build with entirely different components.
So I'm reaching out for any troubleshooting tips before I decide to swap out the RAM. Is it more likely that the issue lies with the RAM or the motherboard?
2 Answers
Don't lose hope just yet! If you haven't already, consider reseating the RAM and CPU again or booting with just one stick of RAM at a time. Sometimes a flaky DIMM can cause these types of issues. If you still get the same error, it might be worth trying a different brand of RAM that is known to work well with your motherboard.
First off, you'll want to check the memory QVL (Qualified Vendor List) for your Supermicro motherboard. Server boards can be quite picky about RAM compatibility, especially with OEM RDIMMs like your Lenovo TruDDR. If your RAM isn't on the supported list, it might not train correctly. While updating the BIOS can help in some cases, the best long-term fix is often going with RAM listed in the QVL.
Thanks for the tip! I suspected the compatibility might be an issue. I’ll definitely check the QVL before trying any other fixes.
That’s a good point. I’ve had similar issues where a single faulty stick would cause the server to get stuck. I’ll try that next!