r/supermicro • u/MoriorL • 11d ago

X9DRL-iF Boot Issue

Post image

I was given a PC with a X9DRL-iF motherboard. Whenever I boot it up, it gets stuck on this step where it gives two short beeps and has F2 in the bottom right. Has anyone else ran into this issue before and know how to fix it? It seems a lot of people run into a 2F error, but I haven't found any documentation on a F2 error.

Additionally I did have the thought that it just needed me to press F2 on the keyboard, however I tried that and it didn't work.

3 Upvotes

80% Upvoted

7 comments sorted by

2

u/kumits-u 11d ago

F2 is usually RAM memory - try with only 1 ram stick, also try to reseat the rams etc. If still doesn't boot on 1, try removing power and CMOS battery, leave like this for 10 min and try again

2

u/MoriorL 11d ago

Sounds good! I will try that, thanks!

3

u/IntelligentLake 11d ago edited 11d ago

Actually, F2 is 'recovery process started' see the POST codes. In other words, the BIOS is corrupted and it is trying to find the Super.ROM file on a device to flash it.

You can get this BIOS from the board's page under 'update your BIOS' and put the X9DRL8.712 file inside of it on the root of an USB stick formatted as FAT12, FAT16 or FAT32 and rename it Super.ROM, insert it, and start the computer.

Edit: Here is a FAQ on the issue and the entry on recovery which links to the procedure with a slightly different filename. The CMOS clear procedure is in the manual on page 2-36. Do not only remove the CMOS battery, this will only corrupt settings, not clear them.

1

u/kumits-u 11d ago

In faq it says its stuck on f9 after f2... User has f2 issue which is ram memory ;)

2

u/IntelligentLake 11d ago

Wrong. Read the POST codes I linked to which is for various series of Supermicro motherboards, including X9. F2 is 'recovery process started', which happens when a corrupt BIOS is detected.

2

u/MoriorL 11d ago

It looks like the two beeps also mean recovery started, so I believe you are correct. Thanks for the recommendation!

2

u/MoriorL 11d ago

I did try reseating all the RAM, unfortunately that didn't fix it. I will try flashing the BIOS like the other comment recommended next. Appreciate the feedback!