Skip to contentSkip to conversation

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

DISCUSSION Jim McDonald 1 participant 1 message Feb 11, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 1013461497.806.501.camel@phantasy

#1 lore raw
Quoted 9 lines · Robert Love
Quoted 8 lines · 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:

Quoted 7 lines
Quoted 3 lines

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.

Quoted 1 line

Robert Love

Cheers,
Jim.

Signature · 1 line
Jim McDonald - [email protected]