From: amit.virdi@st.com (Amit Virdi)
To: linux-arm-kernel@lists.infradead.org
Subject: Need advice: unable to mount filesystem
Date: Thu, 14 Feb 2013 10:54:45 +0530 [thread overview]
Message-ID: <511C751D.9090404@st.com> (raw)
In-Reply-To: <CACRpkdb=zgaWkzoMtaWbMZXe_wUyszwsjmRC=03iMPDpU90N4w@mail.gmail.com>
On 2/13/2013 6:44 PM, Linus Walleij wrote:
> On Wed, Feb 13, 2013 at 1:29 PM, Amit Virdi<amit.virdi@st.com> wrote:
>
>> I have tried mounting the filesystem from DDR, that too with no success. One
>> observation is that before mounting the FS, the kernel throws a warning:
>> --
>> Warning: unable to open an initial console.
>
> This is not your problem. The kernel screams that all the time, (I once
> saw that explained and some ugly workaround for).
>
Okay.
> This (from your log) is the real problem:
>
> VFS: Cannot open root device "mtdblock3" or unknown-block(31,3): error -14
> Please append a correct "root=" boot option; here are the available partitions:
> 1f00 64 mtdblock0 (driver?)
> 1f01 192 mtdblock1 (driver?)
> 1f02 2048 mtdblock2 (driver?)
> 1f03 14080 mtdblock3 (driver?)
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)
> [<2000cb50>] (unwind_backtrace+0x0/0xf8) from [<2018655c>] (panic+0x8c/0x1d8)
> [<2018655c>] (panic+0x8c/0x1d8) from [<201f8d58>] (mount_block_root+0x1fc/0x2b8)
> [<201f8d58>] (mount_block_root+0x1fc/0x2b8) from [<201f90c0>]
> (prepare_namespace+0x160/0x1b8)
> [<201f90c0>] (prepare_namespace+0x160/0x1b8) from [<20185984>]
> (kernel_init+0x8/0xe4)
> [<20185984>] (kernel_init+0x8/0xe4) from [<20008e98>] (ret_from_fork+0x14/0x3c)
>
> The kernel cannot find a working filesystem at mtdblock3.
>
>> I have even tried using initramfs (compiled kernel with busybox binary).
>
> And how does the boot log look when you try to do that?
>
Almost the same:
---
Kernel command line: console=ttyAMA0,115200
<<snip>>
Warning: unable to open an initial console.
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -14
Please append a correct "root=" boot option; here are the available
partitions:
1f00 64 mtdblock0 (driver?)
1f01 192 mtdblock1 (driver?)
1f02 2048 mtdblock2 (driver?)
1f03 14080 mtdblock3 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[<2000cb50>] (unwind_backtrace+0x0/0xf8) from [<2018655c>]
(panic+0x8c/0x1d8)
[<2018655c>] (panic+0x8c/0x1d8) from [<201f8d60>]
(mount_block_root+0x1fc/0x2b8)
[<201f8d60>] (mount_block_root+0x1fc/0x2b8) from [<201f90c8>]
(prepare_namespace+0x160/0x1b8)
[<201f90c8>] (prepare_namespace+0x160/0x1b8) from [<20185984>]
(kernel_init+0x8/0xe4)
[<20185984>] (kernel_init+0x8/0xe4) from [<20008e98>]
(ret_from_fork+0x14/0x3c)
---
Regards
Amit Virdi
next prev parent reply other threads:[~2013-02-14 5:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 12:29 Need advice: unable to mount filesystem Amit Virdi
2013-02-13 13:14 ` Linus Walleij
2013-02-14 2:57 ` Anil Kumar
2013-02-14 5:34 ` Amit Virdi
2013-02-14 5:24 ` Amit Virdi [this message]
2013-02-14 9:36 ` Linus Walleij
2013-02-15 11:55 ` Amit Virdi
2013-10-16 5:25 ` Amit Virdi
[not found] ` <20131016082019.GA10079@pengutronix.de>
2013-10-21 11:29 ` copy from user broken on no-MMU (Was: Need advice: unable to mount filesystem) Amit Virdi
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=511C751D.9090404@st.com \
--to=amit.virdi@st.com \
--cc=linux-arm-kernel@lists.infradead.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).