IBM 86884RX Installation Guide - Page 84

The EFI shell, EFI Shell [Built-in]

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 84 highlights

When you select one of the network controllers (marked PXE boot), you initiate the PXE remote boot process. When no PXE boot server is discovered on the network during this process, a failure message appears as well. Beyond the options mentioned, in this section we cover the following: The EFI shell Flash update Configuration and Setup utility Diagnostic utility Boot maintenance menu 4.1.1 The EFI shell The EFI shell allows the loading of EFI applications (including booting installed operating systems) from any EFI-defined file system. The EFI environment replaces DOS to perform maintenance operations, such as upgrading firmware or running system diagnostics. To start the EFI shell, select EFI Shell [Built-in] from the Boot Manager menu. As the shell starts, a device mapping table is displayed, as shown in Figure 4-2. Loading.: EFI Shell [Built-in] EFI Boot Manager ver 1.10 [14.60] Device Mapping Table fs0 : MemMap(0:FF000000-FFFFFFFF) fs1 : MemMap(0:FF800200-FFBFFFFF) fs2 : Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master)/CDROM(Entry0) fs3 : Acpi(PNP0A03,1)/Pci(3|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig4879D0ED-FF blk0 : MemMap(0:FF000000-FFFFFFFF) blk1 : MemMap(0:FF800200-FFBFFFFF) blk2 : Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master) blk3 : Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master)/CDROM(Entry0) blk4 : Acpi(PNP0A03,1)/Pci(3|0)/Scsi(Pun0,Lun0) blk5 : Acpi(PNP0A03,1)/Pci(3|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig4879D0ED-FF Shell> Figure 4-2 Entering EFI shell This mapping table lists both block devices (blk) and file systems (fs). All fixed disks, CD-ROM drives, and USB storage devices will appear as block devices. If the server contains additional controllers and disks, they will appear as additional block devices. The EFI automatically maps known file systems on the block devices to their FSx mappings (FSx is referred to as the file system identifier). 70 IBM ^ xSeries 450 Planning and Installation Guide

  • 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
70
IBM
^
xSeries 450 Planning and Installation Guide
When you select one of the network controllers (marked PXE boot), you initiate
the PXE remote boot process. When no PXE boot server is discovered on the
network during this process, a failure message appears as well.
Beyond the options mentioned, in this section we cover the following:
±
The EFI shell
±
Flash update
±
Configuration and Setup utility
±
Diagnostic utility
±
Boot maintenance menu
4.1.1
The EFI shell
The EFI shell allows the loading of EFI applications (including booting installed
operating systems) from any EFI-defined file system. The EFI environment
replaces DOS to perform maintenance operations, such as upgrading firmware
or running system diagnostics.
To start the EFI shell,
select
EFI Shell [Built-in]
from the Boot Manager menu. As
the shell starts, a device mapping table is displayed, as shown in Figure 4-2.
Figure 4-2
Entering EFI shell
This mapping table lists both block devices (blk) and file systems (fs). All fixed
disks, CD-ROM drives, and USB storage devices will appear as block devices. If
the server contains additional controllers and disks, they will appear as additional
block devices. The EFI automatically maps known file systems on the block
devices to their FSx mappings (FSx is referred to as the
file system identifier
).
Loading.: EFI Shell [Built-in]
EFI Boot Manager ver 1.10 [14.60]
Device Mapping Table
fs0
: MemMap(0:FF000000-FFFFFFFF)
fs1
: MemMap(0:FF800200-FFBFFFFF)
fs2
: Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master)/CDROM(Entry0)
fs3
: Acpi(PNP0A03,1)/Pci(3|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig4879D0ED-FF
blk0 : MemMap(0:FF000000-FFFFFFFF)
blk1 : MemMap(0:FF800200-FFBFFFFF)
blk2 : Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master)
blk3 : Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master)/CDROM(Entry0)
blk4 : Acpi(PNP0A03,1)/Pci(3|0)/Scsi(Pun0,Lun0)
blk5 : Acpi(PNP0A03,1)/Pci(3|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig4879D0ED-FF
Shell>