IBM System x POST 启动与引导设备故障诊断
Fails to POST and Boot device issue
Welcome to the POST problems section. This section covers the POST sequence of the computer. It does not cover why an OS may fails to complete the boot process. In more complex servers it may be best to be familiar with the tools needed to pull logs, VPD and BIOS information from the service processor to assist in determining why the server is not completing POST. Keep in mind that in this state, the computer is unlikely to be able to accept a flash of any kind or allow you to use a bootable tool. While a flash may be part of your action plan, it should not be the first step in your problem determination for this type of problem.
The first step in beginning this process is to determine if any changes have recently been applied to the machine prior to the inability to complete post.Before continuing please review Field Tip's / Lenovo Tech Tips / PE Corner aswell as Latest published
1. Server hangs during boot
Look for the UEFI/Post code on the server LCD display panel and contact Support and provide this number for further assistance.2. The embedded hypervisor flash device is not in the boot list
1. If the server has recently been installed, moved, or serviced, or if this is the first time the embedded hypervisor is being used, make sure that the device is connected properly and that there is no physical damage to the connectors (see “Removing a USB embedded hypervisor flash device” on page 244 and “Replacing a USB embedded hypervisor flash device” on page 245).
2. Check the Lenovo ServerProven web site to validate that the server supports the embedded hypervisor device.
3. Use the Setup utility to make sure that the embedded hypervisor device (USB key) is in the startup sequence. From the Setup utility, select Start Options.
4. See the documentation that comes with the optional embedded hypervisor flash device for setup and configuration information.
5. Check Lenovo Support web site for any service bulletins related to the embedded hypervisor and the server.
6. Make sure that all other server software is running without problems to ensure that the server is working properly.
3.The external USB device is not recognized
1. Make sure that the proper drivers are installed on the standard I/O book. See the documentation that comes with the USB device for information about device drivers.
2. Use the Setup utility to make sure that the device is configured correctly.
3. If the USB device is plugged into a hub or the console breakout cable, unplug the device and plug it directly into the USB port on the rear of the standard I/O book.
4. Run the DSA USB diagnostic tests.
4. At the end of POST the server does not detect a boot device
Before performing instructions for either issue below, first perform the following:
1. Check Light path and event logs for indication and possible cause for issue.
2. Follow problem resolution documentation (Problem Determination and Service Guide or Installation and Service Guide) actions to resolve the issue.
3. Check for related Lenovo Tech Tips.
4. If the issue has not been resolved, continue using the following instructions.
(A) No boot device available: The boot selection failed because a required device is not found
At the end of the POST process, the UEFI checks a pre-determined list of drives and devices. Normally, the server boots from the primary hard drive, or a boot device that is selected, where the operating system is stored. If the boot device is damaged, or if the server attempts to boot from a different device, the operating system does not start up and the server shows an error message.There are numerous possible causes and solutions for this issue
1. Check if the intended device is listed in the boot order. The boot order list can be found using the following method: In UEFI setup menu (F1), check the "Start Option"2. If the device does not exist: In UEFI, select "Boot Manager"→"Add Boot Option" to add the device to the "Start Option" list Restart the server and recheck the issue.
In problem persist enter UEFI, select "Boot Manager"→"Boot from File" →Select the GUID Partition Tables (GPT) → Select EFI. → Select Boot. → Select bootmgfw.EFI
3. Check to ensure the Option ROM for the associated device controller is enabled.
Note: Adapter Option ROM for PCIe slots can be found through
Enter UEFI setup menu (F1), System Settings, Devices and I/O ports, Enable/Disable Adapter Option ROM Support4. If the device is physically installed
Check any cables associated with the intended boot device for damage (i.e. pinched, bent pins, exposed wires, etc.)
Ensure associated device controller or slot is enabled in UEFI (F1) setup
Reinstall all associated hardware (i.e. controller, storage or media device(s), backplane, interposer, riser, embedded hypervisor)
When finished, restart the computer and recheck for issue.
5. If the issue continues
Capture Logs (reference: System x - Scenario/Log(s) Collection Matrix)
Escalate the issue to next support level
5. Operating System load failure: Fail to Boot an Operating System
Note: the following problem determination steps assuming an Operating System has been properly installed onto the device intended to boot.
1. Check to ensure the Option ROM for the associated device controller is enabled.
Note: Adapter Option ROM for PCIe slots can be found through
Enter UEFI setup menu (F1), System Settings, Devices and I/O ports, Enable/Disable Adapter Option ROM Support2. Ensure the device is in the boot order.
3. Ensure the Physical / Logical drive, from which the OS is booted, is set as a boot device.
4. If a partition was added or removed, this may cause the computer to attempt to boot from the incorrect device or partition.
5. If the issue continues
Capture Logs (reference: System x - Scenario/Log(s) Collection Matrix)
Escalate the issue to next support level