IBM 86884RX Installation Guide - Page 85

File operations in the EFI shell, ScsiPun0, Part1, HD Part1

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

Here are some tips for easier identification of devices in the list: Even with no storage devices, the server has at least two default mappings - the MemMap entries listed as fs0: and fs1: in Example 4-2 on page 70. These are read-only RAM disks created during POST so they will always be available. The first MemMap file system is the content of the 4 MB of NVRAM assigned to the EFI, and contains a number of drivers. The second MemMap file system is the content of the NVRAM assigned to the server diagnostics. The internal disks contain Scsi and HD strings. In Figure 4-2 on page 70: Scsi(Pun0,Lun0)/HD(Part1,Sig4879D0ED-FFF4-456D-A15C-DD6C856DF2F5) where Lun0 is disk's SCSI ID, Part1 stands for Partition1, and Sig is the disk's GUID (discussed in 1.3.1, "GUID Partition Table disk" on page 7). The disk partitions are numbered from 1 onwards: the first partition is Part1, the second Part2, and so on. EFI System Partition is easily identifiable in Figure 4-2 on page 70 if we realize that EFI is always the first partition on the disk (that is, it is identified by HD Part1 in the string). In this case it is fs3. In Figure 4-2 on page 70, the CD-ROM is represented as fs2. Note: Unless CD-ROM media is inserted, there is no FSx mapping created for the CD-ROM. The USB memory devices include the string USB. File operations in the EFI shell From the EFI shell you may access FAT/FAT32 file systems on existing disk partitions, run EFI executables, and manipulate with disk contents on various media. The EFI executables are text mode utilities similar to DOS or UNIX commands. In general, EFI commands are not case-sensitive. Tip: All the EFI executable files have an extension of .EFI. The executables may be run only from within EFI, not from within any operating system. Access to the file system on a device is done through the FSn: command (where n is the file system number shown in the device mapping table). This is similar in concept to changing drive letters in DOS. You can use the map command at any time to remind yourself of the available file systems. Chapter 4. Installation 71

  • 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
71
Here are some tips for easier identification of devices in the list:
±
Even with no storage devices, the server has at least two default mappings —
the MemMap entries listed as
fs0:
and
fs1:
in Example 4-2 on page 70.
These are read-only RAM disks created during POST so they will always be
available. The first MemMap file system is the content of the 4 MB of NVRAM
assigned to the EFI, and contains a number of drivers. The second MemMap
file system is the content of the NVRAM assigned to the server diagnostics.
±
The internal disks contain
Scsi
and
HD
strings. In Figure 4-2 on page 70:
Scsi(Pun0,
Lun0
)/HD(
Part1
,
Sig4879D0ED-FFF4-456D-A15C-DD6C856DF2F5
)
where
Lun0
is disk’s SCSI ID,
Part1
stands for Partition1, and
Sig
is the disk’s
GUID (discussed in 1.3.1, “GUID Partition Table disk” on page 7).
±
The disk partitions are numbered from 1 onwards: the first partition is Part1,
the second Part2, and so on.
±
EFI System Partition is easily identifiable in Figure 4-2 on page 70 if we
realize that EFI is always the first partition on the disk (that is, it is identified by
HD Part1
in the string). In this case it is fs3.
±
In Figure 4-2 on page 70, the CD-ROM is represented as fs2.
±
The USB memory devices include the string USB.
File operations in the EFI shell
From the EFI shell you may access FAT/FAT32 file systems on existing disk
partitions, run EFI executables, and manipulate with disk contents on various
media. The EFI executables are text mode utilities similar to DOS or UNIX
commands. In general, EFI commands are not case-sensitive.
Access to the file system on a device is done through the
FSn:
command (where
n
is the file system number shown in the device mapping table). This is similar in
concept to changing drive letters in DOS. You can use the
map
command at any
time to remind yourself of the available file systems.
Note:
Unless CD-ROM media is inserted, there is no FSx mapping created
for the CD-ROM.
Tip:
All the EFI executable files have an extension of .EFI. The executables
may be run only from within EFI, not from within any operating system.