search for: clearpart

I made a file partition-ks.cfg and put it in our machine 192.168.5.17 under /var/www/html. When I install a new machine I just do a linux ks=http://192.168.5.17/partition-ks.cfg I have a couple questions though: 1) I have the following in it: clearpart --all part /boot --fstype ext3 --size=100 part /var --fstype ext3 --size=10000 part / --fstype ext3 --size=10000 part swap --size=2048 part /home --fstype ext3 --size=100 --grow which is OK if I am installing over a previous installation. But for new machines it does not...

...ompletes. I have a kickstart install file that specifies the disk devices (sda, sdb) pulled and modified from another similiar system. My goal here is configuring software RAID. Whenever I try to use the file for software raid, she dies with an error: "Specified nonexistant disk sda in clearpart command" ... if I removed the --drives-sda,sdb from the clearpart, it will just fail on the part command for RAID. Now, I struggled with machine #1 for a long time, then realized that it is probably the onboard raid in the BIOS, which isn't a real RAID. Turned it off, and it appeared...

...rrectly. However the volgroup / logvolume was not made active, so my /dev/volgroup/logvol did not exist. Running `lvm lvchange -a -y pathname` from with in the shell after anaconda failed made the volgroup / logvol active. Which would allow the format command to complete. Option 1: zerombr yes clearpart --all --initlabel part /boot --fstype ext3 --size=100 part pv.os --size=10000 --grow --maxsize=10000 --asprimary volgroup os_volgroup01 pv.os logvol swap --fstype swap --name=os_swap_logvol --vgname=os_volgroup01 --recommended logvol / --fstype ext3 --name=os_root --vgname=os_volgroup01 --size=102...

I have 2 questions dealing with 2 different kickstart files. 1) my kickstart sections for RAID disk setup and kickstart reports it cannot find sda. Why is that. sda is there and works. clearpart --all --initlabel part raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda1 --size=20000 part swap --asprimary --bytes-per-inode=4096 --fstype="swap" --onpart=sda2 --size=4000 part raid.02 --bytes-per-inode=4096 --fstype="raid" --grow --onpart=sda...

...10 anaconda installer. Somehow I am ending up with my swap partition 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...

.../sdx devices. For hp servers, /dev/ccisss/whatever (sorry, no proliant with an array controller handy to check it). in order to just have one kickstart script to maintain I am trying to use the %pre section but getting a bit stuck. This is what I have: %pre if [ -b /dev/sda ] then zerombr clearpart --all bootloader --location=mbr --timeout=0 --driveorder=sda --append="crashkernel=auto rhgb quiet" part /boot --fstype=ext4 --size=500 part pv.008002 --grow --size=1 volgroup vg_host --pesize=4096 pv.008002 logvol / --fstype=ext4 --name=lv_root --vgname=vg_host --grow...

...algo=sha512 firewall --service=ssh #Disable graphical stuff skipx #text # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work # Uncommented by j zerombr clearpart --all autopart #ip=192.168.122.99 network --bootproto=static --ip=192.168.122.100 --netmask=255.255.255.0 --gateway=192.168.122.1 --nameserver=192.168.122.1 bootloader --location=mbr --timeout=5 --append="rhgb quiet" .... %end Some more details: This is what my "df" output is...

Hi List, I use a kickstart file to install my operating systems. In the kickstart file, I put the clearpart options to erase all my partition. But the install failed because the partition aren't erased. Does someone have the same issue ? Regards Kevin C

...s with no prompt on KVM hypervisors and succeeds? I have read the release notes[2]/tech notes[3] for 6.4 and noted lots of changes concerned with virtualization in general and hyperv hosts in particular, but I don't see anything that appears to be directly pertinent. I did try using the "clearpart --initlabel --all" approach (although that appears to be removed from 6.4), but I get the prompt with that as well. [1]: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html [2]: https://access.redhat.com/knowledge/docs/e...

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part pv.00 --fstype="lvmpv" --onpart=vda2 --noformat volgroup v --noformat logvol / --fstype=xfs --name=wurzel --vgname=v --useexisting logvol /home --fstype=ext4 --name=home --vgname=v...

...> > > # The following is the partition information you requested > > # Note that any partitions you deleted are not expressed > > # here so unless you clear all partitions first, this is > > # not guaranteed to work > > # Uncommented by j > > zerombr > > clearpart --all > > autopart > > #ip=192.168.122.99 > > network --bootproto=static --ip=192.168.122.100 --netmask=255.255.255.0 > --gateway=192.168.122.1 --nameserver=192.168.122.1 > > bootloader --location=mbr --timeout=5 --append="rhgb quiet" > > .... > > %e...

...ooks like safety defeats my unattended kickstart installation >> (like on Windows: "Do you really - really want to do this?"). > > It would have been helpful to see the disk-specific part of your > kickstart file, but here's a snippet that's worked for me: > > clearpart --all --initlabel > zerombr > bootloader --location=mbr > part ... > part ... > > I've also noticed that LVM meta information will stick around during a > re-installation. So if you're reusing the names of volumes groups, you > might encounter an error. I do somethin...

Hi, I have a test system that booted fine using "Legacy Bios? mode and using the following Kickstart snippet configured the disks correctly:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow --ondisk=sda --size=1 part raid.03 --fstype="raid" --ondisk=sdb --size=500 part raid.04 --fstype="raid" --grow --ondisk=...

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda --fstype xfs --size=1 --asprimary --grow the line with /...

...() > + ); > + bpf "\n"; > + > + bpf "bootloader --location=mbr --append=\"%s\"\n" > + (kernel_cmdline_of_os os arch); > + bpf "\n"; > + > + (match os with > + | CentOS _ -> > + bpf "\ > +zerombr > +clearpart --all --initlabel > +part /boot --fstype=ext4 --size=512 --asprimary > +part swap --size=1024 --asprimary > +part / --fstype=ext4 --size=1024 --grow --asprimary > +"; > + | RHEL ((3|4), _) -> > + bpf "\ > +zerombr > +clea...

...guration than it is a Xen issue. I use a modified kickstart file from an earlier manual installation with a very basic filesystem setup. It fails with "SystemError: vgcreate failed for VolGroup00". The Xen VM file is allowed to grow up to 2GB. The kickstart commands for partioning are: clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 pv.2 --pesize=32768 pv.2 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow logvol swap --fstype swap --name=LogVol01 --vgname=Vol...

...FO anaconda: fs space: 0 B needed: 2861.02 MiB If I reboot, select legacy BIOS it works The only differences in the Kickstart files are as follows: legacy KS bootloader --location=mbr --boot-drive=sda --driveorder=sda,sdb --append="console=tty0 console=ttyS1,9600 console=ttyS2,115200" clearpart --all --initlabel --- UEFi Ks below: bootloader --location=partition --boot-drive=sda --driveorder=sda,sdb --append="console=tty0 console=ttyS1,9600 console=ttyS2,115200" clearpart --all --initlabel --drives=sda,sdb part /boot/efi --fstype="efi" --size=200 --ondisk=sda And I...

On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart

...how the kickstart process partitions the disks, though. As you may have noticed above, md0 is made up of sdb1 and sda2. Could anybody help me understand how to make the partitions on the two drives identical still using kickstart? Here's the relevant part from the kickstart file: zerombr yes clearpart --all --initlabel bootloader --location=mbr part /boot --fstype ext3 --size 250 --asprimary --ondisk sda part swap --size 2048 --asprimary --ondisk sda part raid.01 --size 40000 --asprimary --ondisk sda part raid.03 --size 1 --grow --asprimary --ondisk sda part /boot2 --fstype ext3 --size 250 --asp...

Dear Experts, Could somebody point to kicstart HOWTO specific for CentOS 7? On CentOS 7 I somehow am always given human intervention questions about drive which defeats unattended ks install. <rant ??> I'm doing kickstart installations for quite some time, normally I was just installing system when new release comes, and am basing kickstart file on anaconda-ks.cfg - with some