I empathise with your frustration; it can be stressful to encounter a new bug like this in hardware that's been successfully running for a long time. First, note that the user reports we've seen only indicate issues with entering BIOS setup, not normal system boot. From your description, it sounds like you are able to boot Ubuntu, so you are at least still able to boot and use the system normally, yes?Good morning, I am new to the forum even though I have been following you for a long time. Sorry for the translation, but I don't speak English. I have three x9sci-ln4f boards with the AB problem, one that I have with the freenas working fine. I have done some tests 1. Set BIOS clock to date before 2021 result after system boot, next reboot follows problem AB 2. With a live ubuntu program, the hardware clock with hwclock. Result of restarting problem AB. 3. Remove the BIOS stack. Result on restarting problem AB From the tests performed, the only way to enter BIOS is to restore cmos. Shared BIOS here is not supported by x9sci-ln4f Hope supermicro will update BIOS for all X9 boards; otherwise i will not buy supermicro again
You should be able to access the boot menu (F11) and boot that way... But if you need to change the boot order for normal use, then you will need to clear the CMOSCommenting so I'm aware of the fix.
I just started building a server with an X9SCL last night. Thought I bricked the motherboard when I get the blue screen and "AB" in the corner. I inadvertently found the workaround of clearing the CMOS, but I was able to get into the BIOS this morning.
I don't have an OS installed yet, will the board recognize my USB drive with the iso on it when it's trying to boot up, without me going into the BIOS to change the boot order?
No - this is not the same issue. We have many of the X9DRi/X9DR3 and similar boards with no issues. Only the Xeon E3v1/v2 CPU-based boards are impacted.Hi there, has anyone been able to replicate this issue on an X9DR3i-F board? I'd forgotten about this forum post until I rebooted for the first time this year today, but I'm getting code b2 and a black background screen rather than the blue described by others. I found this posting that seems like the same issue, but because this board is almost certainly impacted by the bug listed in this thread, I thought I'd ask and see if it should be the same issue as others have had here or if I should just follow the guide I linked. Thanks
Edit to note: I've tried clearing CMOS several times, and no success/change in behavior (which makes me more convinced that it's the standard b2 error rather than this thread's ab error)