Resolving a problem with failure to boot

Light path LEDs might indicate a hardware failure on SAN Volume Controller 2145-DH8 . SAN Volume Controller 2145-SV1 does not have light path LEDs, but it does have some diagnostic LEDs.Diagnostic LEDs might indicate a hardware failure on a SAN Volume Controller 2145-SV1 .

Before you begin

If the SAN Volume Controller software is not running, then the node status and battery status LEDs are off. The service interfaces such as the technician port and statask.txt on a USB flash drive do not work.

Note: The SAN Volume Controller 2145-SV1 node fault LED can flash when a warning or critical error shows in the BMC event log (SEL). The warning or critical error prevents the SAN Volume Controller code from booting.

If the SAN Volume Controller software is running, then the node error LED might be on. The node error code and error data can be seen by connecting to the technician port or by using the other service interfaces. Look up the node error code in the IBM® SAN Volume Controller Knowledge Center .

About this task

Complete the following steps if the SAN Volume Controller software is not running.

Procedure

Connect a monitor to the VGA port and a keyboard to a USB port. Consider any error messages on the monitor.
For example, was it unable to find a device from which to boot? (Check that the SAS cables between the boot drives and the main system board are connected correctly.)
If no useful messages display on the monitor, complete the following steps.
1. Power off the system by using the power button.
2. Disconnect the power cables.
3. Wait for 1 minute.
4. Reconnect the power cables. The node attempts to power on.
5. If the power LED comes on green, then watch the VGA monitor for any useful messages.
Attempt to access the UEFI setup utility on the VGA monitor by powering off, and then powering on by using the power button while you hold down the ESC or Delete key for the SAN Volume Controller 2145-SV1 , or the F1 key for the SAN Volume Controller 2145-DH8 . If the Setup Utility displays, complete the following steps.
1. If the node fault LED is flashing, access the Bmc self test log from the Server Mgmt tab to look for a cause.
2. Access the System Event Log from the Server Mgmt tab. Events in this log might help to pinpoint the problem.
If by using the setup utility you are unable to pinpoint a broken component, or if the setup utility does not start, complete the following steps. It is best to initially investigate a fault with the DIMMs.
1. Power off the system by using the power button.
2. Disconnect the power cables.
3. Remove the DIMMs but leave in one DIMM per microprocessor (CPU). For example, leave the DIMM in the first DIMM slot of each CPU.
4. Reconnect the power cables. The node attempts to power on.
5. If the SAN Volume Controller software now boots and the node fault LED comes on, then one of the DIMMs that you removed might be broken. Repeat the steps with a different DIMM until you find the broken DIMM.
6. If all the DIMMs work when only one is fitted per CPU, then refit the DIMMs.
If the SAN Volume Controller software does not load with all of the tested good DIMMs fitted, complete the following steps. It is best to investigate a fault with the CPUs before you consider replacing the system board.
1. Power off the system by using the power button.
2. Disconnect the power cables.
3. Remove the CPU labeled as CPU 1 on the system board.
4. Reconnect the power cables. The node attempts to power on. If the SAN Volume Controller software now boots and the node fault LED comes on, then the CPU that you removed might be broken.
5. If the SAN Volume Controller software does not boot, swap the CPUs. If the SAN Volume Controller software now boots and the node fault LED comes on, then the CPU that you removed might be broken.
If you did not find any evidence of a broken DIMM or CPU, contact IBM Remote Technical Support. They might want to know the state of the SAN Volume Controller 2145-SV1 system board LEDs.