From: simon widmer <simonxwidmer@gmail.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS Informations
Date: Wed, 05 Sep 2012 14:54:59 +0200 [thread overview]
Message-ID: <50474BA3.2070404@gmail.com> (raw)
In-Reply-To: <1346673385.3061.48.camel@sauron.fi.intel.com>
Update: I tested on Kernel 2.6.24-24 without success. The same manner if
i want to mount the image. What I discovered is that i noted earlier
that i have to compile with:
$ mkfs.ubifs -q -r $PATH\/data_h -m 2048 -e 129024 -c 2047 -o temp_h.img
$ ubinize -o data_h.img -m 2048 -p 128KiB -s 512 ubinize_h.cfg
and i have no idea what option "-q" is (neither does mkfs.ubifs). so I
just kicked it and compiled with:
$ mkfs.ubifs -r $PATH\/data_h -m 2048 -e 129024 -c 2047 -o temp_h.img
$ ubinize -o data_h.img -m 2048 -p 128KiB -s 512 ubinize_h.cfg
ubinize.cfg looks this way:
[data_h]
mode=ubi
image=temp_h.img
vol_id=0
vol_size=4MiB
vol_type=static
vol_name=data_h
vol_flags=autoresize
and the attaching procedure as follows:
UBI: attaching mtd8 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd8 to ubi0
UBI: MTD device name: "data_h"
UBI: MTD device size: 4 MiB
UBI: number of good PEBs: 32
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 32
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 165352633
UBI: background thread "ubi_bgt0d" started, PID 497
and finally the mounting procedure:
UBIFS error (pid 529): ubifs_read_node: bad node type (0 but expected 6)
UBIFS error (pid 529): ubifs_read_node: bad node at LEB 0:0
mount: wrong fs type, bad option, bad superblock on ubi0_0,
missing codepage or helper program, or other error
(UBIFS error (pid 529): ubifs_read_node: bad node type (0 but
expected 6)
for several filesystems (e.g. nfUBIFS error (pid 529): ubifs_read_node:
bad node at LEB 0:0
s, cifs) you might
need a /sbin/mount.<type> helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so
prev parent reply other threads:[~2012-09-05 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 14:19 UBIFS Informations simon widmer
2012-09-03 11:56 ` Artem Bityutskiy
2012-09-03 16:16 ` simon widmer
2012-09-05 12:54 ` simon widmer [this message]
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=50474BA3.2070404@gmail.com \
--to=simonxwidmer@gmail.com \
--cc=dedekind1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).