Re: ubiattach problem

[Artem Bityutskiy <dedekind@infradead.org>]

On Tue, 2009-07-07 at 16:21 +0300, Oren wrote:
> ubinize: LEB size:      126976
> ubinize: PEB size:      131072
> ubinize: min. I/O size: 2048
> ubinize: sub-page size: 2048
> ubinize: VID offset:    2048
> ubinize: data offset:   4096
> ubinize: loaded the ini-file "images/ubinize.cfg"
> ubinize: count of sections: 1
> 
> ubinize: parsing section "ubifs"
> ubinize: mode=ubi, keep parsing
> ubinize: volume type: dynamic
> ubinize: volume ID: 0
> ubinize: volume size: 16777216 bytes
> ubinize: volume name: NAND-block1
> ubinize: volume alignment: 1
> ubinize: autoresize flags found
> ubinize: adding volume 0
> ubinize: writing volume 0
> ubinize: image file: images/ubifs_ncomp.img
> 
> ubinize: writing layout volume
> ubinize: done

OK, thanks. Can I please see what the kernel UBI is doing?

Could you please enable this option in the kernel config:

Device Drivers  --->
  <*> Memory Technology Device (MTD) support  --->
    UBI - Unsorted block images  --->
      Additional UBI debugging messages  --->
        [*] Additional UBI initialization and build messages

Then attach the UBI device, reproduce the problem, and give me UBI
output. I want to see what UBI finds on the flash. Please, refer
this section for more information about how to capture the debugging
messages:
http://www.linux-mtd.infradead.org/faq/ubi.html#L_how_debug

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