From: JNY <jny0@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] EXT2-fs error
Date: Thu, 2 Sep 2010 04:17:36 -0700 (PDT) [thread overview]
Message-ID: <29603102.post@talk.nabble.com> (raw)
In-Reply-To: <878w3lx010.fsf@macbook.be.48ers.dk>
Why don't you just check the image before writing (E.G. on your build
machine)?
/sbin/e2fsck -f output/images/rootfs.ext2
e2fsck 1.41.9 (22-Aug-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs.ext2: 502/896 files (0.4% non-contiguous), 1453/3744 blocks
If the image is OK, then I guess your problem is either in the copying
or some I/O issue on your flash disk.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
I don't have a file called rootfs.ext2. I have the following files:
bzImage
rootfs.i486.tar
rootfs.i486.tar.bz2
If I try to /sbin/e2fsck -f output/images/ any of those, I get:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Which is pretty much what I'd have expected, as they're mounted files. What
am I doing wrong.
--
View this message in context: http://old.nabble.com/EXT2-fs-error-tp29591683p29603102.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-09-02 11:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 9:35 [Buildroot] EXT2-fs error JNY
2010-09-01 9:53 ` Peter Korsgaard
2010-09-02 11:17 ` JNY [this message]
2010-09-03 5:56 ` Mitch Davis
2010-09-03 5:57 ` Mitch Davis
2010-09-07 16:58 ` JNY
2010-09-07 23:57 ` Mitch Davis
2010-09-08 8:31 ` JNY
2010-09-09 12:35 ` Johnny Beardsmore
2010-09-10 15:41 ` Johnny Beardsmore
2010-09-10 16:12 ` Johnny Beardsmore
2010-09-10 16:16 ` Yann E. MORIN
2010-09-13 7:51 ` Johnny Beardsmore
2010-09-13 8:20 ` Thomas Petazzoni
2010-09-13 8:45 ` Johnny Beardsmore
2010-09-13 9:22 ` Peter Korsgaard
2010-09-15 11:07 ` Johnny Beardsmore
2010-09-15 11:31 ` Thomas Petazzoni
2010-09-15 12:39 ` Johnny Beardsmore
2010-09-15 13:28 ` Malte Starostik
2010-09-15 17:07 ` Thomas Petazzoni
2010-09-16 6:50 ` Johnny Beardsmore
2010-09-16 7:01 ` [Buildroot] FW: " Johnny Beardsmore
2010-09-16 8:51 ` [Buildroot] " Ormund Williams
2010-09-16 9:21 ` Johnny Beardsmore
[not found] ` <AANLkTinbDS1nrt4b6TgctMwHArtwrX7_JSrzbeqxWCn=@mail.gmail.com>
2010-09-16 10:11 ` Johnny Beardsmore
2010-09-16 10:14 ` Mitch Davis
[not found] ` <233D327176C4471A9A40B36BC1B4EB35@AP366>
2010-09-16 11:14 ` Johnny Beardsmore
2010-09-16 11:57 ` Mitch Davis
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=29603102.post@talk.nabble.com \
--to=jny0@hotmail.com \
--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