From: Timon ter Braak <timonterbraak@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Re: ubiattach error!
Date: Fri, 20 May 2011 14:14:37 +0000 (UTC) [thread overview]
Message-ID: <loom.20110520T161007-38@post.gmane.org> (raw)
In-Reply-To: 1270715032.6754.108.camel@localhost
Artem Bityutskiy <dedekind1 <at> gmail.com> writes:
>
> > # ubiattach /dev/ubi_ctrl -m 3
> > UBI: attaching mtd3 to ubi0
> > UBI: physical eraseblock size: 524288 bytes (512 KiB)
> > UBI: logical eraseblock size: 516096 bytes
> > UBI: smallest flash I/O unit: 4096
> > UBI: VID header offset: 4096 (aligned 4096)
> > UBI: data offset: 8192
> > UBI error: ubi_scan_add_used: two LEBs with same sequence number 4
> > ubiattach: error!: cannot attach mtd3
> > error 22 (Invalid argument)
>
> Looks weird, is this reproducible with nandsim?
>
After a power cut / reset, we experience similar problems.
I just upgraded to linux 2.6.39 as more and more UBIFS 'bugs' seem to get solved.
Unfortunately, we use a Spansion GL512P (64MB) NOR Flash chip,
which makes life kind of hard:
[ 0.510000] UBI: attaching mtd1 to ubi0
[ 0.510000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 0.520000] UBI: logical eraseblock size: 130944 bytes
[ 0.530000] UBI: smallest flash I/O unit: 1
[ 0.530000] UBI: VID header offset: 64 (aligned 64)
[ 0.540000] UBI: data offset: 128
[ 0.540000] UBI error: ubi_scan_add_used: two LEBs with same sequence number 9
[ 0.550000] UBI error: ubi_init: cannot attach mtd1
next prev parent reply other threads:[~2011-05-20 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:26 ubiattach error! jerry
2010-04-08 8:23 ` Artem Bityutskiy
2011-05-20 14:14 ` Timon ter Braak [this message]
2011-05-20 14:23 ` Artem Bityutskiy
2011-05-20 16:24 ` Timon ter Braak
2011-05-23 12:42 ` Artem Bityutskiy
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=loom.20110520T161007-38@post.gmane.org \
--to=timonterbraak@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.