From: Artem Bityutskiy <dedekind1@gmail.com>
To: Arno Steffen <arno.steffen@googlemail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: error!: "/dev/ubi0" is not a character device ?!?
Date: Fri, 30 Jul 2010 09:35:55 +0300 [thread overview]
Message-ID: <1280471755.2838.29.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTi=7-Ur35OzqF7iJtiPzfc-Jp-ANGwa3g_Y=+ae8@mail.gmail.com>
On Wed, 2010-07-28 at 13:04 +0200, Arno Steffen wrote:
> Thanks Artem,
> I am using a 2.6.33 kernel, this should be new enough. It is right,
> that it is as a block device (in /dev/ ) ?
No, _all_ UBI devices are character devices. New UBIFS can mount these
character devices, old UBIFS cannot, and requires deviceless mounting.
As documented here:
http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mount_ubifs
2.6.33 indeed should be able to mount /dev/ubi0_0.
But because your system is strange in a way that your UBI devices are
block devices, this does not work.
> [root@or:/]# ubiattach /dev/ubi_ctrl -m 8 -d 8
> UBI: attaching mtd8 to ubi8
> 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 warning: ubi_eba_init_scan: cannot reserve enough PEBs for bad PEB
> handling, reserved 1, need 3
> UBI: attached mtd8 to ubi8
> UBI: MTD device name: "extra"
> UBI: MTD device size: 41 MiB
> UBI: number of good PEBs: 331
> UBI: number of bad PEBs: 1
> 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: 331
> UBI: number of PEBs reserved for bad PEB handling: 1
> UBI: max/mean erase counter: 1/0
> UBI: image sequence number: 228182237
> UBI: background thread "ubi_bgt8d" started, PID 386
> UBI device number 8, total 331 LEBs (42706944 bytes, 40.7 MiB),
> available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
> [root@or:/]# ll /dev/ubi*
> brw-rw---- 1 root root 253, 0 Jan 1 00:00 /dev/ubi8
> brw-rw---- 1 root root 253, 1 Jan 1 00:00 /dev/ubi8_0
> crw-rw---- 1 root root 10, 63 Jan 1 00:00 /dev/ubi_ctrl
Wrong. Everything has to be character devices.
> [root@or:/]#
> [root@or:/]# mount -t ubifs /dev/ubi8 /tmp
> mount: mounting /dev/ubi8 on /tmp failed: No such device
> [root@or:/]# mount -t ubifs /dev/ubi8_0 /tmp
> mount: mounting /dev/ubi8_0 on /tmp failed: No such device
These do not work because /dev/ubi* have to be chdev.
> [root@or:/]# mount -t ubifs ubi8_0 /tmp
> mount: mounting ubi8_0 on /tmp failed: No such device
> [root@or:/]# mount -t ubifs ubi8 /tmp
> mount: mounting ubi8 on /tmp failed: No such device
Do you have volume 0 on ubi8?
Please, send me ls /sys/class/ubi/ and ls /sys/class/ubi/ubi8/
Also, please, check /proc/devices and make sure ubi is in "Character
devices" list.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-07-30 6:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 12:00 error!: "/dev/ubi0" is not a character device ?!? Arno Steffen
2010-07-26 13:14 ` Artem Bityutskiy
2010-07-26 13:49 ` Arno Steffen
2010-07-27 15:25 ` Artem Bityutskiy
2010-07-28 11:04 ` Arno Steffen
2010-07-30 6:35 ` Artem Bityutskiy [this message]
2010-08-05 11:55 ` Arno Steffen
2010-08-05 13:23 ` twebb
2010-08-05 13:36 ` Artem Bityutskiy
[not found] ` <AANLkTikkRNqnEX0PkHigv=zT+Z36J52DEtoVeMGbBExf@mail.gmail.com>
2010-08-16 11:27 ` Arno Steffen
2010-08-23 12:34 ` Artem Bityutskiy
2010-08-23 14:13 ` Arno Steffen
2010-08-23 14:41 ` Artem Bityutskiy
2010-08-24 8:32 ` Arno Steffen
2010-08-24 8:53 ` Artem Bityutskiy
2010-08-24 9:19 ` Arno Steffen
2010-08-24 9:33 ` Artem Bityutskiy
2010-07-30 6:23 ` 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=1280471755.2838.29.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=arno.steffen@googlemail.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.