From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: JFFS2 images written from U-Boot unusable in Linux? (Round 2)
Date: Mon, 10 Jan 2005 21:15:40 +0100 [thread overview]
Message-ID: <crunro$316$1@sea.gmane.org> (raw)
In-Reply-To: <crtfkb$6k4$1@sea.gmane.org>
Hi again,
New information entered the scene: I tried another (identical) board
today having none of the "Bad eraseblock" messages from my Linux kernel.
And then everything worked!
Hence, my boardsupplier suggested that U-Boot "ignored" these "Bad
eraseblock" that the NAND presumable was born with... What do you think?
BR,
Martin Egholm
>>>> # mount -t jffs2 /dev/mtdblock0 /mnt
>>>> jffs2: Erase block size too small (16KiB). Using virtual blocks size
>>>> (32KiB) instead
>>>> Cowardly refusing to erase blocks on filesystem with no valid JFFS2
>>>> nodes
>>>> empty_blocks 0, bad_blocks 5, c->nr_blocks 2048
>>>> mount: Mounting /dev/mtdblock0 on /mnt failed: Invalid argument
==== 8< 8< 8< ====
> But I'm getting some info from the Kernel at startup:
> Scanning device for bad blocks
> Bad eraseblock 1 at 0x00004000
> Bad eraseblock 2 at 0x00008000
> Bad eraseblock 3 at 0x0000c000
> Bad eraseblock 4 at 0x00010000
> Bad eraseblock 5 at 0x00014000
> Bad eraseblock 6 at 0x00018000
> Bad eraseblock 7 at 0x0001c000
> Bad eraseblock 1600 at 0x01900000
>>> I think it's not u-boot's fault -- u-boot is actually being better
>>> than the kernel about reading a damaged JFFS2 fs, where the kernel
>>> refuses to.
> Sounds resonable to assume yes - I just wondered whether U-Boot had some
> sophisticated way of writing the image to the nand, that required some
> specific kernel configuration.
next prev parent reply other threads:[~2005-01-10 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 11:00 [U-Boot-Users] JFFS2 images written from U-Boot unusable in Linux? (Round 2) Martin Egholm Nielsen
2005-01-09 17:03 ` Craig Hughes
2005-01-09 17:30 ` Allen Curtis
2005-01-09 18:32 ` Craig Hughes
2005-01-10 8:50 ` [U-Boot-Users] " Martin Egholm Nielsen
2005-01-10 20:15 ` Martin Egholm Nielsen [this message]
2005-01-12 12:29 ` Pantelis Antoniou
2005-01-12 13:46 ` Martin Egholm Nielsen
2005-02-16 7:35 ` Martin Egholm Nielsen
2005-02-16 9:34 ` Wolfgang Denk
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='crunro$316$1@sea.gmane.org' \
--to=martin@egholm-nielsen.dk \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.