From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7580] New: Invalid filesystem in Pandaboard defconfig
Date: Thu, 30 Oct 2014 00:40:46 +0000 (UTC) [thread overview]
Message-ID: <bug-7580-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7580
Summary: Invalid filesystem in Pandaboard defconfig
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: spam+busybox at phyks.me
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hi,
I tried to build a disk image using the provided Pandaboard defconfig, but I
could not get the system to boot, due to a kernel panic.
Here is the line I got at boot :
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(179,2)
After the kernel saying that it tried only ext3 to mount the root filesystem.
However, the default root filesystem using the pandaboard defconfig is ext2.
I manually used tune2fs to get an ext3 partition for my root filesystem, and
everything boot up fine.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-10-30 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 0:40 bugzilla at busybox.net [this message]
2014-10-30 1:14 ` [Buildroot] [Bug 7580] Invalid filesystem in Pandaboard defconfig bugzilla at busybox.net
2014-11-07 7:27 ` bugzilla at busybox.net
2014-11-08 11:31 ` bugzilla at busybox.net
2014-11-09 13:23 ` bugzilla at busybox.net
2014-11-09 16:38 ` bugzilla at busybox.net
2014-11-10 9:17 ` bugzilla at busybox.net
2014-11-12 21:33 ` bugzilla at busybox.net
2014-11-12 21:34 ` bugzilla at busybox.net
2015-12-24 16:51 ` bugzilla at busybox.net
2015-12-25 17:32 ` bugzilla at busybox.net
2016-03-07 20:24 ` bugzilla at busybox.net
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=bug-7580-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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