On Sun, Jul 12, 2015 at 1:33 PM, dwoody5654 dwoody5654@gmail.com wrote:
I created a menu entry in the current F20 grub.cfg with menu_entry name of 'Remote Install'. So I boot to the netinstall from F20.
OK now I'm lost on the advantage of modifying the current bootloader to do this, rather than boot from either Fedora 21 netinstall media, or boot.fedoraproject.org media.
This has been working up until the current issue. The 2 pertinent lines are: linux /boot/vmlinuz-remote repo=hd:md126:/david/Fedora-Server-netinst-i386-21.iso noselinux ks.device=00:14:6c:55:f1:85 ks=hd:md126:/david/ks.cfg --noip6 ramdisk_size=8192 panic=30 initrd /boot/initrd-remote.img
I've never seen this kind of notation before, and I don't see a root=UUID= line so it seems like systemd is going to have no idea what volume to mount as root fs.
What are vmlinuz-remote and initrd-remote.img? set root='hd0,msdos1' is telling GRUB that those files are local, on the primary drive's first partition. So where did they come from?
A particular Fedora installer version expects a particular environment setup by a precreated initramfs which is on the netinstall.
I thought noselinux was deprecated a long time ago in favor of selinux=0 or enforcing=0, with the latter being preferred since it still labels files correctly.
The set root line is what I think I do not have set correctly. The /dev/root error comes up during the initial netinstall boot up.
The set root line in the grub.cfg tells GRUB where the kernel and initramfs are located. That's it. Obviously it found /boot/vmlinuz-remote and /boot/initrd-remote.img or the system wouldn't have gotten to dracut. So it did exactly what you asked it to do. I just don't know why you're booting the system this way instead of using install media written to a USB stick or pxeboot or something.
The file rdsosreport.txt is below.
It looks really short, I'm expecting a lot more data including journal entries and there are none.
Chris Murphy