Hi Colin,

Sorry for the delay in getting back to you. (I probably have to reply to
your first email separately to respond to the things you raise there...)

On Mon, 2006-02-27 at 11:40 +0000, Colin Turner wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Andree,
> 
> Further to my promises to run another test at work and report back, here
> is the breakdown
> 
> It is in the call to mindi where the whole thing falls over
> 
> > Calling MINDI to create boot+data disks Your boot loader is LILO and
> > it boots from /dev/hda /home/tmp.mondo.4420/tmp.mondo.31723 Mindi
> > failed to create your boot+data disks. ---promptpopup---1--- Fatal
> > error. Can't loopmount
> > /home/mondo.scratch.9854/mondo.scratch.10587/images/mindi-data-1.img
> > at
> > /home/tmp.mondo.4420/tmp.mondo.31723/mindilinux/23557/mountpoint.23557;
> > does your kernel support loopfs? If not, please recompile your
> > kernel. Your Linux distro is broken. ---promptpopup---Q--- [OK] --- 
> > -->
> 
> I have slightly modified the script here to show the image file it is
> trying to mount as well as the mountpoint.
> 
> There seems to be two problems here:
> 
> 1. The mount point does not exist
> 
> > einstein:/home/mondo.scratch.9854/mondo.scratch.10587/images# mount
> > -t ext2 -o loop mindi-data-1.img
> > /home/tmp.mondo.4420/tmp.mondo.31723/mindilinux/23557/mountpoint.23557
> >  mount: mount point
> > /home/tmp.mondo.4420/tmp.mondo.31723/mindilinux/23557/mountpoint.23557
> > does not exist
> 
> In fact nothing exists inside the mindilinux directory

Hm, mindi or mondoarchive would most likely have cleaned that up after
the failure.

> > einstein:~# ls -al /home/tmp.mondo.4420/tmp.mondo.31723/mindilinux/
> > total 12
> > drwxr-xr-x  2 root root  4096 2006-02-27 11:24 .
> > drwx------  4 root staff 8192 2006-02-27 11:24 ..
> 
> 2. Even when one tries to mount the image on a valid directory, it fails
> 
> > einstein:/home/mondo.scratch.9854/mondo.scratch.10587/images# mount -t ext2 
> > -o loop mindi-data-1.img /cdrom/
> > mount: wrong fs type, bad option, bad superblock on /dev/loop0,
> >        missing codepage or other error
> >        In some cases useful info is found in syslog - try
> >        dmesg | tail  or so
> 
> dmesg | tail produces
> 
> > VFS: Can't find an ext2 filesystem on dev loop0.
> > VFS: Can't find an ext2 filesystem on dev loop0.

Hm. In mondo-archive.log I see:

mke2fs: symbol lookup error: mke2fs: undefined symbol: e2p_os2string

Could you try calling mke2fs directly and see what happens? If that
works, could you try creating an ext2 filesystem (say by using a file
you creted with dd or something) with mke2fs?

> I attach the appropriate log file, but I'm aware that although this
> started as a mondo problem, this particular problem is mindi related,
> sorry :-(.
> 
> The logs also show a failure to insmod loop, strangely. But this
> 
> > einstein:~# insmod loop
> > insmod: can't read 'loop': No such file or directory
> > einstein:~# lsmod | grep loop
> > loop                   13704  0
> > einstein:~#
> 
> shows that the module is loaded at least.

Yep, insmod requires the full path to the kernel module file, e.g.
something like:

insmod /lib/modules/2.6.10-1-k7/kernel/drivers/block/loop.ko

One of the many items on my list of things to look into...

But so far I don't think that loop support is the problem here.

> CT.

Cheers,
Andree

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFEAuVK0SwfPjLnaZYRAgGkAKD5k1ZDtbHIiR55nNAyt1JrYKBNNgCePo5S
> shPWVqX82Wj6rn424LTYMb8=
> =STfv
> -----END PGP SIGNATURE-----
-- 
Andree Leidenfrost
Sydney - Australia

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to