 | | | driverdisk option in ks.cfg doesn 't load megaide driver disk | driverdisk option in ks.cfg doesn 't load megaide driver disk 2004-12-08 - By Tom Georgoulias
Back
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
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
Earn $52 per hosting referral at Lunarpages.
|
|
|