similar to: RAID help

I am testing some kickstarts on ESXi virtual machine with pair of 16GB disks. Partitioning is lvm over raid. If i am using "logvol --grow i get "ValueError: not enough free space in volume 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

Hello. A couple of years ago I installed two file-servers using kickstart. The server has two 1TB sata disks with two software raid1 partitions as follows: # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb4[1] sda4[0] 933448704 blocks [2/2] [UU] md0 : active raid1 sdb1[1] sda2[2](F) 40957568 blocks [2/1] [_U] Now the drives are starting to be failing and next week

Hello, I'm trying to do a kickstart install of centos5. 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

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.

Has anyone gotten this to work ? I can define a raid device but cant put a VG on it. I then tried 'autopartition' and it created an 'LVM' of sorts, when I tried to edit it I wasnt able to as a message appeared saying, LVM editing was not allowed in text mode. Any help ? Cheers, Brian. PS - PIII-500mhz 128mb RAM, 4mb AGP.

I am trying to install CentOS 4.6 to a pair of 750GB hard drives. I can successfully install to either of the drives as a single drive, but when I try to use both drives and mirror the partitions, I start having problems. Anaconda crashes as it is trying to format the drives. This is what I'm trying to create: /dev/md0: 200MB, /boot /dev/md1: 2GB, swap /dev/md2: rest of the

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant 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)

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"

I have a p4 motherboard with 2 ide interfaces, I connect 2 40 GB drives as hda and hdc, I install Centos 4 from a CDROM, and partition the drives as 2 x raid partition each plus a swap partition on hda, the make md0 and md1 to install /boot and / respectively. Install goes well, everything looks great, go to reboot from drives, and all I get is "grub" but no boot. I have tried this ten

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 1 kickstart file that works for either a hda

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

Hey, Can anyone tell me why option 1 works and option 2 fails ? I know I need swap and such, however in trouble shooting this issue I trimmed down my config. It fails on trying to format my logical volume, because the mount point does not exist (/dev/volgroup/logvol) It seems that with option 2, the partitions are created and LVM is setup correctly. However the volgroup / logvolume was not

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

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

Hi All, I cannot seem to find a resource that will allow me to RAID5 3 x 1tb drives on system install. Can this be done? -jason

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

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

I am an experienced MS administrator of W2003 servers & Exchange systems. I have 5+ years UNIX mid-level experience but not in centOS. Grounded in SCO UNIX (the real SCO UNIX). We want to use CentOS on a recently grave yarded Dell poweredge 400SC server. This is a P4 3.0 Ghz, w/4GB memory, 2 SATA 250 GB disks. We want to use this server w/CentOS5, to provide file and print resources to 100

> On 1/9/19 2:30 AM, Gary Stainburn wrote: >> 1) The big problem with this is that it is dependant on sda for booting. >> I >> did find an aritcle on how to set up boot loading on multiple HDD's, >> including cloning /boot/efi but I now can't find it. Does anyone know >> of a >> similar article? > > > Use RAID1 for /boot/efi as well.? The

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.