search for: ignoredisk

...is logged in: /run/user/0 /run/user/65000 Seems if the partition is there when the monitor is set or is added while the monitor is active the monitor will keep looking for it and these are meant to go away. We thought "OK we can just ignore those" so we added a line to /etc/snmpd.conf : ignoredisk /run/user/* but that has not helped :( Does anybody have a recommendation on how we can stop those partitions from being seen on walks so we can stop being alerted about partitions for which we are not interested in monitoring their available space? Thanks, Cameron

...0 > > Seems if the partition is there when the monitor is set or is added while > the monitor is active the monitor will keep looking for it and these are > meant to go away. > > We thought "OK we can just ignore those" so we added a line to > /etc/snmpd.conf : > ignoredisk /run/user/* > > but that has not helped :( > > Does anybody have a recommendation on how we can stop those partitions from > being seen on walks so we can stop being alerted about partitions for which > we are not interested in monitoring their available space? I had a quick pl...

...ssue with storage configuration / bootloader configuration... I can install it using the ISO, with basic configuration. The /root/anaconda-ks.cfg looks like the following (I striped some part, I cannot copy past because I have only console access through a secured VPN :-/ ): firstboot --enable ignoredisk --only-use=mpatha,sdc,sdd,sdb,sda bootloader --location=mbr --boot-drive=mpatha autopart --type=lvm clearpart --all --initlabel --drives=mpatha %packages @base @core %end My ks.cfg template is identical (I also cannot attach it unfortunately?). I tried several things like: - put sda as boot-driv...

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

.... 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) My kickstart storage config looks like this: bootloader --location=mbr --driveorder=sda,sdb zerombr ignoredisk --only-use=sda,sdb clearpart --all --drives=sda,sdb part raid.boot0 --size 1000 --ondrive=sda part raid.swap0 --size 8192 --ondrive=sda part raid.root0 --size 8000 --grow --ondrive=sda part raid.boot1 --size 1000 --ondrive=sdb part raid.swap1 --size 8192 --ondrive=sdb part raid.root1 --size 8000 --...

...39;t want you to tell it to put it on sda1 when using autopart. > Pretty much autopart wants to be told very little, and Phil's > kickstart is being too explicit for autopart. > > Thanks for all the comments to date, so I should try:- clearpart --all --initlabel --drives=sda,sdb ignoredisk --only-use=sda,sdb # System bootloader configuration bootloader --append=" crashkernel=auto" --location=mbr autopart --type=lvm There is also a nvme drive in the system too, hence the use of "ignoredisk --only-use=sda,sdb?. Phil

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 disk added to a one-disk system will always show up as sdb, and sda w...

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 does not exist ? step comple...

...m this install, and tried to use this as the install kickstart. It failed. I deleted all the partitions and tried again no joy, the default ks is as follows:- #version=DEVEL # Use network installation url --url="http://192.168.0.156/CentOS7-x86_64/disc1/" # Use text mode install text ignoredisk --only-use=sda,sdb # Keyboard layouts keyboard --vckeymap=us --xlayouts='us' # System language lang en_US.UTF-8 # Network information network --bootproto=dhcp --device=enp0s31f6 --ipv6=auto --activate network --hostname=localhost.localdomain # Root password rootpw --iscrypted # Do not c...

...about what I would double-check or if you've resolved a similar issue I would be quite interested. More details: I see the same behaviour after cutting most items out of the cobbler kickstart template, however I confirm that /run/install/ks.cfg in the anaconda environment has the following: ignoredisk --only-use=sda zerombr bootloader --location=mbr clearpart --all part / --label="/" --fstype=ext4 --grow --asprimary program.log from the anaconda environment is here: https://gist.github.com/christopherwood/72f390d7e5788b9bc9e841d40c926895 The system does boot and install just fine f...

...000 > > Seems if the partition is there when the monitor is set or is added while > the monitor is active the monitor will keep looking for it and these are > meant to go away. > > We thought "OK we can just ignore those" so we added a line to > /etc/snmpd.conf : > ignoredisk /run/user/* > > but that has not helped :( > > Does anybody have a recommendation on how we can stop those partitions from > being seen on walks so we can stop being alerted about partitions for which > we are not interested in monitoring their available space? You could try it t...

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

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

...ed_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } redhat/swap failed Kickstart:- #version=RHEL7 # System authorization information auth --enableshadow --passalgo=sha512 # Use CDROM installation media cdrom # Run the Setup Agent on first boot firstboot --enable ignoredisk --only-use=vda # Keyboard layouts keyboard --vckeymap=us --xlayouts='us' network --device eth0 --bootproto static --ip 10.97.60.50 --netmask 255.255.255.0 --gateway 10.97.60.254 --nameserver 10.97.2.1 --noipv6 # System language lang en_US.UTF-8 # System timezone timezone America/Los_Angel...

...mp 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 install graphical # Run the Setup Agent on first boot firstboot --enable ignoredisk --only-use=sda # Keyboard layouts keyboard --vckeymap=de-nodeadkeys --xlayouts='de (nodeadkeys)' # System language lang de_DE.UTF-8 # Network information network --bootproto=dhcp --device=enp0s3 --ipv6=auto --no-activate network --hostname=localhost.localdomain # Root password rootpw --...

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

...DEBUG anaconda: is_valid_stage1_device(sda1) returning False 06:08:54,867 ERR anaconda: BootLoader setup failed: failed to find a suitable stage1 device 06:08:54,979 INFO anaconda: fs space: 0 B needed: 2861.02 MiB The relevant kickstart section is:- clearpart --all --initlabel --drives=sda,sdb ignoredisk --only-use=sda,sdb # System bootloader configuration part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 autopart --type=lvm So it's failing on the bootloader section. I've tried with th...

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.

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"

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