[wplug] Red Hat kmod: failed to exec /sbin/modprobe...

Vanco, Donald VANCOD at PIOS.com
Wed Aug 13 18:23:55 EDT 2003

mkinitrd options worth knowing:
-v = be verbose (it will tell you what it's pre-loading based on contents of
-f = force overwrite if target file (foo.img) exists
--ifneeded = won't do anything if all the required bits are already
monolithic in the kernel (a good idea)
There's also an option to force pre-load of a module if, for some reason
(like a unique but temporary hardware profile) you don't want a permanent
edit in modules.conf - pretty sure it's "--preload modulename1 modulename2"

-----Original Message----- 
From: Scott Eicher [mailto:Scott.Eicher at e-profile.com] 
Sent: Wed 8/13/2003 4:53 PM 
To: 'wplug at wplug.org' 
Subject: RE: [wplug] Red Hat kmod: failed to exec /sbin/modprobe...

That was it, 
I re-created the image using mkinitrd, rebooted and there it was!! 

Thanks guys 

-----Original Message----- 
From: Jonathan S Billings [mailto:billings at negate.org
<mailto:billings at negate.org> ] 
Sent: Wednesday, August 13, 2003 4:10 PM 
To: wplug at wplug.org 
Subject: Re: [wplug] Red Hat kmod: failed to exec /sbin/modprobe... 

Probably the problem is that the initrd isn't correct for the SMP 
kernels.  Boot into a working kernel, and run 'mkinitrd' for the 
appropriate kernel image.  For example: 

% mkinitrd /boot/initrd-2.4.21smp.img 2.4.21smp 

Make sure that the initrd you build is the one provided in the 
{lilo,grub}.conf.  Also, make sure that the kernel image name you use is 
the one for the SMP kernel you can't boot.  If the initrd image already 
exists, you may have to move it out of the way or use the -f (force) 
option to mkinitrd. 

If making a new initrd doesn't work, yet some kernels mount correctly, 
you'll have to take a look at what is defined in /etc/modules.conf as 
the SCSI and/or RAID controller. 

On Wed, 2003-08-13 at 15:54, Scott Eicher wrote: 
> I am receiving an error after installing Red Hat ES 2.1 on an IBM 
> Netfinity 6000R with dual 700mhz xeon processors and 1gb of ram in it. 
> I also have a hardware Raid 5 via IBM's ServeRAID. The error only 
> occurs when I choose to boot to the smp kernel. If I choose to boot to 
> the non-smp kernel it boots fine and I get to the root prompt. 
> Here is the error: 
> kmod: failed to exec /sbin/modprobe -s -k block-major -8 error=2 
> vfs cannot open root device "sda3" 
> please append correct "root=" boot option 
> kernel panic unable to mount root fs 
> I get this immediately after installing and rebooting. I'm going to 
> submit this to Red Hat as well but I think I'll get a faster answer 
> from wplug. 
> Thanks, 
> Scott 
Jonathan S Billings <billings at negate.org> 
TSFNKP, President and Chief Lackey 

wplug mailing list 
wplug at wplug.org 
wplug mailing list 
wplug at wplug.org 

More information about the wplug mailing list