From: Lars Michael <lh_post@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: mount ubi volume fails: No such device
Date: Wed, 9 Feb 2011 00:32:34 -0800 (PST) [thread overview]
Message-ID: <421430.70003.qm@web30207.mail.mud.yahoo.com> (raw)
> On Mon, 2011-02-07 at 07:05 -0800, Lars Michael wrote:
> > UBI: scrubbed PEB 863, data moved to PEB 1097 UBI warning:
> ubi_eba_copy_leb: read data back from PEB 1092 and it is different UBI
> error: wear_leveling_worker: error -22 while moving PEB 868 to PEB 1092
> UBI warning: ubi_ro_mode: switch to read-only mode UBI error: do_work:
> work failed with error code -22 UBI error: ubi_thread: ubi_bgt0d: work
> failed with error code -22
>
> It says you that it wrote some date, then read it back, compared, and
> the data did not match. You need to start with validating your falash
> drivers - use mtd tests:
>
> http://www.linux-mtd.infradead.org/doc/general.html#L_mtd_tests
>
The speedtest, stresstest, readtest, pagetest ran ok, but showing 1 bad eraseblock. I guess that is acceptable?
The oobtest and subpagetest found 3 errors, see below. Does it explain
my initial problem?
=================================================
mtd_oobtest: MTD device: 0
mtd_oobtest: MTD device size 1048576, eraseblock size 131072, page size 2048, count of eraseblocks 8, pages per eraseblock 64, OOB size 64
mtd_oobtest: scanning for bad eraseblocks
mtd_oobtest: block 0 is bad
mtd_oobtest: scanned 8 eraseblocks, 1 are bad
mtd_oobtest: test 1 of 5
mtd_oobtest: erasing whole device
mtd_oobtest: erased 8 eraseblocks
mtd_oobtest: writing OOBs of whole device
mtd_oobtest: written 8 eraseblocks
mtd_oobtest: verifying all eraseblocks
mtd_oobtest: error: verify failed at 0xa0000
mtd_oobtest: verified 8 eraseblocks
mtd_oobtest: test 2 of 5
mtd_oobtest: erasing whole device
mtd_oobtest: erased 8 eraseblocks
mtd_oobtest: writing OOBs of whole device
mtd_oobtest: written 8 eraseblocks
mtd_oobtest: verifying all eraseblocks
mtd_oobtest: verified 8 eraseblocks
mtd_oobtest: test 3 of 5
mtd_oobtest: erasing whole device
mtd_oobtest: erased 8 eraseblocks
mtd_oobtest: writing OOBs of whole device
mtd_oobtest: written 8 eraseblocks
mtd_oobtest: verifying all eraseblocks
mtd_oobtest: verified 8 eraseblocks
mtd_oobtest: test 4 of 5
mtd_oobtest: erasing whole device
mtd_oobtest: erased 8 eraseblocks
mtd_oobtest: attempting to start write past end of OOB
mtd_oobtest: an error is expected...
mtd_oobtest: error occurred as expected
mtd_oobtest: attempting to start read past end of OOB
mtd_oobtest: an error is expected...
mtd_oobtest: error occurred as expected
mtd_oobtest: attempting to write past end of device
mtd_oobtest: an error is expected...
mtd_oobtest: error occurred as expected
mtd_oobtest: attempting to read past end of device
mtd_oobtest: an error is expected...
mtd_oobtest: error: read past end of device
mtd_oobtest: attempting to write past end of device
mtd_oobtest: an error is expected...
mtd_oobtest: error occurred as expected
mtd_oobtest: attempting to read past end of device
mtd_oobtest: an error is expected...
mtd_oobtest: error: read past end of device
mtd_oobtest: test 5 of 5
mtd_oobtest: erasing whole device
mtd_oobtest: erased 8 eraseblocks
mtd_oobtest: writing OOBs of whole device
mtd_oobtest: written 7 eraseblocks
mtd_oobtest: verifying all eraseblocks
mtd_oobtest: verified 7 eraseblocks
mtd_oobtest: finished with 3 errors
=================================================
=================================================
mtd_subpagetest: MTD device: 0
mtd_subpagetest: MTD device size 1048576, eraseblock size 131072, page size 2048, subpage size 2048, count of eraseblocks 0, pages per eraseblock 0, OOB size 64
mtd_subpagetest: scanning for bad eraseblocks
mtd_subpagetest: block 0 is bad
mtd_subpagetest: scanned 8 eraseblocks, 1 are bad
mtd_subpagetest: erasing whole device
mtd_subpagetest: erased 8 eraseblocks
mtd_subpagetest: writing whole device
mtd_subpagetest: written 8 eraseblocks
mtd_subpagetest: verifying all eraseblocks
mtd_subpagetest: error: verify failed at 0xa0000
mtd_subpagetest: ------------- written----------------
290a823d1a832f294f3a152962dc06ad94bbe2a0556a0c65921a9092c1b7106f
<cut>
0d4441159c41f58ff943fe9fc93847c9f6d46b283a2b27736d1381b18f37b4bc
mtd_subpagetest: -------------------------------------
mtd_subpagetest: verified 8 eraseblocks
mtd_subpagetest: erasing whole device
mtd_subpagetest: erased 8 eraseblocks
mtd_subpagetest: verifying all eraseblocks for 0xff
mtd_subpagetest: verified 8 eraseblocks
mtd_subpagetest: writing whole device
mtd_subpagetest: written 8 eraseblocks
mtd_subpagetest: verifying all eraseblocks
mtd_subpagetest: error: verify failed at 0x40000
mtd_subpagetest: error: verify failed at 0xc0000
mtd_subpagetest: verified 8 eraseblocks
mtd_subpagetest: erasing whole device
mtd_subpagetest: erased 8 eraseblocks
mtd_subpagetest: verifying all eraseblocks for 0xff
mtd_subpagetest: verified 8 eraseblocks
mtd_subpagetest: finished with 3 errors
=================================================
next reply other threads:[~2011-02-09 8:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 8:32 Lars Michael [this message]
2011-02-11 14:28 ` mount ubi volume fails: No such device Artem Bityutskiy
2011-02-14 8:49 ` Lars Michael
2011-02-14 11:01 ` Artem Bityutskiy
2011-02-14 12:47 ` Lars Michael
-- strict thread matches above, loose matches on Subject: below --
2011-02-18 10:57 Lars Michael
2011-02-25 10:45 ` Artem Bityutskiy
2011-02-28 8:49 ` Lars Michael
2011-02-14 10:22 Lars Michael
[not found] <9186EF1D8AB86E40B9C8009D36864D0403CA4342@dhreinsvxb03.messaging.danaherad.com>
2011-02-11 14:21 ` Lars Michael
2011-02-11 14:35 ` Artem Bityutskiy
2011-02-11 14:57 ` Artem Bityutskiy
2011-02-09 12:34 Lars Michael
2011-02-11 14:32 ` Artem Bityutskiy
2011-02-07 15:05 Lars Michael
2011-02-07 15:27 ` Artem Bityutskiy
2011-01-31 10:35 Lars Michael
2011-02-06 14:19 ` 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=421430.70003.qm@web30207.mail.mud.yahoo.com \
--to=lh_post@yahoo.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.