47

Create a directory to mount your source. mkdir /tmp/bootiso Loop mount the source ISO you are modifying. (Download from Red Hat / CentOS.) mount -o loop /path/to/some.iso /tmp/bootiso Create a working directory for your customized media. mkdir /tmp/bootisoks Copy the source media to the working directory. cp -r /tmp/bootiso/* /tmp/bootisoks/ ...


10

I attempted bburky's fix, but found that the following was needed in Debian Wheezy... d-i apt-setup/use_mirror boolean false d-i apt-setup/cdrom/set-first boolean false d-i apt-setup/cdrom/set-next boolean false d-i apt-setup/cdrom/set-failed boolean false


9

i guess it is because you have chosen a new Volume Id by -V "NewFedoraImage". I am the developer of xorriso and have experienced a similar problem when experimenting with GPT enhanced isohybrid in Fedora-LiveCD.iso. It did not work unless i used the same -V as with the original image. In an old mail text of mine i see a reference to "/dev/disk/by-label/". ...


7

I was able to solve this by doing the following: Place the kickstart file at the top of the isolinux directory and make sure it is named ks.cfg my isolinux.cfg file looks like this: label linux menu label ^Install CentOS 7 kernel vmlinuz append initrd=initrd.img inst.ks=hd:LABEL=CentOS\x207\x20x86_64:/isolinux/ks.cfg inst.stage2=hd:LABEL=CentOS\x207\...


7

You're right that lvmpv isn't a real filesystem type. But, the point of that parameter isn't as much to define a filesystem. It's to define what goes into the partition. In this case, instead of a filesystem, the partition contains an LVM physical volume. On that note, you may wish to study LVM a bit closer. The point of it is to create logical volumes, i.e....


6

With EL6, all you need to type is ks=http://example.com/ks/ks.cfg. You don't need linux anymore. As for network configuration, you can enter some basic network parameters at the same prompt... Most people prefer DHCP, the default... but something like this also works... Append this to the boot line: ks=http://example.com/ks/ks.cfg ip=192.168.10.17 netmask=...


6

The %post section won't do what you need without some extra work - you need to do this copy inside a %post --nochroot section so you have access to the CD. You can probably issue a mount command inside %post, but using %post --nochroot is likely easier. I don't remember the source ISO layout offhand, but it'll be there somewhere.


5

Where would the / filesystem reside, if an operating system were installed? Would it be in the same place on all the nodes you intend to install? You could test for the presence of a partition: [ -b /dev/sdXY ] && { do something ; } Or a logical volume: [ -b /dev/mapper/vg00/lvXYZ ] && { do something ; } You could attempt to mount it, ...


5

The CentOS 7 anaconda "repo" command supports --install, which installs the repo information on the system being built: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html


5

Make sure you have shadow and passalgo=sha512 on a machine, set the root pass to whatever password you want on that machine and take it from /etc/shadow and put it in the kickstart. This is not advisable for production use. To do it programmatic, use the crypt library of your chosen language that generates the kickstart file: RUBY: 'password'.crypt('$6$' +...


5

If you're receiving an error message similar to the following in your EL6 kickstart, you'll need to add zerombr to the kickstart command set. You should also have this instead: zerombr clearpart --all --initlabel From the documentation: zerombr: If zerombr is specified any invalid partition tables found on disks are initialized. This destroys all ...


5

You need to add the system-config-firewall-base package, which provides the lokkit command used to configure the firewall during kickstart. Versions of RHEL/CentOS prior to 6.6 automatically included this package, see https://bugs.centos.org/view.php?id=7956 and https://bugzilla.redhat.com/show_bug.cgi?id=1161682 for discussion of the issue.


5

I was having the exact same problem until I realized that I hadn't updated my pxe tftpboot environment to agree with my up-to-date Centos 7.5 media, by copying Centos-7.5-version files from centos/7/os/x86_64/isolinux/.


5

If the filesystem was ext[234] I would guess you could probably do something like tune2fs -l /dev/devicename. # tune2fs -l /dev/sda3 | grep -i 'block' Block count: 9865984 Reserved block count: 493299 Free blocks: 8871467 First block: 0 Block size: 4096 Reserved GDT blocks: 1024 Blocks per group: ...


4

Your problem (probably) is with nouveau. I have seen this before on machines with Optimus chipsets, but it apparently can also rear it's ugly head on machines that have just NVIDIA hardware. Try and pass nouveau.modeset=0 on the kernel command line when starting the machine.


4

I set the hostname in the kickstart file directly. If you're trying to reuse the same template, you could get creative and use a bit of PHP to pass something to the installer. Kickstart files are http, so you could do something like: ks=http://repo.brazzers.com/ks/kickstart.php?hostname=kitty ...where kitty is a variable in the kickstart file that ...


4

You can try using a snake server. Once configured, both the server and the client machine, it will provide a curses interface to select a kickstart file amongst other options.


4

If you have a separate physical partition to copy your installation media to, you could do that and modify Grub to Kickstart on boot. install harddrive --partition=sdb2 --dir=/path/to/installation-media Add to /etc/grub.conf: title Reinstall CentOS 6 root(hd0,0) kernel /vmlinuz-kickstart ks=kickstart.cfg initrd /initrd-kickstart.img You'll ...


4

I've tried everything, but only this seems to work: put the ks.cfg inside the initrd. So the steps below extract initrd, add the ks.cfg in there, and recreate it. Tested with CentOS7 First mount the original .iso image on your pc, and copy its contents under tmp/ Then, #Keep the original file cp -ai tmp/isolinux/initrd.img initrd.img.orig mkdir irmod cd ...


4

I guess the error messages are caused by a typo: url --url http://centos.mirror.iweb.ca/7/os/x86_64/ should be url --url=http://centos.mirror.iweb.ca/7/os/x86_64/ By the way, I think you should add "@core" to the "%packages" section too; it includes a minimal set of very essential RPMs.


4

I believe you need to remove --device eth0 from the network command in the kickstart. Centos7 now uses some weird network device names (for example, on my vmware Centos7 VM it automatically detected the network device as Eno160, not eth0) network --bootproto dhcp --ipv6 xxxxx::10/64 --gateway xxxxx:1 --nameserver --hostname foo.example.com


4

You're trying to install from the installation DVD, which due to space constraints doesn't contain every possible package. To install packages that aren't on the DVD during installation, you'll need to do a network installation instead, generally from a local mirror accessible via NFS or HTTP, or a public mirror.


4

This is a known bug. See: https://bugzilla.redhat.com/show_bug.cgi?id=1093144 and https://bugzilla.redhat.com/show_bug.cgi?id=1120339 EDIT: Those bugs applied to the release candidate (RC). which are closed in CentOS 7.0.1406


4

I've finally solved my own issue! I'll put this as an answer so that if anyone else sees it they will know the cause. However, I assume only Canadians will be affected... It turns out that the problem was with the lang en_CA.UTF-8 line in the kickstart file. I changed this to lang en_US.UTF-8 and the installation completes normally. I may ask another ...


4

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html The official documentation states the --gid directive as being buggy.


4

The CentOS ISO images include rd.live.check as a boot command line option. If you haven't rolled your own images, or manually removed this each time you boot, then the media check will occur. The following appears when booting the CentOS 7.2.1511 netinstall image: To resolve the problem, tap your up arrow key to select "Install CentOS 7" instead of "Test ...


4

You would simply need to add the --grow option to your logvol line. From the RHEL 7 documentation: --grow - Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting, if one is specified. A minimum size must be given, using either the --percent= option or the --size= option. Source: RHEL 7: 24.3.2 - Kickstart ...


4

The defined way of locking the root account in a kickstart is with: rootpw --lock --lock - If this option is present, the root account is locked by default. This means that the root user will not be able to log in from the console. This option will also disable the Root Password screens in both the graphical and text-based manual installation.


4

%post --nochroot --logfile=/mnt/sysimage/root/ks-post.log cp /run/install/repo/script.sh /mnt/sysimage/root/ chroot /mnt/sysimage/ /bin/sh /root/script.sh %end


3

You may use the %post (post-installation) part of the kickstart file to run the firewall rules, or even create a basic firewall script. I found, on this site an usage example of post-installation configuration. And here you have another explanation of how to achieve what you want. EDIT: %post suggestion: %post mkdir /usr/sample sed -i 's/^\(ENABLE=\s*\).*...


Only top voted, non community-wiki answers of a minimum length are eligible