rebuilding driver disk image with ext2 fs

Tom Georgoulias tgeorgoulias at nandomedia.com
Wed Dec 8 16:14:52 UTC 2004


Hello,

I'm new to the list and seem to have found a posting that addresses a 
problem I'm experiencing in getting my kickstart install to use an IBM 
driver disk from my kickstart server.   (I've included the contents of a 
previous email I posted to the taroon-list that describes my problem below.)

https://www.redhat.com/archives/kickstart-list/2004-November/msg00077.html
In that message, one of the recommended fixes is to rebuild the driver 
disk image with an ext2 fs.

According to the info in that thread, the driver disk on a network 
server needs to be in either iso9660, cramfs, or ext2 format.  The disk 
image I have appears to be in vfat:

-bash-2.05b$ file dud-rh30-9EL-megaide-v5.06i-generic-1.img
dud-rh30-9EL-megaide-v5.06i-generic-1.img: x86 boot sector, system 
mkdosfs, FAT (12 bit)

Can someone give some pointers on how to rebuild it so I can work around 
this bug?

Many thanks,

Tom

(message below previously posted to taroon-list at redhat.com)

I'm struggling to get the driverdisk option in my ks.cfg file to provide 
the megaide driver disk to my IBM blades.  From what I can tell, the 
disk image is not being loaded and the install fails cause it can't deal 
with the on-board RAID controller that mirrors the root disks.  Has 
anyone else done this successfully?

I'm doing an kickstart over HTTP and everything works just fine when I 
start the install using my boot floppy and this command:

linux ks=http://<ksserver>/kickstart/ks.cfg dd

then use my IBM provided megaide driver disk after being prompted to do so.

When I try to store this driver disk image on my kickstart server and 
point to it with this entry in my ks.cfg:

driverdisk --source=http://kickstart/driver_disks/megaide.img

I get this error:
-- 
No Drives Found
An error has occurred - No valid devices were found on which to create a 
new file systems.  Please check your hardware for the cause of this problem.
-- 

The syntax *seems* to be correct to me 'cause I followed this example 
from sec. 9.4 of the the RHEL3 SysAdmin guide:

"driverdisk --source=http://path/to/dd.img"

After the install fails, I switch over to the tty on F2 and run "lsmod." 
I can see that megaide.o is not loaded.  When I look around to see if it 
even got copied from the kickstart server to the client, I don't see it 
in tmp or tmp/drivers either.

Any ideas on what I'm doing wrong?  Or what I can do to get more info on 
where the process is breaking down?

Thanks in advance,
Tom




More information about the Kickstart-list mailing list