From: Callebaut Benoit <callebaut@mailandnews.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re : Can't find ext2 filesystem on dev mtdblock
Date: Thu, 15 May 2003 08:13:42 -0400 [thread overview]
Message-ID: <3EC6FB62@mailandnews.com> (raw)
Hi,
> I am getting following error while mounting the filesystem.
>I am using ppcboot and linux-2.4.18 . The same filesystem was earlier
>working for linux-2.2.14.
>
>=========================================================
> VFS: Can't find ext2 filesystem on dev mtdblock(31,0)
>=========================================================
>
>What has gone wrong??
I don't know precisely what changed between the two kernels but I use ppcboot
and a 2.4.17 based kernel. So I will try to help you.
First it is strange that you use a ext2 filesystem on a flash. A better choice
would be CRAMFS (READ ONLY) or JFFS. And pay attention that the write support
to the flash is not full proof (experrimental status). So first check that
your filesystem valid is.
Second remarks : Do you try to mount this as root filesystem or not (I don't
think so). But such a line doesn't say a lot of the possible problem.
So first check the filesystem integrity (with fschk or a probe)
Two check that you can access your flash with a character driver(/dev/mtd0) in
case of a bad setting in the kernel (FLASH base address change)
Third give more informations like a full syslog or even better look directly
in the log_bu buffer in RAM (buffer where all the printk text is placed before
writing it to syslog).
Fourth : use a probe, GDB and debug your kernel.
Good luck,
Benoit Callebaut
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-05-15 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 12:13 Callebaut Benoit [this message]
2003-05-15 12:51 ` Re : Can't find ext2 filesystem on dev mtdblock Anil Giri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EC6FB62@mailandnews.com \
--to=callebaut@mailandnews.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).