Red Hat Bugzilla – Bug 496257
F11 Beta: anaconda cannot find kickstart file on hard disk whereas F10 does.
Last modified: 2010-01-20 13:48:34 EST
Description of problem:
Instead of playing the guessing game of where the usbkey is located. I put the kickstart file back on the hard drive. F11 Beta cannot find this file but F10 has no problem finding this file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create kickstart file and put on hard drive
2. pass location of kickstart file on kernel line
3. boot kernel
F11 Beta: cannot find kickstart file on hard drive
F10: finds the kickstart file.
finds the kickstart file
Are you positive that the USB drive is sdd1 when you do the install? Remember that device names are not guaranteed to be stable between reboots. Does using LABEL=<whatever> or UUID=<whatever> instead of sdd1 work better?
We didn't use the usbkey here. sdd1 is the /boot partition where we had placed the kickstart file in /boot/upgrade/ks.cfg. I'll try this using UUID.
I tried it like this:
ks=hd:UUID=<big id went here>:/upgrade/ks.cfg
and both of these failed as well.
I tried this just now from the rawhide boot.iso and it fails exactly the same there as well.
I tested the x86_64 rawhide boot.iso to be exact.
Created attachment 340189 [details]
Log for latest attempts
Created attachment 340190 [details]
Log of latest attempts
Comment on attachment 340190 [details]
Ok, ignore these logs. Judging from the timestamps on them they are from a year ago when the machine was still on F9.
I cannot find any other anaconda logs on the machine so maybe it isn't logging right with F10, F11-beta or the boot.iso disks.
This problem is still happening with both regular anaconda and with preupgrade. Whenever you try to pass the location of the kickstart file on the kernel line, anaconda refuses to find the file.
Is it possible you're passing too much stuff on your kernel command line, so the location of the kickstart file is getting trimmed down to something that doesn't work?
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
No, there's very little on the line except for the kickstart. Just root= and quiet rhgb. Even when you tried to edit the line in the anaconda screen, it still would not find the file.
I just saw this on a very different setup from what you're doing. I noticed that if I hit enter at the early dialog to change the kickstart location, it worked. This was reliably reproducable - it wouldn't find the kickstart file on USB the first time, but did after enter was hit.
Does this match up with what you're seeing?