Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: JNY <jny0@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] EXT2-fs error
Date: Tue, 7 Sep 2010 09:58:21 -0700 (PDT)	[thread overview]
Message-ID: <29641601.post@talk.nabble.com> (raw)
In-Reply-To: <29591683.post@talk.nabble.com>


> Out of curiosity, a USB flash device, or CF, or NAND flash, or ?

Not sure about the USB stick, but the flash device (see below) on the target
is NAND.

To clear up any confusion: 
-USB stick is the means of transfering the image
-flash device is the target device memory

>> I don't have a file called rootfs.ext2.  I have the following files:
>> rootfs.i486.tar
>> rootfs.i486.tar.bz2

>Which of these files are you transferring to the flash device, and how?
I'm transfering the bzImage file to the flash device, and referencing it
with grub.

The USB stick always comes up clean when I e2fsck both partitions (even with
a force -f).

Is it possible that when the file system is created by Buildroot, that it
could need some kind of fsck, before it is transfered to the USB stick?


-- 
View this message in context: http://old.nabble.com/EXT2-fs-error-tp29591683p29641601.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

  parent reply	other threads:[~2010-09-07 16:58 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
2010-09-03  5:56 ` Mitch Davis
2010-09-03  5:57   ` Mitch Davis
2010-09-07 16:58 ` JNY [this message]
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=29641601.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