From: Erno Kuusela <erno@gulp.u--3.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: debian-arm@lists.debian.org, linux-mtd@lists.infradead.org
Subject: Re: UBIFS fails & crashes on SheevaPlug
Date: Fri, 24 Jul 2009 15:12:41 +0200 [thread overview]
Message-ID: <20090724131241.GC1792@gulp.u--3.com> (raw)
In-Reply-To: <4A694C3C.4010108@gmail.com>
On Fri, Jul 24, 2009 at 08:53:00AM +0300, Artem Bityutskiy wrote:
> On 07/23/2009 09:59 PM, erno@gulp.u--3.com wrote:
>> [ 191.690000] UBI error: ubi_io_write: error -5 while writing 512 bytes
>> to PEB 4051:512, written 0 bytes
>> [ 191.700000] UBI warning: ubi_eba_write_leb: failed to write VID
>> header to LEB 2147479551:0, PEB 4051
>> [ 191.710000] UBI warning: ubi_ro_mode: switch to read-only mode
>> [ 191.720000] UBI error: autoresize: cannot auto-resize volume 0
>
> http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail
Ah, ok. I did google for that error message but searching for
"ubi_io_write: error -5" doesn't yield anything useful for the first
screenful of results..
So workaround would be to disable CONFIG_MTD_NAND_VERIFY_WRITE or to
follow the "ignore sub pages" entry from the faq...
Indeed the latter seems to work, if I give --vid-hdr-offset 2048 option
to the ubinize, ubiformat & ubiattach commands. Thanks!
Maybe it would be better to disable the verify & subpages combo
until the bug is fixed? Especially since it crashes the kernel...
Also, ubiformat mentioned 1400+ "bad" eraseblocks, what should I make of
that? Is it really failed flash cells, just some blocks reserved for
u-boot and stuff, or blocks traumatized from my earlier misadventures
with ubiformat parameters?
Erno
next prev parent reply other threads:[~2009-07-24 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 18:59 UBIFS fails & crashes on SheevaPlug erno
2009-07-23 20:08 ` Adrian Hunter
2009-07-23 21:28 ` Corentin Chary
2009-07-23 21:52 ` erno
2009-07-24 5:53 ` Artem Bityutskiy
2009-07-24 13:12 ` Erno Kuusela [this message]
2009-07-24 14:38 ` Artem Bityutskiy
2009-07-26 15:35 ` Erno Kuusela
2009-08-09 4:56 ` Artem Bityutskiy
2009-07-26 11:07 ` Artem Bityutskiy
2009-07-24 21:00 ` Nicolas Pitre
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=20090724131241.GC1792@gulp.u--3.com \
--to=erno@gulp.u--3.com \
--cc=debian-arm@lists.debian.org \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@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 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.