UBIFS error (pid 564): read_znode: bad indexing node at LEB 484:66064, error 2
dedekind1 at gmail.com
Fri Nov 16 03:31:06 EST 2012
On Wed, 2012-11-07 at 16:32 -0500, Micah Anderson wrote:
> I had a power outage yesterday. When things came back and I tried to
> boot my guruplug, I am not getting the following:
> [ 97.273764] UBIFS error (pid 564): read_znode: bad indexing node at LEB 484:66064, error 2
> [ 97.282188] UBIFS warning (pid 564): ubifs_ro_mode: switched to read-only mode, error -22
> [ 97.290431] UBIFS error (pid 564): ubifs_budget_space: cannot budget space, error -22
I'd need to see entire log, no -ENOCLUE with this amount of input.
> The filesystem is read-only and I can't seem to figure out how to get it
> out of this state. As far as I can tell, there is no fsck.ubifs and I'm
> at a loss at how to get things back to a reasonable state. I found the
> 'nandtest' command, which might be useful for mapping out bad areas, but
> I'm not going to run that without a better clue at how likely I am to
> brick things.
No, there is no recovery program, the file-system is supposed to always
be mountable. Please, use mtdtests to validate the HW:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the linux-mtd