IBM 88554RU Installation Guide - Page 180

Partitions on IA-64 Linux, Device Boot

Page 180 highlights

scsi_mod mptscsih sd_mod] 229248 6 [usb-storage sg sr_mod ide-scsi Partitions on IA-64 Linux The EFI system implements a new way to work with partitions. That means that the IA-32 tools to manage partitions on Linux may not work properly. For example, if you run fdisk to see the content of a partition or disk, you do not see the real content of the disks. Modifying this partition can destroy the Linux installation. Example 4-5 shows the fdisk output for our test partitions. We had two arrays RAID level 1, each per server, configured on the system: One to run Linux, and the other to run Windows 2003 Server. Tip: In our case the third partition (sdc) is a USB 256 MB memory key. Example 4-5 fdisk output of two EFI partitions Disk /dev/sda: 18.1 GB, 18117296128 bytes 255 heads, 63 sectors/track, 2202 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start /dev/sda1 1 End Blocks Id System 2203 17692671+ ee EFI GPT Disk /dev/sdb: 18.1 GB, 18117296128 bytes 255 heads, 63 sectors/track, 2202 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start /dev/sdb1 1 End Blocks Id System 2203 17692671+ ee EFI GPT Disk /dev/sdc: 262 MB, 262144000 bytes 16 heads, 32 sectors/track, 1000 cylinders Units = cylinders of 512 * 512 = 262144 bytes Device Boot Start /dev/sdc1 * 1 End Blocks Id System 999 255728 6 FAT16 The two disks included more than one partition. In fact, there were at least three partitions on each: One for EFI, one for the operating system boot images, and another for the data. As you can see in the example, fdisk does not see any of these partitions, but only a big partition of type EFI GPT. 166 IBM xSeries 455 Planning and Installation Guide Eserver

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232

166
IBM
Eserver
xSeries 455 Planning and Installation Guide
scsi_mod
229248
6 [usb-storage sg sr_mod ide-scsi
mptscsih sd_mod]
Partitions on IA-64 Linux
The EFI system implements a new way to work with partitions. That means that
the IA-32 tools to manage partitions on Linux may not work properly. For
example, if you run
fdisk
to see the content of a partition or disk, you do not see
the real content of the disks. Modifying this partition can destroy the Linux
installation.
Example 4-5 shows the fdisk output for our test partitions. We had two arrays
RAID level 1, each per server, configured on the system: One to run Linux, and
the other to run Windows 2003 Server.
Example 4-5
fdisk output of two EFI partitions
Disk /dev/sda: 18.1 GB, 18117296128 bytes
255 heads, 63 sectors/track, 2202 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot
Start
End
Blocks
Id
System
/dev/sda1
1
2203
17692671+
ee
EFI GPT
Disk /dev/sdb: 18.1 GB, 18117296128 bytes
255 heads, 63 sectors/track, 2202 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot
Start
End
Blocks
Id
System
/dev/sdb1
1
2203
17692671+
ee
EFI GPT
Disk /dev/sdc: 262 MB, 262144000 bytes
16 heads, 32 sectors/track, 1000 cylinders
Units = cylinders of 512 * 512 = 262144 bytes
Device Boot
Start
End
Blocks
Id
System
/dev/sdc1
*
1
999
255728
6
FAT16
The two disks included more than one partition. In fact, there were at least three
partitions on each: One for EFI, one for the operating system boot images, and
another for the data. As you can see in the example, fdisk does not see any of
these partitions, but only a big partition of type EFI GPT.
Tip:
In our case the third partition (sdc) is a USB 256 MB memory key.