public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Oren <oren_s3@VERIFONE.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach problem
Date: Sun, 09 Aug 2009 07:36:41 +0300	[thread overview]
Message-ID: <1249792601.9157.24.camel@localhost> (raw)
In-Reply-To: <1247055811.2208.25.camel@tlvorens3lnx>

On Wed, 2009-07-08 at 15:23 +0300, Oren wrote:
> Well...thanks...seems like my device was not work properly.
> After fixing it...i have progress in ubiattach:
> 
> 
> [ 1387.120000] UBI: volume 0 ("NAND-block1") re-sized from 133 to 1655
> LEBs
> [ 1387.130000] UBI: attached mtd2 to ubi0
> [ 1387.130000] UBI: MTD device name:            "NAND-block2"
> [ 1387.140000] UBI: MTD device size:            210 MiB
> [ 1387.140000] UBI: number of good PEBs:        1675
> [ 1387.150000] UBI: number of bad PEBs:         5
> [ 1387.150000] UBI: max. allowed volumes:       128
> [ 1387.160000] UBI: wear-leveling threshold:    4096
> [ 1387.160000] UBI: number of internal volumes: 1
> [ 1387.170000] UBI: number of user volumes:     1
> [ 1387.170000] UBI: available PEBs:             0
> [ 1387.170000] UBI: total number of reserved PEBs: 1675
> [ 1387.180000] UBI: number of PEBs reserved for bad PEB handling: 16
> [ 1387.190000] UBI: max/mean erase counter: 0/0
> [ 1387.190000] UBI: background thread "ubi_bgt0d" started, PID 141
> 
> but when trying to mount i get the following:
> 
>  mount -t ubifs ubi0:NAND-block1 /mnt/ubi 
> [ 1654.740000] UBIFS error (pid 149): validate_sb: LEB size mismatch:
> 129024 in superblock, 126976 real
> [ 1654.750000] UBIFS error (pid 149): validate_sb: bad superblock, error
> 1
> mount: mounting ubi0:NAND-block1 on /mnt/ubi failed: Invalid argument

I've just created this FAQ entry for you:
http://www.linux-mtd.infradead.org/faq/ubifs.html#L_lebsz_mismatch

Enjoy :-)

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2009-08-09  4:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <baa101c9fe67$d7b31f0a$b65b1ec0@verifone.com>
2009-07-07  6:25 ` ubiattach problem 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 [this message]
2009-07-06 13:50 Oren
2009-07-06 14:05 ` Artem Bityutskiy
2011-09-09  9:53   ` marco

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=1249792601.9157.24.camel@localhost \
    --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