search for: zerombr

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone have any thoughts on why anaconda might be prompting me to reinitialize the disk during the kickstart of a Centos6.4 install on hyperV when a) the kickstart file contains "zerombr" as referred to in the installation guide[1] b) installation proceeds 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 a...

...is setup correctly. 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_volgrou...

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

...ended 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 %pre section:...

If you use a kickstart file to build unattended servers (eg virt-install) then new disks or virtual volumes will cause problems unless you have "zerombr true" in the kickstart file eg zerombr yes clearpart --all --initlabel part /boot --fstype=ext4 --asprimary --size=100 part swap --asprimary --size=512 part / --fstype=ext4 --asprimary --grow --size=1 (CentOS 6.2 didn't need zerombr). Also FWIW, lines such as repo --name=&quo...

...+ | _ -> () > + ); > + 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 "\ > +ze...

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

...w --passalgo=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"...

...ant bits. I'm using the centOS 6.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 --s...

...roblem with 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 --...

...live. So there is probably a package it needs that I don't know about. Has anyone gotten this to work at all? Since it is a disk/image issue this is the part of the ks relevant to disks: # Disk partitioning information reqpart part / --fstype="ext4" --size=4000 part swap --size=1000 zerombr clearpart --all bootloader --location=mbr Below is my packages part of my kickstart: %packages # Packages needed by anaconda, but not directly required. # Includes all of the grub2 and shim packages needed, except # for the grub2-efi-*-cdboot package @anaconda-tools --optional @core anaconda isom...

...US # Repositories to use 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.

I was just wondering how (or indeed if) people use the %include directive in Kickstart configuration files when building systems via NFS. I've been trying to modularise our Kickstart files a little to make things more readable, having generic defaults and role specific stuff split out into separate configs. I've tried this configuration... [root at archive kickstart]# cat

...disk and parted works fine, I can view, partition and write a partition table and the 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 stil...

...ves are /dev/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=...

...ccelerate kickstart.cfg: text install cdrom lang en_US.UTF-8 keyboard us network --onboot yes --device eth0 --bootproto dhcp --noipv6 rootpw testing123 firewall --service=ssh authconfig --enableshadow --passalgo=sha512 selinux --disable timezone --utc America/New_York bootloader --location=mbr zerombr clearpart --all --initlabel autopart reboot %packages --nobase @core %end ? Matthew Crocker President - Crocker Communications, Inc. Managing Partner - Crocker Telecommunications, LLC E: matthew at corp.crocker.com E: matthew at crocker.com

...l.com> writes: > > > # 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" > &g...

...ice eth0 --bootproto static --ip 192.168.1.165 --netmask 255.255.255.0 --gateway 192.168.1.1 --hostname eagle.mydomain.com firewall --enabled --port=22:tcp --port=80:tcp --port=21:tcp --port=25:tcp --port=443:tcp selinux --disabled authconfig --enableshadow --enablemd5 timezone America/Vancouver zerombr yes bootloader --location=mbr clearpart --all --initlabel part /boot --fstype ext3 --size=1000 --ondisk=sda part /var --fstype ext3 --size=12000 --ondisk=sda --asprimary part /usr --fstype ext3 --size=3000 --ondisk=sdb part / --fstype ext3 --size=3000 --ondisk=sda part /tmp --fstype ext3 --size=500...

...g en_US #Language modules to install langsupport --default en_US en_US #System keyboard keyboard us #System mouse mouse genericps/2 #System timezone timezone America/Chicago #Use text mode install #text #System bootloader configuration bootloader --location=mbr # Clear the Master Boot Record zerombr #Device probing device eth0 bcm4400 device eth0 sis900 device eth0 8139too device eth0 e100 device eth0 e1000 device eth0 3c59x deviceprobe #Install Red Hat Linux instead of upgrade install #Use FTP installation media #url --url ftp://172.50.10.122/tftpboot/FC6 ftp --server 172.50.10.122 --dir /...

...check or if you've resolved a similar issue I would be quite interested. More details: I see the same behaviour after cutting most items out of the cobbler kickstart template, however I confirm that /run/install/ks.cfg in the anaconda environment has the following: ignoredisk --only-use=sda zerombr bootloader --location=mbr clearpart --all part / --label="/" --fstype=ext4 --grow --asprimary program.log from the anaconda environment is here: https://gist.github.com/christopherwood/72f390d7e5788b9bc9e841d40c926895 The system does boot and install just fine from the CentOS 7.4 iso w...