IBM 86884RX Installation Guide - Page 111

for Export from the OS Boot Options Maintenance Tool menu.

Get IBM 86884RX - Eserver xSeries 450 PDF manuals and user guides View all IBM 86884RX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 111 highlights

In this section we show you how to save the Boot Manager menu and how to recover it in case of an NVRAM failure. In 1.3.1, "GUID Partition Table disk" on page 7, we describe how GPT disks are identified by their global unique identifier (GUID). The entries in the Boot Manager menu use the GUID to identify which device to boot from. There are wo scenarios when the EFI Boot Manager menu will need to be restored: Disks rearrangement. If the disks are moved from one server to another, the NVRAM contents and the disk contents are out of sync, meaning that there will be no record in the new server's Boot Manager menu to point at the recently added disks. I/O board replacement. The I/O board contains the system's NVRAM, so when it is replaced, the operating system boot entry in the EFI Boot Manager menu will need to be manually restored. To export an EFI boot menu record, perform the following steps: 1. Invoke the EFI shell from the Boot Manager menu. Change to fsx: where x is the system partition (see 4.1.1, "The EFI shell" on page 70). 2. Change the directory to MSUTIL (cd msutil). 3. Run the NVRBOOT.EFI utility. See Example 4-1. 4. Enter X (for Export) from the OS Boot Options Maintenance Tool menu. 5. Enter the number of Windows boot record you want to export, or * to export all. 6. Type a file name to store the configuration in and press Enter. A confirmation message as shown in Example 4-1 will display. The file will be saved in the root of the EFI System Partition. Back up the file during your regular backup. 7. Press Q and exit the utility. Note: The utility can export/import all boot menu records, but can only display and modify the Windows boot record. Example 4-1 Exporting Windows boot record with NVRBOOT.EFI NVRBOOT: OS Boot Options Maintenance Tool [Version 5.2.3683] * 1. Windows .NET Server, Enterprise 2. EFI Shell [Built-in] 3. Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master) Chapter 4. Installation 97

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
Chapter 4. Installation
97
In this section we show you how to save the Boot Manager menu and how to
recover it in case of an NVRAM failure.
In 1.3.1, “GUID Partition Table disk” on page 7, we describe how GPT disks are
identified by their global unique identifier (GUID). The entries in the Boot
Manager menu use the GUID to identify which device to boot from.
There are wo scenarios when the EFI Boot Manager menu will need to be
restored:
±
Disks rearrangement. If the disks are moved from one server to another, the
NVRAM contents and the disk contents are out of sync, meaning that there
will be no record in the new server’s Boot Manager menu to point at the
recently added disks.
±
I/O board replacement. The I/O board contains the system’s NVRAM, so
when it is replaced, the operating system boot entry in the EFI Boot Manager
menu will need to be manually restored.
To export an EFI boot menu record, perform the following steps:
1.
Invoke the EFI shell from the Boot Manager menu. Change to fsx: where x is
the system partition (see 4.1.1, “The EFI shell” on page 70).
2.
Change the directory to MSUTIL (
cd msutil
).
3.
Run the NVRBOOT.EFI utility. See Example 4-1.
4. Enter
X
(for Export) from the OS Boot Options Maintenance Tool menu.
5.
Enter the number of Windows boot record you want to export, or * to export
all.
6.
Type a file name to store the configuration in and press Enter. A confirmation
message as shown in Example 4-1 will display.
The file will be saved in the root of the EFI System Partition. Back up the file
during your regular backup.
7.
Press Q and exit the utility.
Example 4-1
Exporting Windows boot record with NVRBOOT.EFI
NVRBOOT: OS Boot Options Maintenance Tool [Version 5.2.3683]
* 1. Windows .NET Server, Enterprise
2. EFI Shell [Built-in]
3. Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master)
Note:
The utility can export/import all boot menu records, but can only display
and modify the Windows boot record.