"All of your loopback devices are in use!" reported by mkinitrd

"All of your loopback devices are in use!" reported by mkinitrd

[Al Moote]

Hey all.  I am not-so new to Linux, but I haven't had to recompile my kernel before.  We are taking the leap into Samba Fileserving an thus, I need to add ACL functionality to my kernel.  I have opted to go with 2.4.17 and have had some success so far.  I am, however, stuck at one point.

I am trying to make my .img file to support my RAID devices.  When I run:

/sbin/mkinitrd /boot/initrd-2.4.17-021102.img 2.4.17-021102

I get the message:

All of your loopback devices are in use!

I don't really understand why this is preventing me from creatingthe .img file.  But then again, I have little experience in this area.  I was hoping somebody on this list could len a hand.  Thanks alot guys (and the occasional gal).

Al Moote

Re: "All of your loopback devices are in use!" reported by mkinitrd

[Jim McDonald]

On Mon, 2002-02-11 at 21:04, Robert Love wrote:
> On Mon, 2002-02-11 at 15:59, Al Moote wrote:
> > Hey all.  I am not-so new to Linux, but I haven't had to recompile my kernel before.  We are taking the leap into Samba Fileserving an thus, I need to add ACL functionality to my kernel.  I have opted to go with 2.4.17 and have had some success so far.  I am, however, stuck at one point.
> > 
> > I am trying to make my .img file to support my RAID devices.  When I run:
> > 
> > /sbin/mkinitrd /boot/initrd-2.4.17-021102.img 2.4.17-021102
> > 
> > I get the message:
> > 
> > All of your loopback devices are in use!
> > 
> > I don't really understand why this is preventing me from creatingthe .img file.  But then again, I have little experience in this area.  I was hoping somebody on this list could len a hand.  Thanks alot guys (and the occasional gal).
> 
> You need loopback support in your kernel, and you probably don't?
> 
> Enable CONFIG_BLK_DEV_LOOP (see Block Devices in configure).

Either that or you've compiled loopback devices directly in to the
kernel this time around, they were modules last time around, and you
have kept the same kernel name.  If you do this the make modules_install
blasts the module from the /lib/modules/2.4.xx and a subsequent mkinitrd
can't load the loopback module.  Check out dmesg to see if this is the
problem.

> 	Robert Love

Cheers,
Jim.
-- 
Jim McDonald - Jim@mcdee.net