search for: initlabel

...he 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=1024 --grow Option...

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=sda3 --size=1 part r...

...s 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=VolGroup00 --size=416...

...ompt 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/en-US/Red_Hat...

...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 --noformat ... yo...

...efeats 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 something like this in a %...

...t the vty2 (emergency shell) and easily run fdisk /dev/sda and print the partition table. So the device is there, and accessable. 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...

Not having much luck googling.... I'm working on our ks.cgi, and in the case that we're using gpt, I know that kickstart can't, natively, use gpt yet. However, it is my impression that clearpart --initlabel --none --drives=$DISK would wipe the GPT label. (Plus, googling, I find that initlabel is deprecated). Am I wrong about initlabel? And is there any point in using clearpart, if we've got got to use parted to put a gpt label on the drive, and partition it? Should I just make that line go away?...

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=sdb --size=1 raid...

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 /boot/efi is the on...

...; + 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 > +clearpart --all --init...

...ace: 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 have tried the lat...

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

...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 --asprimary --ondisk sd...

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

I am trying using a kickstart file to install CentOS 6.2 into a new virtual machine (the MBR sector of the harddisk is all zero), however I found that the installer cannot go through the harddisk partition. It failed after I chose "Use All Space" at harddisk partition option. The error message is: http://anony.ws/i/bMcTJ.png "You have not defined a root partition (/), which is

...es/make-template.ml index 8667bfa3e..38c7a36e3 100755 --- a/builder/templates/make-template.ml +++ b/builder/templates/make-template.ml @@ -486,7 +486,7 @@ part / --fstype=%s --size=1024 --grow --asprimary | CentOS _ | RHEL _ | Fedora _ -> bpf "\ zerombr -clearpart --all --initlabel +clearpart --all --initlabel --disklabel=gpt autopart --type=plain "; | _ -> assert false (* cannot happen, see caller *) -- 2.13.2

...repo --name="CentOS" --baseurl=http://mirror.centos.org/altarch/7/os/ppc64le/ --cost=100 ## Uncomment for rolling builds repo --name="Updates" --baseurl=http://mirror.centos.org/altarch/7/updates/ppc64le/ --cost=100 # Disk setup zerombr clearpart --all --initlabel part / --fstype ext4 --size=3000 Looking for the option to select the installation destination through kickstart file. Thanks, Manjunath.

This is what I have for configuring software raid on sata drives in my kickstart config <snip kickstart.cfg> clearpart --initlabel --all part swap --size=2048 --ondisk=sdb part swap --size=2048 --ondisk=sda part raid.01 --size=101 --ondisk=sda part raid.02 --size=101 --ondisk=sdb part raid.04 --size=1 --grow --ondisk=sdb part raid.03 --size=1 --grow --ondisk=sda raid / --fstype ext3 --level=RAID1 raid.03 raid.04 raid /boot --f...

...r hardware as well as VM. But since we introduced Centos 5.7 OS and start building application with 5.7 anaconda the hardware partitions are duplicate of VM partitions *while creating hardware partition my code looks like.* cat > /tmp/partmap.ks <<EOPM *clearpart --all --initlabel --drives=sda *part swap --fstype swap --asprimary --size=16000 part /boot --fstype ext3 --size=400 --asprimary --fsoptions=noatime,defaults part pv.01 --size=1 --grow volgroup jmpvgnocf pv.01 logvol / --fstype ext3 --name=lvroot --vgname=jmpvgnocf --size=1 --grow --fsoptions=noatime,defaults logvol...