similar to: Not getting bootloader installed with CentOS 8 + mdraid

I have been building up a script to quickly and easily make CentOS/RHEL and Fedora VMs from kickstart files for a long time, and thought I'd see if anyone else was interested. It's especially useful IMHO if you are working on building kickstarts, because you can fairly rapidly iterate and test. I've got it built as an RPM, so if others think this is useful, I might submit it to

Once upon a time, Simon Matter <simon.matter at invoca.ch> said: > Are you sure that's still true? I've done it that way in the past but it > seems at least with EL8 you can put /boot/efi on md raid1 with metadata > format 1.0. That way the EFI firmware will see it as two independent FAT > filesystems. Only thing you have to be sure is that nothing ever writes to >

Is there a way to get GRUB2 and the kernel to run a "serial" console under KVM? I'm running a Fedora 20 desktop, with libvirt-managed VMs. When I run a CentOS 6 VM, I can set both the boot loader and kernel up to use ttyS0 and get a console compatible with "virsh console". When I try the same with a CentOS 7 VM, it doesn't work. If I set it to ttyS0, I just

Last time I saw it, I had just upgraded my CentOS 7 box with the 3.10.0-514 kernel and it rebooted already configured into debug mode. Not sure if this is a ?feature? of the newer kernels or not but glad to see that i?m not the only one who had noticed this. # awk -F\' '$1=="menuentry " {print i++ " : " $2}' /etc/grub2.cfg 0 : CentOS Linux

In previous CentOS releases, virt-what was included in the install image. This made it easy for me to spin a custom ISO with my package set and a kickstart that would add open-vm-tools or ovirt-guest-agent as appropriate (when installing the respective guest environments). I updated my ISO to 7.2, and virt-what is nowhere to be found. I assume this is copied from RHEL; anybody know any

We have a working PXE setup. I've tried to adapt it to UEFI as per RHEL6 manual, but the client won't boot. Strangely, tcpdump shows that the client tries to download all files via tftp from the dhcp server rather than the tftp server (they are different). next-server is pointing to the tftp server. Any clues?

Hi, I noticed that some, but not all, of my CentOS 7 machines have these kernel parameters for turning on systemd debug level logging added to the grub.cfg file. systemd.log_level=debug systemd.log_target=kmsg The parameters are *not* in the /etc/default/grub file, so if I rebuild grub.cfg with grub2-mkconfig, they disappear. I am a bit puzzled over how they got introduced. Has anyone else

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda

Hi, I've just started testing CentOS 4.4 installs. When installing on two mirrored drives, the bootloader got installed into the first partition, instead of MBR. It was a kickstart install, and I used "bootloader --location=mbr" in the kickstart file (which is also a default). However, when looking into /root/anaconda-ks.cfg file, misteriously it was changed to

----- On 1 Nov, 2017, at 13:07, Chris Adams linux at cmadams.net wrote: | Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> On 11/01/2017 03:25 PM, Chris Adams wrote: |> >Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> >>Okay, so it looks like I can simply change ksdevice=eth0? to |> >>bootdev=eth0, correct? |> >I

> Am 08.05.2019 um 19:20 schrieb mark <m.roth at 5-cent.us>: > > Leon Fauster via CentOS wrote: >> Hi all, >> >> >> I still use the following kickstart partition scheme for C7 installations >> (via virt-install): >> Briefly, fixed size for /root and /boot, and the rest is filled up for >> /srv. >> >> The same kickstart

Hi, I am trying to adapt my kickstart usb key to optionally auto-setup mdraid on two disks...? But I have one server that keeps attaching the usb key to sda instead of sdc... My kickstart creates the raid devices on sdb and sdc partitions; but then I expect it not to work once the key is unplugged and the disks fall back to sda and sdb... Can I just modify mdadm.conf at the end, just

This should be easy to answer (I hope).? We routinely kickstart boxes to use for managing our customers RADIUS/DHCP configurations (along with other things).? We've had a C7 kickstart in place since I built one in May and are finally starting to roll it out for new installations.? But, I'm curious as to what ksdevice= actually does. With the C6 we routinely used ksdevice=eth0 since we

I checked and secure boot is turned off. Jonathan brings it exactly to the point: we have to face UEFI because legacy mode is fading out, if I enable legacy mode I can't even boot anymore through the network (PXE) as these newer network cards can only boot PXE with UEFI. In the mean time I have installed Ubuntu 17.10 with Xen and I was lucky to see that this combination works with UEFI even

Hello, I am trying to build a PXE boot image for CentOS 7. livemedia-creator --make-pxe-live --ks=ks --no-virt It runs the entire process and then it says: losetup: /dev/: detach failed: Inappropriate ioctl for device 2019-12-26 11:49:47,293: Disk Image install successful 2019-12-26 11:49:47,293: working dir is /var/tmp/tmpKwqC77 mount: /dev/loop0 is write-protected, mounting read-only mount:

Once upon a time, Chris Adams <cma at cmadams.net> said: > I can confirm that a message with multiple Subject: and multiple From: > headers does not get filed correctly into the Spam folder. The > sieve-test tools shows the correct action, but when the message comes in > via LMTP, it goes into INBOX. Okay, digging some more, it looks like something in sieve is overwriting the

Sun, 15 Nov 2020 14:16:48 -0800 Gordon Messmer <gordon.messmer at gmail.com>: > On 11/15/20 3:32 AM, ?ukasz Posadowski wrote: > > Do anyone can suggest what else I forgot to do? > > > Use metadata version 1.2 instead of 0.9. > > You need for the filesystem to be not visible until after the RAID is > assembled, and the easiest way to do that is to put the

On 11/01/2017 03:25 PM, Chris Adams wrote: > Once upon a time, Mark Haney <mark.haney at neonova.net> said: >> Okay, so it looks like I can simply change ksdevice=eth0? to >> bootdev=eth0, correct? > I believe you can just leave both off (IIRC for CentOS 6 as well) if you > add "ipappend 2" to the pxelinux stanza. > I probably should have clarified that

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > On Tue, Apr 26, 2016 at 3:01 PM, Chris Adams <linux at cmadams.net> wrote: > > Once upon a time, Chris Murphy <lists at colorremedies.com> said: > >> On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > >> > I have several recently-installed CentOS 7

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > > I have several recently-installed CentOS 7 servers that keep having > > systemd-journald corruption > > Determined with 'journalctl --verify' or another way? I get messages like this in dmesg: [4756650.489117]