public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: linux-mtd@lists.infradead.org, Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: ubifs error at boot "bad node type"
Date: Wed, 16 Jul 2014 15:17:45 +0300	[thread overview]
Message-ID: <1405513065.5423.17.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <53BBC39F.7010307@gmail.com>

On Tue, 2014-07-08 at 12:10 +0200, Richard Genoud wrote:
> [   87.054687] UBIFS error (pid 652): ubifs_read_node: bad node type
> (255 but expected 0)
> [   87.062500] UBIFS error (pid 652): ubifs_read_node: bad node at LEB
> 405:39728, LEB mapping status 1
> [   87.070312] Not a node, first 24 bytes:

I think it is a good idea do dump the flash and save it, just in case.

So the LEB is mapped.

But the TNC points to an an area with all 0xFFs.

Either TNC is incorrect or, the UBI did not map the LEB to the correct
PEB. "Fastmap" would be an easy target to blame for me, but if it is not
used, I'd say the former is more probably.

Enabling full UBI/UBIFS debugging and reproducing the failure could
help.

And please, do save the flash image (use nanddump).

-- 
Best Regards,
Artem Bityutskiy

      parent reply	other threads:[~2014-07-16 12:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 10:10 ubifs error at boot "bad node type" Richard Genoud
2014-07-09  0:51 ` hujianyang
2014-07-09  7:23   ` Richard Genoud
2014-07-16  8:29 ` Artem Bityutskiy
2014-07-16 12:02   ` Richard Weinberger
2014-07-16 12:26     ` Richard Genoud
2014-07-16 12:32       ` Richard Weinberger
2014-07-16 14:39         ` Richard Genoud
2014-07-16 12:33       ` Artem Bityutskiy
2014-07-16 12:49         ` Richard Weinberger
2014-07-16 12:06   ` hujianyang
2014-07-16 12:17 ` Artem Bityutskiy [this message]

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=1405513065.5423.17.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.genoud@gmail.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