Here is an odd one.
RHEL4U4
I have a PXE based kickstart that creates a RAID + LVM setup on two
internal SATA drives using the
below kickstart entry. This works fine on the first install. However,
I am working on a setup where I
can rebuild hosts often if we need to for whatever reason. If I re-kick
the hosts again, the process works great
up until the reboot. Then, *sometimes* the machine will stop and the
console will display "GRUB" and hang forever.
I can try the kickstart again, but the results are the same. However,
if I manually reinstall and not use md RAID, then
a new kickstart install with this setup works fine again. So, only
thing I can think of is that something is not getting cleared
in the kickstart process on the drives that is confusing GRUB as it
starts to boot. I tried adding all the disk clearing options to the
kickstart file but it has not made a difference. Any ideas?
kickstart partition section:
----------------------------
bootloader --location=mbr
clearpart --all --drives=sda,sdb --initlabel
zerombr yes
part raid.13 --size=100 --ondisk=sda
part raid.14 --size=100 --ondisk=sdb
part raid.17 --size=100 --grow --ondisk=sdb
part raid.16 --size=100 --grow --ondisk=sda
raid /boot --fstype ext3 --level=RAID1 raid.13 raid.14
raid pv.18 --fstype "physical volume (LVM)" --level=RAID1 raid.16 raid.17
volgroup VolGroup00 --pesize=32768 pv.18
logvol swap --fstype swap --name=LogVol03 --vgname=VolGroup00 --size=2016
logvol /usr --fstype ext3 --name=LogVol04 --vgname=VolGroup00 --size=10016
logvol /home --fstype ext3 --name=LogVol01 --vgname=VolGroup00 --size=10016
logvol /var --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=10016
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=5024
TIA,
Lance
