I wanted to MaKe and INITRD and you sent me to check out MKINITRD. How thoughtful... :-)
Kidding aside, I appreciate the suggestion. I checked it out and simply ran a 'mkinitrd --with=sata_sil /path/to/newinitrd <kernel>' and rebooted. When grub popped up, I edited the initrd line to reflect the new initrd. It worked like a charm. I've since updated the grub.conf permanently and everything works as expected when rebooted. Thanks again for the pointers. In the future, when upgrading the kernel, will future initrd's be built with my current modules or will I have to manually create new initrd's after each update? Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 ----- "nate" <[EMAIL PROTECTED]> wrote: > Tim Nelson wrote: > > > If my assumptions are correct, the onboard drives are detected > first, then > > the arrays assembled, and after the system has passed control from > the > > initrd to boot, THEN the addon controller is detected and hence the > third > > drive (sdc). If I am correct, then I need to update my initrd for > the system > > to see and use that third drive during the boot process. Can anyone > lend a > > few tips or pointers on how to proceed? I essentially need the > sata_sil > > driver to be included in the initrd. > > > Check the man page for mkinitrd, it's pretty self explanatory. I > suggest > you back up the existing initrd first, just in case there's a > problem. > > nate > > _______________________________________________ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
