Diagnostic flowcharts
89
If you specify a networked target computer for which you do not have
administrative privileges, an error message is displayed describing the
problem, and then the program exits. Obtain administrative privileges for
the target computer, and then restart the process. Be sure the remote registry
service is running on a Windows
®
-based system.
3.
Invalid or incorrect command-line parameters
If incorrect parameters are passed into command-line options, an error
message describing the invalid or incorrect parameter is displayed and the
program exits (Example: Invalid source path for system configuration).
Correct the invalid parameter, and then restart the process.
4.
Network connection fails on remote communication
Because network connectivity cannot be guaranteed, it is possible for the
administrative client to become disconnected from the target server during
the ROM flash preparation. If any remote connectivity procedure fails during
the ROM flash online preparation, the ROM flash does not occur for the target
system. An error message describing the broken connection displays and the
program exits. Attempt to ascertain and correct the cause of connection
failure, and then restart the process.
5.
Failure occurs during ROM flash
The flash cannot be interrupted during this process, or the ROM image is
corrupted and the server does not start. The most likely reason for failure
is a loss of power to the system during the flash process.
6.
Updating firmware
To update the firmware (BIOS FW, BMC FW, HBA card FW, HDD FW, and so on):
o
Check the firmware version on the device.
o
Determine the latest firmware version available.
o
Download and update the firmware to the current version supported for the
hardware configuration.
o
Verify the firmware update by checking the firmware version.
Boot problems
Possible cause:
1.
The BIOS ROM flash fails.
2.
The system ROM is corrupt.
3.
A logical drive is not configured by the LSI RAID controller.
4.
The controller boot order is not set properly.
5.
Hardware issues.
Correction Action:
If the system ROM is corrupted, the system automatically switches to the redundant
ROM in most cases. If the system does not automatically switch to the redundant
ROM, perform the following steps:
1.
Power down the server.
2.
Remove the server from the rack, if necessary.
3.
Remove the access panel.
4.
Change the clear CMOS jumper into the clear position 2-3, then restore it
to original position 1-2.
5.
Install the access panel.
6.
Install the server into the rack.