Red Hat Linux Image Deployment On A Server With Multiple Drives Causes An "Invalid Partition" Error
Article: 128
Applies to: All releases
When Red Hat Linux is installed without Logical Volume Manager (LVM)
on a server with multiple logical drives, the Linux partitions are
installed across all the drives so all available space is used.
When a disk image is captured, by default, only the partitions on the first disk are captured. Thus, when
this image is deployed, some of the partitions are missing, which can lead to an "Invalid Partition" error.
To resolve this issue, either:
| • |
Install Red Hat Linux with LVM. By default, the RDP-provided kickstart files use
autopart which installs LVM.
|
| • |
Force the partitions to be installed on the first drive during the scripted install as follows:
| 1. |
Copy and rename the kickstart file on the FTP server.
|
| 2. |
Modify the new kickstart file by adding --ondisk=XXX to the
end of each part command in your kickstart file.
For example:
part /boot --size 75 --ondisk=XXX
part swap --recommended --ondisk=XXX
part / --size 5120 --grow --ondisk=XXX
where XXX is the device label, such as sda or cciss/c0d0.
IMPORTANT: If an example in the kickstart file has a forward slash
(/) before the swap, remove it. This syntax no longer
works with the latest Red Hat updates.
For Red Hat Enterprise Linux 3, add --driveorder=XXX to the end of the
bootloader command in the kickstart file:
|
| 3. |
On the Deployment Server, copy and rename the job. Modify the new job to use
the new kickstart file created in step 1.
|
|
|
Printable version
