I was thinking about the rescue vector this morning as well. Rescue booting with RHEL 5.4 does work and everything mounts up properly under /mnt/sysimage, you do have to deal with anaconda stopping on the disk that isn't partitioned and asking for it to be initialized twice during your rescue session. There is always a *big* concern that an admin would select yes and then blow out the LVM PV. It doesn't quite feel like a whole disk method is an accepted practice yet or either the tools have not caught up to allow this practice yet. Maybe when we can finally shove /boot into an LV the toolsets will be a little more friendly to this configuration. Chad ----- Original Message ---- From: Jodok Ole Muellers <muellejo@xxxxxxxxxxxxxx> To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx> Cc: darn570-linux@xxxxxxxxx Sent: Wed, January 13, 2010 2:21:22 AM Subject: Re: Whole disk LVM via kickstart Hi Chad, > /dev/sdb = LVM2 pv, no partitions (LVs /, /home, /usr/local, /opt, swap, /tmp, & /var) I recently learned that it is not a good idea not to have a partition, because you then can't define a partition type 8e and therefore e.g. booting a rescue system could get trouble to automatically identify sdb as LVM PV. This is what I use bootloader --location=mbr --driveorder=sdb --append="console=ttyS1,115200n8 console=tty1 vga=791" clearpart --all --drives=sdb part /boot --fstype ext3 --size=100 --ondisk=sdb part pv.2 --size=0 --grow --ondisk=sdb volgroup rootvg --pesize=32768 pv.2 logvol swap --fstype swap --name=swaplv --vgname=rootvg --size=8192 logvol / --fstype ext3 --name=rootlv --vgname=rootvg --size=20480 cheers _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
