From: Artem Bityutskiy <dedekind@infradead.org>
To: Oren <oren_s3@VERIFONE.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach problem
Date: Mon, 06 Jul 2009 17:05:42 +0300 [thread overview]
Message-ID: <1246889142.20721.293.camel@localhost.localdomain> (raw)
In-Reply-To: <1246888221.17871.5.camel@tlvorens3lnx>
On Mon, 2009-07-06 at 16:50 +0300, Oren wrote:
> HI,
>
> I am trying to attached a ubi image to an MTD nand device.
> I am using kerenl version 2.6.27.18.
> using latest MTD-UTILS + ubi_utils.
>
> For some reosone i get UBI error while trying to attache..
> DO i miss someting?
>
>
> dev: size erasesize name
> mtd0: 01000000 00020000 "NAND-block1"
> mtd1: 01e00000 00020000 "jffs2"
> mtd2: 05200000 00020000 "NAND-block2"
> ./ubinfo
> UBI version: 1
> Count of UBI devices: 0
> UBI control device major/minor: 10:63
> ubiformat /dev/mtd0 -s 2048 -f ubi_ncomp.img
> ubiformat: mtd0 (nand), size 16777216 bytes (16.0 MiB), 128 eraseblocks
> of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
> libscan: scanning eraseblock 127 -- 100 % complete
> ubiformat: 128 eraseblocks are supposedly empty
> ubiformat: flashing eraseblock 16 -- 100 % complete
> ubiformat: formatting eraseblock 127 -- 100 % complete
> ubiattach /dev/ubi_ctrl -m 0
> [42949485.550000] UBI error: ubi_read_volume_table: the layout volume
> was not found
> [42949485.560000] UBI error: ubi_attach_mtd_dev: failed to attach by
> scanning, error -22
> ubiattach: error!: cannot attach mtd0
> error 22 (Invalid argument)
Looks strange. Does dmesg has anything interesting when you enable
UBI debugging?
(http://www.linux-mtd.infradead.org/doc/ubi.html#L_how_send_bugreport)
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-07-06 14:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 13:50 ubiattach problem Oren
2009-07-06 14:05 ` Artem Bityutskiy [this message]
2011-09-09 9:53 ` marco
[not found] <baa101c9fe67$d7b31f0a$b65b1ec0@verifone.com>
2009-07-07 6:25 ` Artem Bityutskiy
2009-07-07 10:32 ` Oren
2009-07-07 10:42 ` Artem Bityutskiy
2009-07-07 12:08 ` Oren
2009-07-07 12:51 ` Artem Bityutskiy
2009-07-07 13:21 ` Oren
2009-07-07 13:28 ` Artem Bityutskiy
2009-07-07 14:08 ` Oren
2009-07-07 14:19 ` Artem Bityutskiy
2009-07-07 14:38 ` Artem Bityutskiy
2009-07-07 14:49 ` Oren
2009-07-07 14:53 ` Artem Bityutskiy
2009-07-07 15:30 ` Oren
2009-07-07 15:38 ` Oren
2009-07-07 15:45 ` Artem Bityutskiy
2009-07-12 7:19 ` Oren Sokolowsky
2009-07-12 14:06 ` Artem Bityutskiy
2009-07-27 12:54 ` Oren
2009-08-09 4:36 ` 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=1246889142.20721.293.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=oren_s3@VERIFONE.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox