similar to: Centos 6 / Kickstart Using degraded mdadm RAID1

Gordon Messmer 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 --type=lvm > > A couple of things to consider: > * The documentation for

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)

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

On Sun, 21 Aug 2016 at 12:51 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/19/2016 11:35 PM, Phil Manuel wrote: > > The install fails under UEFi due to the fact the partitions are not > cleared, and it doesn?t have any space to continue. Is there an extra step > I need to do to remove the original partitions before the new layout will > work ? > > >

I have a kickstart file that I am using to install multiple machines. If I install with no %post script, everything runs great. When I add the following %post section, if fails. I have been working on this for a few days now without luck, Any help would be appreciated. Here is the error, the script follows. Traceback (most recent call first): File

> Hi. > > CENTOS 7.6.1810, fresh install - use this as a base to create/upgrade > new/old machines. > > I was trying to setup two disks as a RAID1 array, using these lines > > mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 > /dev/sdc1 > mdadm --create --verbose /dev/md1 --level=0 --raid-devices=2 /dev/sdb2 > /dev/sdc2 > mdadm

I have a large disk full of data that I'd like to upgrade to SW RAID 1 with a minimum of downtime. Taking it offline for a day or more to rsync all the files over is a non-starter. Since I've mounted SW RAID1 drives directly with "mount -t ext3 /dev/sdX" it would seem possible to flip the process around, perhaps change the partition type with fdisk or parted, and remount as

I have been reading about software raid. I configured my first software raid system about a month ago. I have 4 500 Gig drives configured in RAID 5 configuration with a total of 1.5TB. Currently I configured the complete individual drivers as software raid, then created a /dev/md0 with the drives I then created a /file_storage partition on /dev/md0. I created my /boot / and swap partitions on

Hi all, This the latest output from anaconda.log:- 06:08:54,828 DEBUG anaconda: new disk order: [] 06:08:54,832 DEBUG anaconda: new disk order: [] 06:08:54,851 DEBUG anaconda: stage1 device cannot be of type disk 06:08:54,865 DEBUG anaconda: _is_valid_disklabel(sda1) returning True 06:08:54,867 DEBUG anaconda: _is_valid_size(sda1) returning True 06:08:54,867 DEBUG anaconda:

Is it possible to install CentOS 5 with a degraded RAID 1 array using kickstart? I have the kickstart file already created but the "server" I want to use only has 1 hard drive in it at the moment. Until I can order a 2nd drive, I wanted to install the OS then once I received the replacement drive "fix" the array. I have seen instructions how to do this manually, but so far have

I am trying to install a CentOS qemu/kvm virtual machine using a virt-install script[1]. Since Anaconda text user interface does not permit to users to edit filesystem type and mount points[2], I decided to use a kickstart file to customize such settings. To create a kickstart file, I used a trick: I installed a CentOS machine using Anaconda graphical user interface, and I made all customizations

Hi list, I'm new with UEFI and GPT. For several years I've used MBR partition table. I've installed my system on software raid1 (mdadm) using md0(sda1,sdb1) for swap, md1(sda2, sdb2) for /, md2 (sda3,sdb3) for /home. From several how-to concerning raid1 installation, I must put each partition on a different md devices. I've asked times ago if it's more correct create the

Hi, Does anyone know why an Anaconda Kickstart installation deploys more rpm packages than a manual "basic" installation? In both cases the following package groups were installed/used according to anaconda-ks.cfg in root home directory: @core, @server-policy, @workstation-policy

Hi. CENTOS 7.6.1810, fresh install - use this as a base to create/upgrade new/old machines. I was trying to setup two disks as a RAID1 array, using these lines mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1 mdadm --create --verbose /dev/md1 --level=0 --raid-devices=2 /dev/sdb2 /dev/sdc2 mdadm --create --verbose /dev/md2 --level=0 --raid-devices=2

Hi messmer, seems that anaconda supports partitioned RAID devices. Disk selection see one mdraid device and permits to create partition on it. Il 13/03/2016 01:04, Gordon Messmer ha scritto: > On 03/12/2016 08:22 AM, Alessandro Baggi wrote: >> From several how-to concerning raid1 installation, I must put each >> partition on a different md devices. > > Not necessarily. You

Hi, Is is possible to use kickstart file to install rhel from dvd drive? Mainly idea is to clone one anaconda.ks file to about twenty machines.? examples? ftp/http/dhcp is not possible due to network limitations. -- Eero

I've been reading the RHEL 5 manual/guide linked from centos, and the idea of LVM with expandable partitions seems like a great idea (yes duh why else would it exist if not?). Although the documentation shows a screenshot of how the final setup would look like with LVM & RAID together, it doesn't actually gives the step. 1. Am I correct in thinking it should be done in this way -

So I took the anaconda cfg, commented out the partition/disk pieces and ran it off my repo server and it almost worked. Little things like not including things I had done on network setup. No first boot.... :) So now I am reading up on building a kickstart cfg http://wiki.centos.org/TipsAndTricks/KickStart http://www.centos.org/docs/5/html/5.2/Installation_Guide/s1-kickstart2-howuse.html

On Tue, 23 Aug 2016 at 02:18 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/21/2016 11:56 PM, Phil Manuel wrote: > > part /boot/efi --fstype="efi" --size=200 --ondisk=sda > > And I have tried the latter with location as mbr still fails > > What am I missing ? > > > I very vaguely remember struggling with this as well, but I can't find

I took my anaconda-ks.cfg file, cp to ks.cfg and copied to a floppy The isos have been copied to an ftp server. So I had the following lines in my ks.cfg intall url ftp://10.1.1.1// (yes the ftp server's directory is the Centos directory) This is along with all the appropriate network command to get the ethernet setup. I issue the linux ks=floppy (also tried linux