Description of problem: Probably the same issue as #802042. Procedure that works for Fedora 16 fails for Fedora 17 Beta, at least on Dell R610 (Intel x86_64). Version-Release number of selected component (if applicable): Fedora 17-Beta as of 4/22/2012 How reproducible: Always Actual results: Loading times out to Boot failed Expected results: Installation
Not sure why this got assigned to me. Bill do you have any idea where to assign this? Should it also go to Lorax?
I am also getting this issue. Same procedure I've been using for booting Fedora 14/15 installs as well as RHEL/CentOS installs fails for the beta. How reproducible: Always Actual results: After udevd renames network interfaces, drops to debug shell. After pausing a few seconds after renaming interfaces, I get the following: [ 28.774194] dracut Warning: Unable to process initqueue [ 28.774833] dracut Warning: /dev/root deos not exist Dropping to debug shell. dracut:/# Expected results: Booting into Anaconda for install.
Created attachment 580221 [details] Result of PXE boot attempt.
Yeah, this is a usability nightmare. I usually just grab the vmlinuz + install.img, put it into /boot/, edit grub.conf and reboot. Why can't it e.g. hardcode the https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch path if root is not specified, fetch that, and pick up squashfs.img from some mirror given by that?
I get this too. Once at the dracut prompt, is there a workaround? Or is PXE boot just out of the question for now?
Getting the exact same behaviour with the full release of 17. Looking for a fix.
can you add "rd.shell rd.debug" to the kernel command line and then you are dropped to a dracut shell. mount /boot or a USB stick manually and save "/run/initramfs/init.log". Then attach this file here in the bugzilla.
Created attachment 591208 [details] init.log from Fedora 17 x86_64 PXE boot I have attached an init.log, as requested, from a Fedora 17 (GA release) x86_64 PXE boot done by a KVM guest. The md5sums and file info on the kernel and initrd are as follows: cbf35f7052fd9c315e821898a860c1be initrd.img 5265c3296c7b262c9e3ce61bacac08e5 vmlinuz -rw-r--r--. 2 root root 24337760 May 22 16:55 initrd.img -rwxr-xr-x. 2 root root 4662160 May 7 13:35 vmlinuz They were retrieved out of the directory releases/17/Fedora/x86_64/os/images/pxeboot of a Fedora mirror server located at rsync://fedora.mirrors.tds.net/fedora-enchilada just as I had similarly done with Fedora 16, and not had any issue. If there is any other information needed, please let me know.
I don't see any BOOTIF given on the kernel command line, which is normally given by the PXE loader. To workaround that add "ip=dhcp" to the kernel command line
Created attachment 591231 [details] init.log from Fedora 17 x86_64 with ip=dhcp added Sorry. The additional parameters did not improve the situation. Still drops out at the same point.
I was having the same issue tonight, but was able to resolve it by modifying the append options in my pixie boot to this. "append ksdevice=link initrd=/kernels/f17_i386/initrd.img repo=nfs:<NFS server IPL>:/a/" The "repo" option just needs to be set and pointing to a legit repository. In my case its an nfs export containing the the install media. Hope that helps. See here for more details: http://docs.fedoraproject.org/en-US/Fedora/17/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html
Feeling very embarrassed for not checking the Release Notes. Thanks, Dan. Fixed the problem immediately. I added a stage2= and everything's working. Sorry for the trouble, and hope it fixes the folks who were trying to do the Beta builds.