Hi @zwebb
Here's the procedure for getting into the Boot Menu:
1) After turning on the antsle, keep tapping [F11] to get into the Boot Menu.
2) You can try choose another Boot option.
3) Then navigate to Boot menu. Choose the correct drive.
See attached screenshot as an example. Your configuration may be different.
Here are the instructions for doing fresh install or factory reset of your antsle One. This will get you on the latest version of edgeLinux and antMan:
https://docs.antsle.com/get-started/getting-started-with-edgelinux-software-only-version
For the antsle display getting stuck, can you let us know what numbers or code it gets stuck on? The code should be on the bottom left or right.
Thank you,
antsle Support
The code in the bottom right displays, what looks like, F1. In the bottom left, the message "system initializing" is present with a set of 3 blinking dots.
Over the weekend, I was still having issues getting stuck at JUST the SuperMicro Splash screen. I thought maybe a drive or OS was bad, so I opened the Antsle case, removed one of the HDDs, and installed a fresh image of EdgeLinux on the drive via another PC. When I returned the drive with the new OS to the Antsle and powered it on, it was still getting stuck at the splash screen. I thought this was REALLY odd. So, just for the sake of troubleshooting, I unhooked the SATA and power cables to ALL of the drives and powered on the Antsle... only to see the same SuperMicro splash screen. The device did not even throw an error message indicating that none of the drives were disconnected. Any idea how to get passed this? Is there an issue with the board... or is this Antsle Pro now a brick? Thanks! @daniel-luck
The error code in the bottom left also appears to change from "15 to "F1."
@zwebb
I'm sorry that to hear that you are having trouble with your antsle One.
I've reached out to our team regarding the error codes you are receiving.
Thank you,
antsle Support
Hi @zwebb
Feel free to send an e-mail to [email protected] so they can look into this further.
Thank you,
antsle Support
Hi @zwebb
This condition can be caused by bad memory.
We have found this article on Server Fault that may be helpful:
https://serverfault.com/questions/957635/supermicro-server-stuck-at-boot-0xf1-recovery-condition-triggered-by-user-for
Thank you,
antsle Support
