In Windows Server 2003, you may not be able to start a computer from a GPT disk when the computer has an Itanium processor (902195)


The information in this article applies to:

  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-based Systems

SYMPTOMS

Consider the following scenario:
  • A computer that has an Itanium processor has both the original release version of Microsoft Windows Server 2003 and Windows Server 2003 with Service Pack 1 (SP1) installed.
  • These operating systems are configured in Non-Volatile Random Access Memory (NVRAM) to start from the same boot loader file (Ia64ldr.efi) on an Extensible Firmware Interface (EFI) partition.
In this scenario, you may not be able to start the computer from a GUID partition table (GPT) disk. If the Ia64ldr.efi file is the original release version, the computer cannot start by using Windows Server 2003 with SP1. If the Ia64ldr.efi file is the SP1 version, the computer cannot start by using the original release version of Windows Server 2003.

CAUSE

This problem occurs because the boot loader file in Windows Server 2003 with Service Pack 1 is not compatible with the original release version of Windows Server 2003. Additionally, the boot loader file in the original release version of Windows Server 2003 is not compatible with Windows Server 2003 with Service Pack 1.

RESOLUTION

To resolve this problem, configure the boot entries in NVRAM to start each installation from a separate boot loader file on the EFI partition. Then, install Windows Server 2003 Service Pack 1 on one of the installations.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Steps to reproduce the problem

  1. Install Windows Server 2003 without service packs on each of two GPT disks or on each of two Logical Disk Manager data partitions on a single GPT disk.
  2. Install Windows Server 2003 Service Pack 1 on one of these installations.
  3. On either installation, run the following command at a command prompt:

    bootcfg /mirror /add {Partition GUID} /D "Test incompatible boot loader"

    Note In this command, {Partition GUID} is a placeholder for the GUID of the Logical Disk Manager data partition that contains the other installation. This command copies the boot loader path that is used to start the current operating system for the new boot entry to create a new boot entry in NVRAM.
  4. Restart the server by using the "Test incompatible boot loader" startup entry.
The computer cannot start when you use this entry.

Note The command in step 3 is frequently used when the primary installation on an LDM data partition has been recovered. However, a new boot entry must be created by using a backup of an installation that can still be started.
Modification Type:MajorLast Reviewed:6/28/2005
Keywords:kbtshoot kbprb KB902195 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.