[Celinux-dev] mount error when I mount ext2 block file in Ubuntu 6.06

[chenggh]

On Saturday 16 September 2006 00:04, Paolo Giarrusso wrote:
> On 9/15/06, chenggh <chenggh04 at st.lzu.edu.cn> wrote:
> > Hi, Everyone:
> >         In Ubuntu6.06 when I mount the ext2 block file there is something
> > wrong. It is like this:
> >
> >         root at fiasco-desktop:/home/fiasco/uml# mount -t ext2 -o loop
> > rootfs /mnt/ mount: wrong fs type, bad option, bad superblock on
> > /dev/loop0, missing codepage or other error
> >                 some cases useful info is found in syslog - try
> >                 dmesg | tail  or so
> >         root at fiasco-desktop:/home/fiasco/uml# dmesg | tail
> >         4294805.745000] loop: loaded (max 8 devices)
> >         [4295632.760000] VFS: Can't find an ext2 filesystem on dev loop2.
> >         [4295791.983000] VFS: Can't find an ext2 filesystem on dev loop0.
> >
> >         My host OS is Ubuntu6.06. I don't know why. Please help me.
>
> Post the output of "file rootfs" and of "mount -o loop rootfs /mnt/" -
> possibly (if that is indeed an ext2 fs) also "fsck rootfs" should be
> run when the fs is unmounted (possibly fsck -n, IIRC, to avoid doing
> changes and just check for errors).
	
root at fiasco-desktop:/home/fiasco/uml# ls
rootfs  vmlinux
root at fiasco-desktop:/home/fiasco/uml# file rootfs
rootfs: data
root at fiasco-desktop:/home/fiasco/uml# mount -o loop rootfs /mnt/
ioctl: LOOP_CLR_FD: Device or resource busy
mount: you must specify the filesystem type
root at fiasco-desktop:/home/fiasco/uml# fsck.ext2 rootfs
e2fsck 1.38 (30-Jun-2005)
rootfs is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Attempt to read block from filesystem resulted in short read while 
trying to open rootfs
Could this be a zero-length partition?
root at fiasco-desktop:/home/fiasco/uml# modprobe ext2
root at fiasco-desktop:/home/fiasco/uml# lsmod | grep ext2
ext2                   68360  0
root at fiasco-desktop:/home/fiasco/uml# mount -t ext2 -o loop rootfs /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

root at fiasco-desktop:/home/fiasco/uml# dmesg | tail
[4294704.633000] Bluetooth: HCI socket layer initialized
[4294704.718000] Bluetooth: L2CAP ver 2.8
[4294704.718000] Bluetooth: L2CAP socket layer initialized
[4294704.722000] Bluetooth: RFCOMM socket layer initialized
[4294704.723000] Bluetooth: RFCOMM TTY layer initialized
[4294704.723000] Bluetooth: RFCOMM ver 1.7
[4294972.320000] loop: loaded (max 8 devices)
[4294972.408000] VFS: Can't find an ext2 filesystem on dev loop0.
[4295061.397000] VFS: Can't find an ext2 filesystem on dev loop1.
[4295321.620000] VFS: Can't find an ext2 filesystem on dev loop1.

>
> Finally, "modprobe ext2" and "lsmod|grep ext2" to verify the loading
> should be done - if modprobe fails it means ext2 is compiled in or
> that you recompiled the kernel without ext2.
	
	Thank you
									chenggh