Microsoft Windows Server 2008 R2 fails to boot UEFI systems with RAW disks

2008 R2버전을 설치하고
스토리지를 연결시에 부팅이 안되는 현상을 패치 하는것입니다

기본적으로는 레거시 온리를 추가해서 제일위로 올리면 잘되는데
위 환경에서는 잘안됩니다
그럴때 적용하세요

Source

RETAIN tip: H197004

Symptom

Windows 2008 R2 Operating System (OS) 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 (SAS) HBA attached external storage, but can also occur on any other manufacturer's HBA.

The issue has been observed in the following four (4) scenarios:

1. The OS is to be applied on a local storage subsystem while the system is connected and mapped to raw disks on external storage through multiple and active paths.
2. The OS is to be applied on external storage while the system is connected and mapped to raw disks on external storage through multiple and active paths.
3. The OS is up and running either applied on local storage subsystem or on external storage subsystem and a raw disk is added.
4. An UEFI enabled system has a storage device attached that has more than four (4) partitions and/or boot loader responds with 'Boot Failed', if a key is pressed to boot from a Windows Server 2008 R2 installation DVD.

The system fails to start the OS when any initiated OS reboots for reason of maintenance, during an HBA I/O device driver installation/update, or automated reboot during the OS installation process.

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:

1. 979374 - "The system becomes unbootable after you add raw disks ..." located at the following URL:
2. • http://support.microsoft.com/kb/979374
3. 975535 - "You cannot install Windows Server 2008 R2 on a computer that uses EFI" located at the following URL:
4. • http://support.microsoft.com/kb/975535
5. 982929 - 'Boot failed' error when you start a UEFI-enabled system from .. (Package1) located at the following URL:
6. • http://support.microsoft.com/kb/982929
7. 2223832 - 'Boot failed' error when you start a UEFI-enabled system from .. (Package2) located at the following URL:
   • http://support.microsoft.com/kb/2223832

Method 1

Install hotfix 979374 and 982929 to an existing Windows Server 2008 R2 installation. For this method, you do not have to also install hotfix 975535 and 2223832.

1. Disconnect any raw disks from the computer to start the OS.
2. Apply this package to resolve the issue.
3. Reconnect the raw disks to the computer.

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.

Workaround

To prevent the issue for the observed scenarios, apply one of the methods below.

Method 1

You can install hotfix 979374 and 982929 to an existing 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:

• http://support.microsoft.com/kb/2011542/

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.

Apply the OS on the local or external storage subsystem by using the unpatched installation media.

While it is required for installing the OS 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 OS for every HBA in device manager.

Install failover drivers/Device Specific Modules and restart again before opening additional paths.

If the OS 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 OS setup has been finished being applied on the local storage subsystem.

Install Microsoft hotfix 979374 and enable/map additional paths to raw disk subsequently.

Additional information

This issue occurs because the EFI loader (Winload.efi) incorrectly identifies raw disks as GUID Partition Tables (GPT) disks. Then, Windows tries to enumerate GPT partitions on the raw disks. Therefore, the computer will no longer start.

A second issue is issued 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.


그래도 안된다면 다음껄 진행해보세요
UEFI-aware operating system does not boot after load defaults or deployment

Source

RETAIN tip: H194888

Symptom

Loading the defaults in Unified Extensible Firmware Interface (UEFI) deletes the Boot Order entries for any UEFI aware operating system.

These entries are required to boot the operating system correctly.

Deployment images may also use this information to automatically boot an Extensible Firmware Interface (EFI) operating system for the first time.

Affected configurations

The system may be any of the following IBM servers:

• BladeCenter HS22, type 7870, any model
• BladeCenter HS22V, type 1949, any model
• BladeCenter HS22V, type 7871, any model
• BladeCenter HX5, type 7872, 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 4252, any model
• System x3250 M3, type 4261, any model
• System x3400 M2, type 7836, any model
• System x3400 M2, type 7837, any model
• System x3500 M2, type 7839, any model
• System x3550 M2, type 7946, 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
• iDataPlex dx360 M2 Server, type 6380, any model
• iDataPlex dx360 M2 Server, type 7321, any model
• iDataPlex dx360 M2 Server, type 7323, any model
• iDataPlex dx360 M3 Server, type 6391, any model

This tip is not software specific.

This tip is not option specific.

Workaround

The workaround is dependent upon the particular UEFI operating system. Refer to the UEFI operating system information for the actual file name and path used to boot that particular operating system.

For example, for Microsoft Windows Server 2008, the steps are as follows:

1. Power on the system, and, when prompted, press F1 to enter setup.
2. Select Boot Manager.
3. Select Boot from File.
4. Select the GUID Partition Tables (GPT) System Partition where you installed Microsoft Windows Server 2008.
5. Select EFI.
6. Select Microsoft.
7. Select Boot.
8. Select bootmgfw.EFI.

Additional information

This is working as designed.

Operating system vendors are aware of the symptom. When you boot your UEFI operating system using "use the Boot from File method," the operating system may recreate the UEFI Boot Order Entry if it has been deleted.

By copying the UEFI operating system boot manager to the GPT System Partition directory \EFI\BOOT with the name BOOTX64.EFI, this will allow the EFI operating system to boot automatically.

The boot manager for Microsoft Windows Server 2008 is as follows:

\EFI\Microsoft\Boot\Bootmgfw.EFI

Copying the UEFI operating system boot manager when building the master disk image that will be cloned for deployment will allow the EFI operating system to boot the first time the system is started.