Step Condition Action
4c Cannot find a boot disk. The iLO 3 MP is
running.
Nothing can be logged for this condition.
1. Check the disk drive LED.
2. Examine the Smart Array POST message.
3. If FC storage is used for boot, check the FC
card status with the offline utility (drvcfg).
4. Reinsert the boot disk into the drive bay.
5. Search for the boot disk path using the UEFI
shell (map-r) command.
6. Examine the iLO 3 MP logs for entries related
to processors, processor power modules, and
shared memory, and core I/O devices (see
Errors and error logs on page 103 for more
details).
7. As a last resort, replace the server blade. This
issue is fixed when all boot paths are found.
5 Cannot see OS prompt on system
console. iLO 3 MP is running.
Nothing can be logged for this condition.
1. Examine the console message.
2. Verify the console configuration with the UEFI
conconfig command.
3. Examine the iLO 3 MP logs for entries related
to I/O devices (see Errors and error logs on
page 103 for more details). This issue is fixed
when the OS prompt appears on the system
console.
NOTE:
All events listed below are logged in both FPL and SEL unless otherwise noted. An event of alert
level 2 or greater will be logged in both places, alert level 1 or 0 is logged in FPL only.
6a "POWER_FAIL_NO_SBL" - Power
command failed because no Blade Link is
installed.
1. Be sure that the Blade Link is properly
installed and fully seated.
2. Look for bent connector pins on the Blade Link
6b "SBL_REMOVED" - Blade Link was
removed
1. If the Blade Link was not removed, be sure
that is properly installed and fully seated.
2. Look for bent connector pins on the Blade
Link.
6c "ILO_RST_REASON_SBL" - The iLO 3
was reset because the Blade Link was
installed (FPL only).
1. Be sure that the Blade Link is properly
installed and fully seated.
2. Look for bent connector pins on the Blade
Link.
Table Continued
Troubleshooting 89
To Next Page
Loading...
Need help?
General