similar to: PXE install in a boot on san with LVM environment, fails after reboot

On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> 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

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

> 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

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

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:

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

Hi all, I'm running a Centos 7.2.1511 freshly installed on a SAN device. Everything is fine on the SAN side, but I have an issue with multipath or udev or systemd, I'm not sure. I when I boot my machine with the multipathd service enabled at boot, boot fails beacause some partitions on the multipathed device are missing from /dev. >From the boot rescue shell, if I do a fdisk -l

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

Hi all, We are hitting an error in the centos 7 installation with our kickstart configuration. =============================================================================== An unknown error has occurred =============================================================================== anaconda 21.48.22.56-1 exception report Traceback (most recent call first): File

I looked around but could not find any info on how to expand a libvirt managed LVM storage pool. I do not see any virsh command to do it but I was successful using the vgexpand command to add some more storage once I destroyed the pools and then restarted it. I'd like to verify that this is the proper way to grow the storage in a libvirt LVM storage pool. And this brings up a second

Howdy, The default partitioning scheme appears to be: swap /boot / small amount of space /home remainder of space. Is there any way via kickstart to have it just create swap with the recommended size, /boot, and then just / with the remainder without manually specifying the names of the lvs/vgs etc? I figured there would be an autopart -atomic option but that doesn't seem to exist. Any

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

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"

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

I'm having what appears at first glance to be a kickstart+anaconda issue on CentOS 7.4. As near as I can tell in the program.log in the anaconda environment, the partitioning instructions downloaded with the kickstart from cobbler appear to simply not be applied. Then /mnt/sysimage is not mounted, the logs are not copied to /mnt/sysimage/root and the installation stalls due to the anamon

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

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

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.

Hi there, after using Foreman successful on our clusters for more than a year. I'd like to reinstall a 90 node cluster with Centos 7.4. It's now running on Centos 7.3 . I'm not able to just update to 7.4 because of zfsonlinux dependencies and well - some nodes died and had to bare metal install them. So I was able to install these nodes successfully by pxe-booting and using a