All of your loopback devices are in use.
 

when i compiling kernel 2.6.1 and make bzImage and make modules went fine and no error
but when i wanted to make modules_install the 1st message i got is this and follows with other modules installatin modules name

Mutex destroy failure: Device or resource busy


then i make install i got this error.
its seems like mkinitrd is wrong right?

sh /usr/src/linux-2.6.1/arch/i386/boot/install.sh 2.6.1 arch/i386/boot/bzImage System.map ""
All of your loopback devices are in use.
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2

i tried to do this manually

# /sbin/mkinitrd /boot/initrd-2.6.1 2.6.1
All of your loopback devices are in use.

what is all loopback device are in use?
how to fix this?

"what is all loopback device are in use?
how to fix this?"

You can find out how many loopback devices you have with this command:
ls -l /dev/loop*

I have 15 loopback devices on my system and I have never run out. If you need more loopback devices you can create them with the mknod command.

Since you compile your own kernels be sure that loopback device support is enabled in your kernel compile.


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

there should be a devices.txt file somewere in the kernel source (i 4get were) it have the all the devices listed along with the numbers that the mknod comand needs, its been a while sence i usd it but it will be something like mknod c * * loop* (you expect me to remember the major and minor numbers for that deice?)

You also need to include loopback support into your kernel. Either as a module or in kernel:
CONFIG_BLK_DEV_LOOP=m

Example:
# sbin/mkinitrd /boot/initrd-2.6.1 2.6.1
WARNING: using /tmp for temporary files
All of your loopback devices are in use.
# /sbin/modprobe loop
# /sbin/mkinitrd /boot/initrd-2.6.1 2.6.1
WARNING: using /tmp for temporary files
# lsmod| grep loop
loop 17256 0

I have the same problem. Upgrading 2.4.22 kernel tom2.6 under Fedora core 1.
Everything goes smoothly until "make install" time

Any ideas ?

[root@localhost linux]# make install
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.5/arch/i386/boot/install.sh 2.6.5 arch/i386/boot/bzImage System.map ""
All of your loopback devices are in use.
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2
[root@localhost linux]# ls -l /dev/loop*
brw-rw---- 1 root disk 7, 0 Sep 15 2003 /dev/loop0
brw-rw---- 1 root disk 7, 1 Sep 15 2003 /dev/loop1
brw-rw---- 1 root disk 7, 10 Sep 15 2003 /dev/loop10
brw-rw---- 1 root disk 7, 11 Sep 15 2003 /dev/loop11
brw-rw---- 1 root disk 7, 12 Sep 15 2003 /dev/loop12
brw-rw---- 1 root disk 7, 13 Sep 15 2003 /dev/loop13
brw-rw---- 1 root disk 7, 14 Sep 15 2003 /dev/loop14
brw-rw---- 1 root disk 7, 15 Sep 15 2003 /dev/loop15
brw-rw---- 1 root disk 7, 2 Sep 15 2003 /dev/loop2
brw-rw---- 1 root disk 7, 3 Sep 15 2003 /dev/loop3
brw-rw---- 1 root disk 7, 4 Sep 15 2003 /dev/loop4
brw-rw---- 1 root disk 7, 5 Sep 15 2003 /dev/loop5
brw-rw---- 1 root disk 7, 6 Sep 15 2003 /dev/loop6
brw-rw---- 1 root disk 7, 7 Sep 15 2003 /dev/loop7
brw-rw---- 1 root disk 7, 8 Sep 15 2003 /dev/loop8
brw-rw---- 1 root disk 7, 9 Sep 15 2003 /dev/loop9

I followed the 2.6 instructions at http://www.linuxquestions.org/questi...threadid=73436

vmlinuz and System.map are created in /boot but there is no initrd-2.6.5.img

I still get the same error using either of the 2 commands below
<<<<<<<<<command 1>>>>>>>>
[root@localhost linux]# /sbin/mkinitrd /boot/initrd-2.6.5.img 2.6.5
All of your loopback devices are in use

<<<<< command 2>>>>>>>>>>>
[root@localhost linux]# make install
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.5/arch/i386/boot/install.sh 2.6.5 arch/i386/boot/bzImage System.map ""
All of your loopback devices are in use.
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2

Check the permissions and mount options on /tmp. I caused this problem for myself with the following. "nodev" is generally a good idea for security, but it prevents mkinitrd from working.

none /tmp tmpfs nosuid,mode=1777,nodev 0 0

While all the above suggestions may work in different situations, I found that this problem was fixed for me by simply re-enabling autofs in system-config-services, or with "/sbin/service autofs restart" when compiling kernel 2.6.7

Simply try exiting the kernel you're in and using a different kernel version. I was upgrading my 2.4.22 kernel while using my 2.4.22 kernel and then I rebooted into 2.4.20 kernel and recompiled the kernel and everything worked fine. Hope this works, it's way easier than the other solutions.

PEACE
KAN