search for: ondrive

...tition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1) My kickstart storage config looks like this: bootloader --location=mbr --driveorder=sda,sdb zerombr ignoredisk --only-use=sda,sdb clearpart --all --drives=sda,sdb part raid.boot0 --size 1000 --ondrive=sda part raid.swap0 --size 8192 --ondrive=sda part raid.root0 --size 8000 --grow --ondrive=sda part raid.boot1 --size 1000 --ondrive=sdb part raid.swap1 --size 8192 --ondrive=sdb part raid.root1 --size 8000 --grow --ondrive=sdb raid /boot --fstype ext4 --device md0 --level=RAID1 raid.boot1 raid.boo...

...disk is 10.5GB. However, looking through the logs, it tries to run 'dmsetup info /dev/sda' which fails! Device /dev/sda not found Command failed The disk setup part looks like this: zerombr clearpart --drives=sda --initlabel part /boot --fstype ext3 --size 200 --ondrive=sda part swap --recommended --ondrive=sda part / --fstype ext3 --size 40000 --ondrive=sda part /scratch --fstype ext3 --size 1 --grow --ondrive=sda Running without a KS, the GUI works (but I still got the problem with dmsetup in the logs). Any ideas? -- ... but you know as soon...

...ble. I've tried every incarnation of clearpart commands. My current kickstart info: # RAID kickstart # clearpart --linux --drives=sda,sdb # clearpart --all --linux --initlabel clearpart --drives=sda,sdb --all --initlabel # clearpart --all --initlabel --drives=sda,sdb part raid.9 --size=100 --ondrive=sda part raid.10 --size=100 --ondrive=sdb part raid.13 --size=2000 --ondrive=sdb part raid.12 --size=2000 --ondrive=sda part raid.16 --size=100 --grow --ondrive=sdb part raid.15 --size=100 --grow --ondrive=sda raid /boot --fstype ext3 --level=RAID1 --device=md0 raid.9 raid.10 raid swap --fstype swa...

...lume group" Only workaround i can find is to add --maxsize=XXX where XXX is at least 640MB less than available. (10 extents or 320Mb per created logical volume) Following snippet is failing with "DEBUG blivet: failed to set size: 640MB short" part raid.01 --size 512 --asprimary --ondrive=sda part raid.02 --size 1 --asprimary --ondrive=sda --grow part raid.11 --size 512 --asprimary --ondrive=sdb part raid.12 --size 1 --asprimary --ondrive=sdb --grow raid /boot --fstype="xfs" --device="md0" --level=RAID1 raid.01 raid.11 raid pv.01 --fstype="lvm...

Has anyone managed to create an encrypted disk partition with CentOS 8 kickstart? 1 reqpart --add-boot 2 part /boot --fstype ext3 --size=1024 --ondrive=sda 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla" 4 volgroup vol0 pv.100000 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4 ... No matter what I specify in line 3, the installer bombs out. The only way to successful kickstart is to not encr...

On Sun, 21 Aug 2016 at 12:51 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/19/2016 11:35 PM, Phil Manuel wrote: > > The install fails under UEFi due to the fact the partitions are not > cleared, and it doesn?t have any space to continue. Is there an extra step > I need to do to remove the original partitions before the new layout will > work ? > > >

...I missing ? I very vaguely remember struggling with this as well, but I can't find my notes from that work at the moment. My kickstart files for non-RAID UEFI boots use something like this: bootloader --location=mbr --append="net.ifnames=0 biosdevname=0" part /boot/efi --ondrive=sda --fstype=efi --label EFI part /boot --fstype=ext4 --ondrive=sda ... My memory is really fuzzy, but if I remember right, this didn't work when I didn't specify "--label EFI" or some other really silly thing. I think I resolved the problem by doing a manual install...

...ly remember struggling with this as well, but I can't find > my notes from that work at the moment. > > My kickstart files for non-RAID UEFI boots use something like this: > > bootloader --location=mbr --append="net.ifnames=0 biosdevname=0" > part /boot/efi --ondrive=sda --fstype=efi --label EFI > part /boot --fstype=ext4 --ondrive=sda > ... > > > My memory is really fuzzy, but if I remember right, this didn't work > when I didn't specify "--label EFI" or some other really silly thing. I > think I resolved the pro...