Description of problem:
Attempt kickstart off disk, with USB disk as the source media, IDE
disk as target install. USB disk has RHEL3 Update 3 both in iso
format, as well as expanded directory layout in the target directory
of the partition. Kickstart file on floppy. Boot off a RHEL3 Update 3
boot.iso, with usb disk plugged in. installer sees usb, and loads
usb-storage module. goes to start X. but instead gives a fatal dump
screen, saying "this is probably a bug". anaconda.txt dump, syslog,
and ks.cfg files are attached.
Version-Release number of selected component (if applicable):
RHEL 3, Update 3
Every single time.
Steps to Reproduce:
1. Burn RHEL3.3 boot.iso
2. get a usb disk, partition it, and copy RHEL3 to a partition, as per
3. copy attached ks.cfg file to msdos floppy.
4. boot boot.iso with command "linux ks=floppy"
5. sit back, relax, and observe kernel loading, usb-storage modukle
loading, and instead of X starting for install, an anaconda crash dump
will come up!
unable to kick-start install off usb disk.
able to kick start install using usb hard drive.
note: normal install using usb hard drive works just fine.
Created attachment 105105 [details]
anaconda dump file
Created attachment 105106 [details]
syslog from anaconda
Created attachment 105107 [details]
note: you will likely have to change the path to match the RHEL3 location in
the partition that you create on YOUR usb hard disk!
Backported fix from HEAD to rhel3 branch.
what does that mean to me, if I wish to kickstart machines with a USB
disk ? (e.g. I looked in rawhide, but the RHEL binaries aren't (and
I'm pretty sure, won't, be :) there!
I'm an RHCX, and I need to rebuild server1 machines on a fairly
I'd be appreciative of any suggestions as to how I might achieve this.
It looks like I just need a new 'loader' put that into the initrd, and
then make a new boot.iso, or a bootdisk.img, yes ?
(if yes, might I know, please, how might I generate a new 'loader' and
a new boot.iso ? :)
thanks, and best rgds,
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.