initrd.img module loading

[Ronald Reed]

I can make it work with the workarounds that have been presented. I have
to change the install so that it installs to sdb and then does Pete
Eisch's steps to create a new initrd that will move sdb to sda. But it
all seems like such a pain step to have to invoke when you should be
able to specify the devices in the kickstart file and have it follow
them.

I would like to thank everyone who has responded to my problem.

Ron

On Thu, 2005-03-03 at 16:44, Edward F. Brown wrote:
> Is there a particular reason "sda' has to be assigned to this drive?  I
> understand that it would be great if linux allowed more determination over
> drive letter assignments, I've wrestled with this too.  But is there an
> issue for which a workaround hasn't been suggested?
> 
> -Ed
> 
> 
> > I created a new initrd and tried to use it as part of the install. But
> > this didn't work. I understand what your steps are doing, but that
> > doesn't work for what I need.
> >
> > I have to make sure that the aacraid module gets loaded first so that it
> > will be sda. Your ideal works, but it is after the fact, which means
> > that if I do it in the %post like you said, the machine would not be
> > bootable, since the drives that were attached to the megaraid card were
> > formated and setup as the root device and the new initrd will load the
> > aacraid first, which will having nothing on it.
> >
> > Ron
> >
> > On Tue, 2005-02-22 at 13:39, Peter Eisch wrote:
> >> Did you try rebuilding the initrd.img using something like:
> >>
> >> /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with aacraid \
> >>     --with megaraid --with aic7xxx --with eepro100 --with bcm5700 \
> >>        /boot/ninitrd-%{KVERREL}.img %{KVERREL}
> >> /bin/mv /boot/initrd-%{KVERREL}.img /boot/oinitrd-%{KVERREL}.img
> >> /bin/mv /boot/ninitrd-%{KVERREL}.img /boot/initrd-%{KVERREL}.img
> >>
> >> I put this in my kernel's %post so it gets done at boot, but do the same
> >> kind of thing with the initrd.img on the install media.
> >>
> >> peter
> >>
> >> On 2/22/05 12:38 PM, "Ronald Reed" <rreed at ops.sgp.arm.gov> wrote:
> >>
> >> > I have found that the scsihosts= boot line command is only for kernels
> >> > that have the modules built into the kernel, but no other resolution
> >> has
> >> > been found.
> >> >
> >> > I have tried the device parameter in the kickstart file, but anaconda
> >> > seems to ignore them. Anyone have any other ideals? Here is a portion
> >> of
> >> > my kickstart file:
> >> >
> >> > #kickstart file (partial)
> >> > install
> >> > cdrom
> >> > lang en_US.UTF-8
> >> > langsupport --default en_US.UTF-8 en_US.UTF-8
> >> > device scsi aacraid
> >> > device scsi megaraid
> >> > device scsi aic7xxx
> >> > device eth eepro100
> >> > device eth bcm5700
> >> > keyboard us
> >> > mouse genericwheelps/2 --device psaux
> >> > skipx
> >> > network --device eth0 --bootproto dhcp --hostname nfs-basic
> >> >
> >> > Ron
> >> >
> >> > On Tue, 2005-02-08 at 12:27, Ronald Reed wrote:
> >> >> No, I need the drive letter assignments to be different.
> >> >>
> >> >> Ron
> >> >>
> >> >> On Tue, 2005-02-08 at 11:58, Ed Brown wrote:
> >> >>> The --driveorder option won't change the drive letter assignments,
> >> but
> >> >>> it will change the drive that grub is installed to.  Isn't that what
> >> you
> >> >>> are after?  In your case, you probably want:
> >> >>>
> >> >>> bootloader --driveorder=sdb,sda --location=mbr
> >> >>>
> >> >>> -Ed
> >> >>>
> >> >>>
> >> >>> On Tue, 2005-02-08 at 10:53, Ronald Reed wrote:
> >> >>>> Yes, the aacraid device get set to /dev/sdb. The accraid device is
> >> a
> >> >>>> mirrored pair of 36GB drives that are inside the hardware. The
> >> megaraid
> >> >>>> device is a Raid 5 group of 4 73GB drives (3 in the array, and 1
> >> hot
> >> >>>> spare). The megaraid is to be used for NFS file storage and the
> >> accraid
> >> >>>> is to be used for the system drive.
> >> >>>>
> >> >>>> Ron
> >> >>>>
> >> >>>> On Tue, 2005-02-08 at 11:47, Brian Long wrote:
> >> >>>>
> >> >>>>> What does it detect the aacraid device as?  /dev/sdb?  If so, why
> >> don't
> >> >>>>> you use the bootloader option mentioned previously to get grub to
> >> use
> >> >>>>> sdb as the boot drive?
> >> >>>>>
> >> >>>>> /Brian/
> >> >>>
> >> >>> _______________________________________________
> >> >>> Kickstart-list mailing list
> >> >>> Kickstart-list at redhat.com
> >> >>> https://www.redhat.com/mailman/listinfo/kickstart-list
> >>
> >> _______________________________________________
> >> Kickstart-list mailing list
> >> Kickstart-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/kickstart-list
> > --
> > ===========================
> > Ron Reed
> > RedHat Certified Engineer
> > SGP Computer Department Manager
> > Unix Systems Administrator
> > ARM SGP CART Site
> > (580)388-4053
> > ron.reed at arm.gov
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/kickstart-list
> >
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
-- 
===========================
Ron Reed
RedHat Certified Engineer
SGP Computer Department Manager
Unix Systems Administrator
ARM SGP CART Site
(580)388-4053
ron.reed at arm.gov