Not to ask an odd question did you use a usb stick for the iso? If so did you dd the iso to the stick?
dp -----Original Message----- From: Alan Young [mailto:[email protected]] Sent: Monday, April 06, 2015 4:09 PM To: Provo Linux Users Group Mailing List - 100% Unmoderated, High Traffic Subject: Trying to build centos 7 iso and having weird problems. This procedure works just fine with the CentOS 6 NetInstall iso. I've downloaded the CentOS 7 1406 x86_64 NetInstall iso from the xmission mirror. I also tried direct from the CentOS repo. Same results both ways. If I edit the kernel command line when the iso boots and change vmlinux initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 quiet to vmlinux initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=http://vr.vwh.net/files/ks/ks_minimal_7.cfg The system boots and installs without any problems. When I take the following steps, I get the error detailed below. sudo mkdir -p CentOS-7.0-1406-x86_64-NetInstall.mounted sudo mount -o loop CentOS-7.0-1406-x86_64-NetInstall.iso CentOS-7.0-1406-x86_64-NetInstall.mounted sudo rsync -aviHSc --del --numeric-ids CentOS-7.0-1406-x86_64-NetInstall.mounted/ iso_root/ #modify iso_root/isolinux/isolinux.cfg $ diff -u {CentOS-7.0-1406-x86_64-NetInstall.mounted,iso_root}/isolinux/isolinux.cfg --- CentOS-7.0-1406-x86_64-NetInstall.mounted/isolinux/isolinux.cfg 2014-07-04 09:59:18.000000000 -0600 +++ iso_root/isolinux/isolinux.cfg 2015-04-06 15:17:27.737080861 -0600 @@ -61,7 +61,7 @@ label linux menu label ^Install CentOS 7 kernel vmlinuz - append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 quiet + append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=http://vr.vwh.net/files/ks/ks_minimal_centos_7.cfg label check menu label Test this ^media & install CentOS 7 # This is the exact same change I made from the grub interface. sudo mkisofs -b isolinux/isolinux.bin -boot-info-table -boot-load-size 4 -c isolinux/boot.cat -J -no-emul-boot -o minimal-centos-7.iso -R -T -v -V 'CentOS 7 x86_64' iso_root # Mount the newly created iso and compare files. I've edited out the lines that being with 2 because the 2 means they are identical and shouldn't cause a problem. sudo mkdir -p minimal-centos-7.mounted sudo mount -o loop minimal-centos-7.iso minimal-centos-7.mounted for d in *.mounted ; do cd $d ; find -printf "%3U %3G %#m %12s %p\n" ; cd .. ; done | sort | uniq -c | sort -nr $ bin/compare 2 0 0 0755 954752 ./EFI/BOOT/grubx64.efi ... 1 0 0 0644 3032 ./isolinux/isolinux.cfg 1 0 0 0644 2376 ./isolinux/isolinux.cfg So, the isolinux.cfg is the only file that differs, and that only in file size--which is to be expected. The first indication of something wrong when booting this iso in a vmware instance is that dracut-initqueue is trying to download something--or several somethings. But I can't figure out what. It gives no indication other than RTNETLINK answers: File exists, then the headers total, received xferd blah blah and numbers that only make sense if they are separate files. This takes between 5 and 10 minutes. Once that's done I get Warning: Could not boot. /dev/root does not exist and the Dracut emergency shell. If I remove the inst.stage2=hd:LABEL... from the cfg, everything is the same, except the kickstart file is downloaded and execution is started but I get errors about the xfs kernel module not being there. $ diff -u {CentOS-7.0-1406-x86_64-NetInstall.mounted,iso_root}/isolinux/isolinux.cfg --- CentOS-7.0-1406-x86_64-NetInstall.mounted/isolinux/isolinux.cfg 2014-07-04 09:59:18.000000000 -0600 +++ iso_root/isolinux/isolinux.cfg 2015-04-06 16:02:41.243204710 -0600 @@ -61,7 +61,7 @@ label linux menu label ^Install CentOS 7 kernel vmlinuz - append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 quiet + append initrd=initrd.img inst.ks=http://vr.vwh.net/files/ks/ks_minimal_centos_7.cfg label check menu label Test this ^media & install CentOS 7 The main screen shows a python stack dump, with the final line saying ValueError: new value non-existent xfs filesystem is not valid as a default fs type And the storage-log shows blivet trying to set new default type to xfs, could not load kernel module xfs. I'm not using xfs in my kickstart at all. I'm explicitly setting everything to --fstype=ext4 (excepting swap). Can anyone tell me what I'm doing wrong? -- Alan Young /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
