Re: ubiattach fails with "bad image sequence number"

[Artem Bityutskiy <dedekind1@gmail.com>]

On Tue, 2010-01-12 at 22:26 -0500, Jeff Angielski wrote:
> Artem Bityutskiy wrote:
> > On Sun, 2010-01-10 at 01:51 +0200, Artem Bityutskiy wrote:
> >> Hi,
> >>
> >> On Mon, 2009-12-21 at 17:33 -0500, Jeff Angielski wrote:
> >>> If I ubiformat my NAND partition with an UBIFS image I keep on getting 
> >>> "bad image sequence number" when I try to do the ubiattach.  If I just 
> >>> do a plain ubiformat with no image then everything works fine when I 
> >>> ubiattach.
> >>>
> >>> I was wondering if somebody ran into something similar.  The steps are 
> >>> so trivial it seems like something fundamentally wrong with either the 
> >>> mkfs.ubifs or the ubiformat.
> >>>
> >>> I did not see anything related to this on the UBFI FAQ or documentation.
> >> I believe this is an ubiformat bug. Thanks for reporting and sorry for
> >> inconvenience.
> >>
> >> I attach and inline 2 patches which should fix this. I cannot have a
> >> possibility to test them now, so they are untested. They are against the
> >> latest mtd-utils.git (commit a4e502d99129da8ebba6d40b373a4422a175e9af).
> > 
> > Could you please try them and report if they fix your problem or not?
> > 
> > P.S. when we fix this, we'll have to tag a new mtd-utils version, since
> > this is a very bad bug.
> 
> This patch worked for me.

Ok, pushed them.

> FWIW, I am using 2.6.31 kernel and the mtd-utils last commit was: 
> a4e502d99129da8ebba6d40b373a4422a175e9af.
> 
> I did receive a warning "ubi_eba_init_scan: cannot reserve enough PEBs 
> for bad PEB handling, reserved 9, need 20" but I believe that is 
> operator error related to the large volume size in the mtd partition.

Yes, create smaller volumes.

> I have one slight change from the original command line commands I 
> posted.  For mkfs.ubifs my original -e was incorrectly the PEB instead 
> of the LEB.  So for those kids following along, don't use the original 
> command sequence.
> 
> 
> So the new command line sequence on the x86 host looks like:
> 
> $ mkfs.ubifs -r build/targetfs_tiny -m 4096 -e 258048 -c 2047 -o tiny.ubifs
> 
> $ ubinize -s 1024 -o ubifs1b.img -m 4096 -p 256KiB ubifs1.cfg
> 
> $ cat ubifs1.cfg
> [ubifs]
> mode=ubi
> image=tiny.ubifs
> vol_id=0
> vol_size=500MiB
> vol_type=dynamic
> vol_name=fs1
> vol_alignment=1
> vol_flags=autoresize

You need to make vol_size=500MiB smaller to get rid of the warning.

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