Bug 167009
Summary: | Kickstart: Unable to kickstart with ks.cfg file stored on USB drive. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | W Agtail <crash70> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-19 17:55:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
W Agtail
2005-08-29 15:43:16 UTC
The kernel recognizes sda1? If you manually switch to tty2, is /dev/sda1 present and can you access the ks.cfg? I'm not sure what you mean? tty2 ? The kickstart procedure does not get as far as starting a shell. Do you have a procedure on how I could to this? Kickstart stops at "Choose a Language" screen on Alt,F1 screen. I have also noticed that usb-storage module gets loaded twice, so I'm just wondering if this could be a timing issue? Is Anaconda looking for ks.cfg before the usb-storage module has loaded and detected storage device /dev/sda ? Thanks again Yes, continue on by manually putting in where your install source is so that you can get to the shell and try to figure out what's going on. It's entirely likely that your usb-storage device isn't actually sda and is something later. Hi, thanks I continued on up until the "NFS Setup" screen and entered the BFS details. Shortly afterwards I was then able to locate a shell on Alt,F2. I was then able to: a) mkdir /mnt/a b) mount /dev/sda1 /mnt/a c) cd /mnt/a d) more ks.cfg to confirm access to ks.cfg file. Alt,F4 displayed references for sda, sdb, sdc & sdd, so I also tried installing Linux via kickstart using these devices (plus sde for good measure). e.g: linux ks=hd:sdd1:/ks.cfg Any other ideas? thanks again Actually, it looks like this is something that's gotten fixed since FC4. If you format the whole device (sda) with an fs instead of doing a partition it should work. |