Skip to main content
A POST (Power-On Self-Test) failure means the appliance’s firmware was unable to complete the hardware initialization sequence before handing control to the operating system. When this happens, the appliance will not boot into its normal operating state. Because the LARK does not have an attached monitor during typical operation, you will use the baseboard management controller (BMC) console to see what the firmware is reporting.

​
What a POST failure looks like

During a normal startup, the LARK completes POST silently and begins loading the operating system within about a minute of power-on. If POST fails, the appliance may:
  • Power on but then power off again without reaching the OS
  • Remain at a black screen without progressing
  • Emit a series of beeps (if a speaker is present in the chassis)
  • Display an error code or message visible only through the BMC console
You will typically notice a POST failure because the appliance never becomes reachable on the network and system status is unavailable in the admin UI.

​
Accessing the BMC console

The BMC (baseboard management controller) provides out-of-band access to the appliance regardless of whether the OS has loaded. You can use it to view the POST output directly.
1

Connect to the management interface

Connect a laptop to the BMC management port on the front of the appliance using the appropriate cable. The management port is separate from the data and connectivity interfaces.
2

Reach the BMC web interface

Open a browser and navigate to the BMC’s address. The BMC address is documented on the delivery record. Log in with the BMC credentials also listed on the delivery record.
3

Open the remote console

In the BMC interface, open the remote console or KVM console view. This gives you a live view of what the appliance is displaying on its virtual screen — including any POST error codes or messages.
4

Note any error codes or messages

Read the error message, code, or indication on screen. The specific code will help you identify the cause of the failure and whether it is recoverable on-site.

​
Common POST failure causes

The most common cause of a boot failure is the management and network module not being fully and correctly seated in its front slot. If the module is absent or partially inserted, the firmware may halt with a hardware detection error.Resolution: Power off the appliance, remove the module fully, and carefully reinsert it until it is flush and secured. Attempt to power on again.
The firmware tests all installed memory during POST. A memory failure will halt POST and display an error code. Memory errors can result from a transient fault (resolved by a power cycle) or a persistent hardware fault.Resolution: Power the appliance fully off, wait at least two minutes, and power on again. If the error recurs on multiple attempts, escalate to support — memory is not a user-serviceable component.
If the firmware cannot detect the primary storage device, it will report an error and decline to attempt a boot. This can indicate a loose internal connection or a failed drive.Resolution: Note the exact error message or code from the BMC console and escalate to support. Internal drive connections and drive replacement are not user-serviceable tasks on the LARK.
In rare cases, a power interruption during a firmware update or a persistent hardware fault can corrupt the BIOS. This will prevent POST from completing normally.Resolution: Escalate to support. BIOS recovery requires vendor-level intervention.
Do not attempt to modify BIOS settings on the LARK unless explicitly directed to do so by support. Incorrect BIOS configuration can prevent the appliance from booting or damage its ability to manage services.

​
When to escalate

Escalate to support if:
  • The same POST failure recurs after a power cycle and reseating the management module
  • The error code indicates a storage or memory fault
  • The appliance has no visible output in the BMC console despite the BMC being reachable
  • A firmware corruption message is displayed
See When to Escalate for guidance on what information to gather before contacting support.