Local operating system boot fails when external storage is attached - IBM BladeCenter and System x
Source
RETAIN tip: H195948
Symptom
Operating systems that are not Unified Extensible Firmware Interface (UEFI) aware can fail at the point of bootstrapping the operating system from local hard drives.
The issue occurs when a Host Bus Adapter (HBA) is installed in the server and attached to external storage. The issue has only been seen with the QLogic and Emulex HBAs.
One of the symptoms of this issue is seen at the point where the OS normally starts to load, but instead, the end user will see the "feed me" screen, indicating an unsuccessful bootstrap of the operating system.
Another symptom is that the duration of the "Configuring system ..." stage of initialization may be excessively long (up to 20 minutes has been observed).
Affected configuration
The system may be any of the following IBM servers:
- BladeCenter HS22, type 1936, any model
- BladeCenter HS22, type 7870, any model
- BladeCenter HS22V, type 1949, any model
- BladeCenter HS22V, type 7871, any model
- System x3550 M2, type 4198, any model
- System x3550 M2, type 7946, any model
- System x3650 M2, type 4199, any model
- System x3650 M2, type 7947, any model
- System x3690 X5, Type 7148, any model
- System x3690 X5, Type 7149, any model
- System x3850 X5, Type 7145, any model
- System x3850 X5, Type 7146, any model
- System x3950 X5, Type 7145, any model
This tip is not software specific.
This tip is not option specific.
Workaround
The following steps detail what to do when either a UEFI or non-UEFI aware operating system is used.
UEFI aware operating system: UEFI 사용시
- Follow the steps detailed in RETAIN tip H194888 to specify the boot file.
- If using Microsft Windows 2008 R2 and the steps detailed in the above tip do not correct the issue, refer to Microsoft Knowledge Base article 975535 - "The system becomes unbootable after you add raw disks to a Windows Server 2008 R2-based computer that has EFI enabled," located at the following URL: http://support.microsoft.com/kb/975535
H194888 내용
Non-UEFI aware operating system: UEFI 미사용시
The failure to bootstrap the operating system can be circumvented as follows:
From within the F1 Setup menus for configuring UEFI, ensure that the HBA Legacy Option Read Only Memory (ROM) and UEFI Option ROM are disabled and add the "Legacy Only" Start Option as per the following procedure:
- Power on or restart the system and press F1 when prompted to enter Setup.
- Select System Settings and press Enter.
- Select Devices and I/O Ports and press Enter.
- Select Enable/Disable Legacy Option ROMs and press Enter.
- Under Enable/Disable Legacy Option ROMs select the slot number in which the HBA is installed and press Enter.
- Select Disabled and press Enter.
- Under Enable/Disable UEFI Option ROMs select the slot number in which the HBA is installed and press Enter.
- Select Disabled and press Enter.
- Press Esc 3 times to return to the System Configuration main menu, select Save Settings and press Enter.
- Select Boot Manager and press Enter.
- Select Add Boot Option and press Enter.
- Select Legacy Only and press Enter.
- Press Esc to return to Boot Manager.
- Select Change Boot Order and press Enter.
- Select the existing Boot Order and press Enter.
- Select Legacy Only and press the + key to promote it to a position above the local device which contains the operating system . Typically, this would be above Hard Disk 0. Press Enter.
- Select Commit Changes and press Enter.
- Press Esc to return to Boot Manager.
- Select Reset System and press Enter.
Additional information
For non-UEFI aware operating systems, this behavior is by design.
The symptoms described occur because UEFI firmware sees devices in one order and legacy firmware sees them in a different order due to basic differences in UEFI and legacy firmware with respect to devices. There is a need to prevent the externally attached storage devices from being mapped in both UEFI and "Legacy Only" modes. The Workaround resolves the issue by forcing device mapping to be performed in legacy mode only and ensures that the Legacy ROM of the HBA connected to the external storage does not execute.
그래도 안되거나 2008 R2사용시
Microsoft Windows Server 2008 R2 fails to boot UEFI systems with RAW disks - IBM BladeCenter and System x
RETAIN tip: H197004
Symptom
Microsoft Windows 2008 R2 operating system does not boot properly on Unified Extensible Firmware Interface (UEFI) enabled systems if raw disk storage is configured.
The issue can be observed if Logical Unit Number (LUN) mapping has been enabled to a raw disk and multiple paths are active.
The issue has been seen with QLogic and Emulex Fibre Host Bus Adapters (HBAs) and LSI Serial Attached Storage (Serial Attached SCSI (SAS)) Host Bus Adapter (HBA) connected external storage, but can also occur on any other manufacturer's HBA.
The issue has been observed in the following four (4) scenarios:
- The operating system is installed on a local storage subsystem while the system is connected and mapped to raw disks on external storage through multiple and active paths.
- The operating system is installed on external storage while the system is connected and mapped to raw disks on external storage through multiple and active paths.
- The operating system is already installed on a local storage subsystem or on external storage subsystem and a raw disk is added.
- The server which had UEFI enabled and has a storage device connected that has more than four (4) partitions and/or boot loader responds with 'Boot Failed' if a key is pressed to boot from a Microsoft Windows Server 2008 R2 installation DVD.
The system fails to start the operating system when any initiated operating system reboots for reason of maintenance, during an HBA I/O device driver installation/update, or automated reboot during the operating system installation process. A status code of 0xc0000185 will be shown.
The Windows boot loader is seen and selecting any of the boot options: "Start Windows Normally" and "Launch Startup Repair (Recommended)" returns to bootstrap.
Affected configurations
The system may be any of the following IBM servers:
- BladeCenter HS22, type 1936, any model
- BladeCenter HS22, type 7870, any model
- BladeCenter HS22V, type 1949, any model
- BladeCenter HS22V, type 7871, any model
- System x3200 M3, type 7327, any model
- System x3200 M3, type 7328, any model
- System x3250 M3, type 4251, any model
- System x3250 M3, type 4261, any model
- System x3400 M2, type 7836, any model
- System x3400 M2, type 7837, any model
- System x3400 M3, type 7378, any model
- System x3400 M3, type 7379, any model
- System x3550 M2, type 4198, any model
- System x3550 M3, type 4254, any model
- System x3550 M3, type 7944, any model
- System x3650 M2, type 4199, any model
- System x3650 M2, type 7947, any model
- System x3650 M3, type 4255, any model
- System x3650 M3, type 7945, any model
- System x3690 X5, type 7148, any model
- System x3690 X5, type 7149, any model
- System x3850 X5, type 7145, any model
- System x3850 X5, type 7146, any model
- System x3950 X5, type 7145, any model
The system is configured with at least one of the following:
- Microsoft Windows Server 2008 R2 Datacenter, any service pack
- Microsoft Windows Server 2008 R2 Enterprise, any service pack
- Microsoft Windows Server 2008 R2 Foundation, any service pack
- Microsoft Windows Server 2008 R2 Standard, any service pack
The system is configured with one or more of the following IBM Options:
- Unified Extensible Firmware Interface (UEFI)
The system has the symptom described above.
Note: This does not imply that the network operating system will work under all combinations of hardware and software.
Please see the compatibility page for more information: http://www.ibm.com/servers/eserver/serverproven/compat/us/
Solution
Microsoft published four (4) hotfixes to solve the issue.
Refer to the following Microsoft Knowledge Base articles:
979374 - "The system becomes unbootable after you add raw disks ..." located at the following URL:
975535 - "You cannot install Windows Server 2008 R2 on a computer that uses Extensible Firmware Interface (EFI)" located at the following URL:
982929 - 'Boot failed' error when you start a UEFI-enabled system from .. (Package1) located at the following URL:
2223832 - 'Boot failed' error when you start a UEFI-enabled system from .. (Package2) located at the following URL:
Option 1:
Install hotfix 979374 and 982929 to an existing Microsoft Windows Server 2008 R2 installation. For this option, you do not have to also install hotfix 975535 and 2223832.
- Disconnect any raw disks from the computer to start the operating system.
- Apply this package to resolve the issue.
- Reconnect the raw disks to the computer.
Option 2:
You can integrate hotfix 979374 and 982929 into the installation media. For this option, this hotfix must be applied together with hotfix 975535 and 2223832.
Option 3:
Use Microsoft Windows 2008 R2 SP1. The media already includes the 4 hotfixes mentioned.
Workaround
To prevent the issue for the observed scenarios, apply one of the following (4) methods below:
Method 1:
You can install hotfix 979374 and 982929 to an existing Microsoft Windows Server 2008 R2 installation before raw disks will be added. For this method, you do not have to also install hotfix 975535 and 2223832.
Method 2:
You can integrate hotfix 979374 and 982929 into the installation media. For this method, this hotfix must be applied together with hotfix 975535 and 2223832.
Refer to Microsoft Knowledge Base article 2011542 - "How to manually apply hotfixes to the pre-install environment on the Windows installation disc" available at the following URL:
Method 3:
Prepare the system to have one path active only to external storage while all others are disabled, unmapped or disconnected to access a raw disk.
Install the operating system on the local or external storage subsystem by using the unpatched installation media.
While it is required for installing the operating system onto the external storage subsystem to apply the HBA I/O device driver in the setup start-up already, the HBA I/O device driver can be installed first after setup has been completed for a local installed operating system for every HBA in device manager.
Install failover drivers/Device Specific Modules and restart again before opening additional paths.
If the operating system has been completed, then Microsoft hotfix 979374 and 929832 should be installed to resolve the issue.
If the setup start-up phase has already started, then the HBA I/O device driver for external storage can be installed after the operating system setup has been finished being applied on the local storage subsystem.
Install Microsoft hotfix 979374 and enable/map additional paths to raw disk subsequently.
Method 4:
Use Microsoft Windows 2008 R2 SP1. The media already includes the 4 hotfixes mentioned.
Additional information
This issue occurs because the EFI loader (Winload.EFI) incorrectly identifies raw disks as GUID Partition Tables (GPT) disks. Windows then tries to enumerate GPT partitions on the raw disks and the computer will no longer start.
The second issue is subject by the boot manager that compares two UEFI device signatures incorrectly, that is in the Extended Boot Record (EBR) and the device signature that is in the Master Boot Record (MBR).
This tip is an extension to RETAIN tip H194888 (MIGR-5079636), which describes how to verify that the required UEFI OS start-up entry is enabled in the UEFI setup.
'My Retain Tip > X Series' 카테고리의 다른 글
| IBM and XenServer 설치 테스트 호환성 확인 (2) | 2011.04.18 |
|---|---|
| X3850 X5 / X3950 X5 PCI Reboot 발생시 해결법 (2) | 2011.04.17 |
| GPT 파티션을 지원하려면 필요한 것들 (0) | 2011.04.14 |
| IBM RAID DRIVER M1015 M5015 MR10i 시리즈 드라이버 입니다. 윈도우용 (0) | 2011.04.12 |
| Hyper-V An error occurred My VM failed (0) | 2011.04.11 |