Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 45014

Summary: genkernel 3.0.1 linuxrc error (losetup parameters reversed)
Product: Gentoo Linux Reporter: Everett Haimes <everett>
Component: Current packagesAssignee: Gentoo Genkernel Maintainers <genkernel>
Status: RESOLVED NEEDINFO    
Severity: major    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Everett Haimes 2004-03-18 05:13:25 UTC
When building a new livecd with catalyst, losetup fails so mounting the loopback device won't work.  Hence, the LiveCD won't boot.

I found the problem to be in genkernel (3.0.1) generic/linuxrc.
/usr/share/genkernel/generic/linuxrc at line 243

echo " " | losetup -E 19 -e ucl-0 -p0 /newroot/dev/loop0 /newroot/mnt/cdrom/${LOOP}

echo " " | losetup -E 19 -e ucl-0 -p0 /newroot/mnt/cdrom/${LOOP} /newroot/dev/loop0

The last two parameters are reversed and the command fails.


Reproducible: Always
Steps to Reproduce:
1. Build LiveCD with Catalyst (gentoo-dev-sources-2.6.4-r1)
2. Boot to LiveCD

Actual Results:  
losetup command fails.
Loopback filesystem will not mount.

Expected Results:  
losetup complete, mount successful.
Comment 1 Everett Haimes 2004-03-18 09:56:20 UTC
Sorry, the losetup command seems is fine.
Here is the error I'm having:

Step 51a: mount gcloop (ext2) filesystem
modprobe gentoo script v1.0
Usage:
  modprobe moduleprefix

Ex: modprobe eepro100

Note: Do not pass the suffix to modprobe
losetup: ioctl: LOOP_SET_STATUS: Invalid argument
FAILED TO losetup THE LOOP DEVICE

BusyBox v1.00-pre7 (2004.03.18-10:29+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/ash: can't access tty; job control turned off

Comment 2 Tim Yamin (RETIRED) gentoo-dev 2004-03-20 15:37:57 UTC
Can you please attach your kernel config - also, what cipher did you use for the loopback?
Comment 3 Tim Yamin (RETIRED) gentoo-dev 2004-06-12 15:09:08 UTC
Closing due to inactivity. Please reopen this bug if you still experience this issue with genkernel-3.0.2b: we encountered this on 2.4 series kernels and this issue should now be fixed in that release.