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 04:34:03 -0800 (PST) [thread overview]
Message-ID: <771706.3446.qm@web30204.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
>
I formatted and wrote the image again. ubiattach _sometimes_ completes without the error code -22. In this case the mount went ok. But mount sometimes fails completely (structure needs cleaning), other times errors are reported but successfully recovered. So it seems to work, but no in
a reliable way. Any suggestions on how to improve it? My kernel is 2.6.29 so perhaps some patches are needed?
For example:
[root@M54418TWR /]# mount -t ubifs ubi0:rootfs /mnt/ubi_rootfs
UBIFS error (pid 661): ubifs_scan: garbage
UBIFS error (pid 661): ubifs_scanned_corruption: corrupted data at LEB 2:8192
UBIFS error (pid 661): ubifs_scanned_corruption: first 4096 bytes from LEB 2:8192
UBIFS error (pid 661): ubifs_scan: LEB 2 scanning failed
UBIFS error (pid 661): ubifs_scan: corrupt empty space at LEB 5:69632
UBIFS error (pid 661): ubifs_scanned_corruption: corrupted data at LEB 5:69632
UBIFS error (pid 661): ubifs_scanned_corruption: first 4096 bytes from LEB 5:69632
UBIFS error (pid 661): ubifs_scan: LEB 5 scanning failed
mount: mounting ubi0:rootfs on /mnt/ubi_rootfs failed: Structure needs cleaning
or:
mount -t ubifs ubi0:datafs /mnt/udatafs
UBIFS error (pid 670): ubifs_scan: garbage
UBIFS error (pid 670): ubifs_scanned_corruption: corrupted data at LEB 2:4096
UBIFS error (pid 670): ubifs_scanned_corruption: first 4096 bytes from LEB 2:4096
UBIFS error (pid 670): ubifs_scan: LEB 2 scanning failed
UBIFS: recovery needed
UBIFS error (pid 670): ubifs_scan: garbage
UBIFS error (pid 670): ubifs_scanned_corruption: corrupted data at LEB 4:0
UBIFS error (pid 670): ubifs_scanned_corruption: first 4096 bytes from LEB 4:0
UBIFS error (pid 670): ubifs_scan: LEB 4 scanning failed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 2, name "datafs"
UBIFS: file system size: 4952064 bytes (4836 KiB, 4 MiB, 39 LEBs)
UBIFS: journal size: 1142785 bytes (1116 KiB, 1 MiB, 9 LEBs)
UBIFS: media format: 4 (latest is 4)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
Regards,
- Lars
next reply other threads:[~2011-02-09 12:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 12:34 Lars Michael [this message]
2011-02-11 14:32 ` mount ubi volume fails: No such device Artem Bityutskiy
-- 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 8:32 Lars Michael
2011-02-11 14:28 ` Artem Bityutskiy
2011-02-14 8:49 ` Lars Michael
2011-02-14 11:01 ` Artem Bityutskiy
2011-02-14 12:47 ` Lars Michael
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=771706.3446.qm@web30204.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.