search for: ondisk

I have a couple lines like: part / --ondisk=sda --fstype ext3 --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /home --ondisk=sda --fstype ext3 --size=1 --asprimary --grow in my kickstart file. Is there a way to have 1 kickstart file that works for hda and sda both??? So I would like to have...

...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 sdb part swap --size 2048 --asprimary --ondisk sdb part raid.02 --size 40000 --asprim...

...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=5000 --ondisk=sdb part /downloads --fstype ext3 --size=10000 --ondisk=sdb part /d1 --fstype ext3 --size=450...

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 --fstype ext3 --level=RAID1 raid.01 raid...

.... I'm pulling it off a network server and i'm getting an error, in the parsing of the file. It refers to line 31, i'm not going to show the complete file, but here is the indicated line: raid swap --fstype swap --level=RAID1 raid.4 raid.7 and the raid lines: part raid.7 --size=512 --ondisk=hdb part raid.4 --size=512 --ondisk=hda My parse error message is: "option --device is required" The raid lines indicate which drive to work on, i'm not seeing the issue. Any help appreciated. Thanks. Dave.

This problem occurred in both CentOS 5.2 and the new (awesome!) 5.3: I'm using a SuperMicro motherboard with a 6 port NVidia SATA controller on the motherboard and an 8 port SuperMicro Marvel controller in a slot. In my kickstart file, I have part raid.01 . --ondisk=sda . part raid.02 . --ondisk=sdb . part raid.03 . --ondisk=sdc . part raid.04 . --ondisk=sdd . . raid / --level=RAID1 --fstype=ext3 --device=md0 raid.01 raid.02 raid.03 raid.04 When I only have 4 drives installed in the system, this works fine. However, whenever I have more than 4 dr...

...ll): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" --name=00 --vgna...

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 only new item other th...

...tion, may have something to do with the Centos install? I took my Anaconda-ks.cfg from my system, turned it into a ks.cfg and did the install. Everything SEEMS ok, but why? First the partitioning information: ks.cfg supplied: clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --start=14 --end=796 --ondisk=hda part pv.34 --start=797 --end=2303 --ondisk=hda part swap --start=2304 --end=2434 --ondisk=hda volgroup VolGroup00 --pesize=32768 pv.34 logvol /var/opt/scalix --fstype ext3 --name=Scalix --vgname=VolGroup00 --size=8192 anaconda-ks.cfg repo...

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"

As I understand anaconda uses parted to partition (starting from centos 6), using this as example (kickstart configuration file): clearpart --all --drives=sda --initlabel part /boot --asprimary --size=200 --fstype=ext2 --ondisk=sda part swap --asprimary --size=16384 --fstype=swap --ondisk=sda part / --asprimary --size=512000 --fstype=ext4 --ondisk=sda part /scratch --asprimary --size=1 --grow --fstype=ext4 --ondisk=sda I can see no problems in parted: GNU Parted 2.1 Using /dev/sda Welcome to GNU Parted! Type 'help...

...=no rhgb quiet" --md5pass=$1$F/BHluSk$YticIZvEKa6Ckmw6GYTno. bootloader --location=mbr --boot-drive=sda --append="crashkernel=no rhgb quiet" # Partition clearing information clearpart --all --initlabel --drives=sda # Disk partitioning information part /boot --fstype="xfs" --ondisk=sda --size=500 --asprimary part / --fstype="xfs" --ondisk=sda --size=5000 --asprimary part /usr --fstype="xfs" --ondisk=sda --size=30000 --asprimary part swap --fstype="swap" --ondisk=sda --size=4000 part /var --fstype="xfs" --ondisk=sda --size=3000 part /tmp...

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

On Thu, 2016-08-04 at 22:21 -0400, Jonathan Billings wrote: > Is it a BIOS boot, or are you using the UEFI firmware for booting? > Either way, you might need a small boot partition (not /boot) at the > beginning of the disk. /boot/efi formatted FAT16, circa 150 MB -- Regards, Paul. England, EU. England's place is in the European Union.

...ing # Using the default partition table. clearpart --all --initlabel # can I add the '--drives=sda' sda section to the end of the above line? i got from example file wanted to combine with initlabel statement.. # clearpart --all --drives=sda part / --fstype "ext3" --size=1012 --ondisk=sda # do i need to call the sda scsi disk out if there are no IDE drives? part /boot --fstype "ext3" --size=256 --ondisk=sda part swap --size=8192 --ondisk=sda part /home --fstype "ext3" --size=8192 --ondisk=sda part /var --fstype "ext3" --size=8192 --ondisk=sda p...

I am trying to install Centos 7 on a couple 4TB drives with software raid. In the Supermicro bios I set UEFI/BIOS boot mode to legacy. I am using the Centos 7 minimal install ISO flashed to a USB thumb drive. So I do custom drive layout something like this using sda and sdb. Create /boot as 512 MB XFS raid1 array. Create SWAP as 32 GB SWAP raid1 array. Create / on 3.xxx TB XFS raid1 array.

...tem 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 /boot --device=0 --fstype="xfs" --level=RAID1 raid.01 raid.03 raid pv....

...=mbr # --append hdb=ide-scsi # 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 clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --size=1024 --grow --ondisk=hda part /var/spool --fstype ext3 --size=1024 --grow --ondisk=hda part /var/cache --fstype ext3 --size=1024 --grow --ondisk=hda part /var/log --fstype ext3 --size=1024 --grow --ondisk=hda part swap --size=128 --grow --maxsize=256 --ondisk=hda #...

...r=$HD1SHORT --append=\"rhgb quiet\" " > /tmp/partition-information echo "clearpart --all --initlabel " >> /tmp/partition-information echo "part --ondisk=$HD1SHORT raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --size=20000 " >> /tmp/partition-information echo "part --ondisk=$HD1SHORT swap --asprimary --bytes-per-inode=4096 --fstype="swap" --size=4000 " >> /tmp/part...

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