From: Artem Bityutskiy <dedekind1@gmail.com>
To: Paul Black <paul.0000.black@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS Problems After Upgrading Kernel
Date: Mon, 15 Apr 2013 18:40:31 +0300 [thread overview]
Message-ID: <1366040431.2768.83.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <51682A79.1010307@gmail.com>
On Fri, 2013-04-12 at 16:38 +0100, Paul Black wrote:
> [ 1.650000] UBIFS error (pid 1): ubifs_read_node: bad node type (255
> but expected 6)
> [ 1.660000] UBIFS error (pid 1): ubifs_read_node: bad node at LEB
> 0:0, LEB mapping status 0
> [ 1.660000] Not a node, first 24 bytes:
> [ 1.670000] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff
UBIFS says that the eraseblock where it expects to find the Master node
is empty. Somehow the data is not there anymore. Can you compare the
contents of the corresponding /dev/mtd and /dev/ubi* before and after
upgrade?
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-04-15 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 15:38 UBIFS Problems After Upgrading Kernel Paul Black
2013-04-15 15:40 ` Artem Bityutskiy [this message]
2013-04-16 14:17 ` Paul Black
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=1366040431.2768.83.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=paul.0000.black@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