similar to: Partition labelling

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

Hello Gentlemen, I would like to ask a question about an issue I have with the Centos 6.3 installation. I have installed a Centos 6.3 on a server we used before with 5.4 on Friday. I have created a KS file to let me connect to the server via VNC and have all repos and packages preconfigured. I only needed to partition the hard drive using VNC. During the partition process I selected which

I'd like to automate the upgrade from CentOS 4.6 to 5.1 as much as possible. Since upgrades per se are not really recommended, I'm planning to do a kickstart installation. However, I want to leave one of the existing partitions (/scratch) untouched during the installation. Here is my current layout (LogVol00 is swap so not shown in the df output below): # df -hl

Hey, I solved my "The installation source given by device ['sdb2'] could not be found". Apparently ignoredisk is so strong it not only ignores the disks to be partitioned but also the disks holding the installation source... Now I ran into: ? In interactive step cleardiskssel, can't continue In anaconda.log I saw: ? step installtype does not exist ? step confirminstall

I have a kickstart file with the following partitioning directives: part /boot --fstype ext3 --onpart=sda1 part pv.100000 --onpart=sda2 --noformat volgroup vol0 pv.100000 --noformat logvol / --vgname=vol0 --name=lvol1 --useexisting --fstype=ext4 logvol /tmp --vgname=vol0 --name=lvol2 --useexisting --fstype=ext4 logvol swap --vgname=vol0 --name=lvol3 --useexisting logvol /data --vgname=vol0

I fought with this for a day, and now am crying for help.... The goal is 5 partitions: boot, notebook suspend, / , /home. and swap. So I have to use LVM. Here are my commands: #System bootloader configuration bootloader --location=mbr #Clear the Master Boot Record zerombr yes #Partition clearing information clearpart --all --initlabel --drives=hda #Disk partitioning information part pv.1

I am using a kickstart file for CentOS 7 raid / --device=md0 --fstype="xfs" --level=1 --useexisting raid /home --noformat --device=md1 --level=1 --useexisting It is erroring out on the --useexisting. The exact text is: RAID volume "0" specified with "--useexisting" does not exist. What did I do wrong? Jerry

I'll be setting up a vSphere 4 environment hosting CentOS 5.4 on Netapp FAS and was curious how you guys are handling the automation of partition alignment within your linux guests. I'd like to use cobbler for dynamically creating kickstart scripts and wasn't sure if I could align my disk during install some how. Are there kickstart arguments to force the alignment on a 4k boundary?

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

Sorry - I did not include that I am actually "updating" a system from C6 to C7 and it has an existing RAID /dev/md0 and /dev/md1. Hit send to quick. Jerry On Wed, Aug 29, 2018 at 3:52 PM Jerry Geis <jerry.geis at gmail.com> wrote: > I am using a kickstart file for CentOS 7 > > raid / --device=md0 --fstype="xfs" >

I am trying kickstart for the first time, and am running into something I don't see described in the documentation. Somewhere between me and my purchasing department and Dell, my order for 6 PE 1850s was changed from "no installed OS" to WIndows. So I received the boxes with Windows pre-installed. I would like to delete the NTFS partition with Windows, but keep the Dell

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'm building kickstart files for use in doing automated installs of various systems. I would prefer to do fairly minimal amounts of work in the "%post" and postpone further installation and configuration until after the first reboot (or even later). It should be easy enough to add something to rc.local that will download scripts and run them, but I'm wondering if there is a

I found a kickstart installation with part pv.100000 --size=1 --grow volgroup vol0 pv.100000 creates a partition with a size of 8TB even though more than 9TB is available. I need to go in manually with gdisk to destroy the partition and recreate it with all available space. No filesystem is specified be cause want to use xfs, which kickstart does not support out of the box. This is under

At Tue, 23 Jun 2015 13:49:08 +0100 CentOS mailing list <centos at centos.org> wrote: > > Do most people today have /boot on a separate partition, > or do they (you) have it on the / partition ? The default CentOS installer always puts /boot on a separate partition. This is mostly because, the default CentOS installer uses LVM for the bulk of the disk and Grub is *generally*

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

I'm ill, i'm german ... the script is looks ok, copy from a slim installation of anaconda. Insert only the "pre part" and part /boot --onpart=/dev/sda1 part / --onpart=/dev/sda2 part swap --onpart=/dev/sda3 As i wrote: Jump over to another console and the partitions are there. Sincerely Andy Am Mittwoch, den 15.02.2017, 11:16 -0800 schrieb John R

I want to replace an existing 32bit with a 64bit installation (Centos 5). There's an existing LVM with lots of partitions. Most are used for Xen guests. The system itself uses only one of them plus a separate /boot partition that is not on LVM. What's the best course of action here? Should I do the reinstall with kickstart or better manually and reuse the existing filesystem? As I

I am trying to finish off a kickstart file for a computer lab on CentOS 6.5 machines. I don't want to have a separate /home as I'm going to add an entry in fstab for it to nfs mount /home from a server. Is there a way to have it autopart the rest of the file system without /home? Wanting to keep autopart for size since not all hard drives across the labs are the same. Matt

I've got some servers running other flavors of Linux (eg. FC2) and I'm wondering if I can install CentOS5 to a new empty partition (eg. on a new drive) while running under the old OS? It seems like the installer OS just needs some hardware sniffing ability and the ability to read the installation media and write to the target media, so in principle one should be able to install from a