From: Adrian Hunter <adrian.hunter@nokia.com>
To: "Tobias Wahlström" <tobias.tanke@gmail.com>
Cc: "Bityutskiy Artem \(Nokia-M/Helsinki\)"
<Artem.Bityutskiy@nokia.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: mkfs.ubifs / ubiformat: Bad UBI magic
Date: Thu, 08 Oct 2009 11:51:49 +0300 [thread overview]
Message-ID: <4ACDA825.2020206@nokia.com> (raw)
In-Reply-To: <29001ab20910060400j76167eg138df17d57727231@mail.gmail.com>
Tobias Wahlström wrote:
> Hi!
>
> This is my first post at this list - I hope it makes (at least) some
> sense anyway. I have looked through the mailing archive and searched
> using google without finding anything useful on the topic. I hope I
> provided the information you need - if not, just tell me what you are
> missing!
>
> I'm working on a project where we would like to use ubi and ubifs as
> root filesystem since it seems to be the best choise in many ways. But
> I have a problem which I can't find anything about either the mail
> archive nor using google etc. I currently use linux 2.6.26 with some
> patches. My target is the freescale imx255 pdk board. My build system
> is Ubuntu 9.04 (run within vmware).
>
> I have cloned the mtd-utils.git (today 2009-09-05) and compiled the
> tools both for my build system and my target (both without xattr
> support). Then I created a ubifs image using mkfs.ubifs on my build
> system and tried to flash it to the nand using ubiformat. The commands
> I used was:
>
> build> mkfs.ubifs -m 2048 -e 256KiB -c 384 -U --root rootfs -o rootfs.ubifs
Try making the -e option the leb-size not the peb-size i.e. probably 252KiB
> target> flash_eraseall /dev/mtd2
> target> ubiformat /dev/mtd2 -s 2048 -v -f rootfs.ubifs
>
> The output from ubiformat is:
>
> ubiformat: mtd2 (nand), size 100663296 bytes (96.0 MiB), 384
> eraseblocks of 262144 bytes (256.0 KiB), min. I/O size 2048 bytes
> libscan: start scanning eraseblocks 0-384
> libscan: scanning eraseblock 0: empty
> [...]
> libscan: scanning eraseblock 383: empty
> libscan: finished, mean EC 0, 0 OK, 0 corrupted, 384 empty, 0 alien, bad 0
> ubiformat: 384 eraseblocks are supposedly empty
> ubiformat: will write 13 eraseblocks
> ubiformat: eraseblock 0: erase, change EC to 0ubiformat: error!: bad
> UBI magic 0x31181006, should be 0x55424923
> ubiformat: error!: bad EC header at eraseblock 0 of "/rootfs.ubifs"
>
> If I look into the source code I see that UBI_EC_HDR_MAGIC is defined
> twice in the source both in include/mtd/ubi-media.h and seems to be
> used by all tools except for mkfs.ubifs. The command mkfs.ubifs use
> UBIFS_NODE_MAGIC in mkfs.ubifs/ubifs-media.h. The values do not match
> at all. And it also seems like mkfs.ubifs use little endian to encode
> the magic number and the other tools use big endian... Strange!
>
> /Tobias
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2009-10-08 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 11:00 mkfs.ubifs / ubiformat: Bad UBI magic Tobias Wahlström
2009-10-08 8:51 ` Adrian Hunter [this message]
2009-10-08 8:54 ` Adrian Hunter
2009-10-08 8:55 ` 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=4ACDA825.2020206@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tobias.tanke@gmail.com \
/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.