similar to: Kickstart and CentOS 6 episode 2...

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

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

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

Hello Guys, after hours of uncessfull create example before i forward special parition tests. part ignoe --onpart But Installation hang out for parition the harddisk. jump to another console partitions are ok ? Which line/lines is/are missing? Andy #version=DEVEL # System authorization information auth --enableshadow --passalgo=sha512 # Use CDROM installation media cdrom # Use graphical

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"

Hi, I am trying to get my kickstart file that worked under 5.1 to work under 5.2 centos x86_64. This is the error that I get. On the screen it says Exception occured and gives me the option to save it. This is that file. I dont see any odd that would cause it to crash. Can anyone help. My kickstart file is in the mix below. Seems to be related to network, my line seems fine (I think) for

Hi, We are using PXELinux 1.75, ISC DHCP 3.0pl1 and atftp-0.6 to deploy RH 7.3 across a number of Dell Rackmount systems. I would like to set things up so that the RH boot kernel grabs the IP Address, gateway aand DNS address from the first DHCP request with 'ipappend 1', but so far have had no success, Kickstart issue a seconed request after booting the kernel. Here are my configs:

In article <CABLobCMg4irXK7Cw6xYhz9g6_0Jug9_Lq33zVyHdQE-JAxoPvw at mail.gmail.com>, Cameron Smith <cameron at networkredux.com> wrote: > We are running into an issue relating to snmpd and the temporary partitions > created in /run/user/ so any insight by someone with magical > net-snmp skills would be much appreciated. > > Our monitoring app walks all our servers. >

On 2/15/2017 11:04 AM, Andreas Benzler wrote: > after hours of uncessfull create example before i forward special > parition tests. > > part ignoe --onpart > > But Installation hang out for parition the harddisk. > > jump to another console partitions are ok ? There are an awful lot of typos in this email message, including the command you're saying you're

Hello, I need to automate installation of CentOS 7.0 using PXE and kickstart. My server is diskless, I'm installing CentOS on a 25GB LUN on a FC SAN with 4 paths. This LUN is the only one accessible by the server. Anaconda processes successfully the installation. But on reboot, I get stuck on a prompt after BIOS. I think I have an issue with storage configuration / bootloader

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

> On 28 Aug 2016, at 10:04 AM, Chris Murphy <lists at colorremedies.com> wrote: > > On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer > <gordon.messmer at gmail.com <mailto:gordon.messmer at gmail.com>> wrote: >> On 08/25/2016 11:35 PM, Phil Manuel wrote: >>> >>> The relevant kickstart section is:- >>> >>> part /boot/efi

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

We are running into an issue relating to snmpd and the temporary partitions created in /run/user/ so any insight by someone with magical net-snmp skills would be much appreciated. Our monitoring app walks all our servers. We modify /etc/snmp/snmpd.conf on all our servers to just have one line: rocommunity ourcommnuityname monitor.ing.app.ip This has worked just fine for almost 10 years. Since

By default, a kickstart installation will spread the configured partitions over all disks that are found, and the only way around that is to use --ondisk or ignoredisk. But I was wondering how reliable this method is. E.g. if there are four SATA ports on the system board, can I blindly assume that port one will always correspond to sda, port two to sdb, and so on? Can I assume that a second

Hi, I get the below issue when i install CentOS 5.6 x86_64 on IBM x3650 M3 when i run "linux xfs" at boot prompt. Please suggest/guide. Regards Kaushal 20:14:50 INFO : moving (1) to step confirminstall 20:14:55 INFO : moving (1) to step install 20:14:55 INFO : moving (1) to step enablefilesystems 20:14:55 DEBUG : starting mpaths 20:14:55 DEBUG : self.driveList():