From: Lars Michael <lh_post@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: mount ubi volume fails: No such device
Date: Mon, 14 Feb 2011 00:49:30 -0800 (PST) [thread overview]
Message-ID: <953130.73844.qm@web30208.mail.mud.yahoo.com> (raw)
In-Reply-To: <1297434507.2760.30.camel@localhost>
--- On Fri, 11/2/11, Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> > The oobtest and subpagetest found 3 errors, see below.
> Does it explain
> > my initial problem?
>
> Yes. You cannot go forward with UBIFS before you have fixed
> those.
> Esepcially subpage test is relevant to you, you really have
> to have it
> fixed, or you can just ask UBIFS to not use sub-pages and
> see how it
> behaves, but this is less optimal.
>
I am running on the TWR-MCF5441X eval. board, which has a 256MB NAND device: MT29F2G16AADWP. From the data sheet it should have no sub pages, and this matches what UBI reports:
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
# cat proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 0ff00000 00020000 "ubi"
mtd2: 00100000 00010000 "at26df081a"
I used ubiformat without the -s or -O:
ubiformat /dev/mtd1 -f /root/ubi.img
I tried with -O 2048, but still failed. I guess forcing the VID header to offset 2048 is anyway correct for this device? Are there another way to turn off sub-page in UBIFS?
Here is how i made the UBI image:
./mkfs.ubifs -m 2048 -e 126976 -c 874 -v -Q -r ./rootfs rootfs.img
./mkfs.ubifs -m 2048 -e 126976 -c 36 -v -Q -r ./progfs progfs.img
./mkfs.ubifs -m 2048 -e 126976 -c 49 -v -Q -r ./datafs datafs.img
ubinize -o ubi.img -p 128KiB -m 2048 -v ubi-config.ini
Now i rebuild the kernel with additional debug options turned on. Will run subpage test again and submit report on that.
Thanks and regards,
- Lars
next prev parent reply other threads:[~2011-02-14 8:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 8:32 mount ubi volume fails: No such device Lars Michael
2011-02-11 14:28 ` Artem Bityutskiy
2011-02-14 8:49 ` Lars Michael [this message]
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=953130.73844.qm@web30208.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.