ubifs error at boot "bad node type"

[Richard Genoud]

2014-07-16 14:32 GMT+02:00 Richard Weinberger <richard at nod.at>:
> Am 16.07.2014 14:26, schrieb Richard Genoud:
>> 2014-07-16 14:02 GMT+02:00 Richard Weinberger <richard.weinberger at gmail.com>:
>>> On Wed, Jul 16, 2014 at 10:29 AM, Artem Bityutskiy <dedekind1 at gmail.com> wrote:
>>>> On Tue, 2014-07-08 at 12:10 +0200, Richard Genoud wrote:
>>>>> ubiattach is ok:
>>>>> # ubiattach -m 3
>>>>> [   50.164062] UBI: default fastmap pool size: 95
>>>>> [   50.164062] UBI: default fastmap WL pool size: 25
>>>>
>>>> I do not know why this happened, I never saw reports like this before.
>>>> Most probably this is because of fastmap. I did not hear any report that
>>>> it was extensively verified WRT power cuts, and my theory is that there
>>>> is a bug in fastmap which causes this, and this may be related to power
>>>> cuts. I do not have proves, but suggest you to dig in this direction.
>>>> E.g., setup power-cut testing.
>>>
>>> The logs don't show the "attached by fastmap" message. So UBI got
>>> attached by scanning.
>>> So, fastmap support is here but not used.
>>>
>>> Only the fastmap pools are used.
>>
>> Well, actually, fastmap is used on this volume when I boot from NAND.
>> (and I must say, It's fast !)
>> Just this time, as I boot from nfsroot, or from a unclean state,
>> fastmap didn't attached UBI.
>> I'll check if it's still operational.
>
> Okay, this explains your logs.
> I fear you don't have the original image anymore?
> Just thinking of how to understand/analyze this issue... :-\
Actually (after digging a little bit), I found the rootfs.ubifs image used.
It was flashed with ubiupdatevol

And, as Artem suggested, I'm going to save the entire flash.