Page 1 of 1

help with UBIFS error

Posted: Mon Mar 26, 2018 3:38 pm
by AXvim1

I am working on a shiratech board som sama5d3xek, Linux version 4.1.0-linux4sam_5.2-ShiraTech-00.02-PIS-svn9532.
I have working boards in the field and some time a board fail with an error.

example error:

UBIFS error (ubi0:0 pid 947): ubifs_decompress: cannot decompress 2461 bytes, compressor lzo, error -22
UBIFS error (ubi0:0 pid 947): read_block: bad data node (block 96, inode 5484)
magic 0x6101831
crc 0x8f24830e
node_type 1 (data node)
group_type 0 (no node group)
sqnum 55159
len 2509
key (5484, data, 96)
size 4096
compr_typ 1
data size 2461

also on boot there is this:

ubi0: attaching mtd7
random: nonblocking pool is initialized
ubi0: scanning is finished
ubi0: attached mtd7 (name "rootfs", size 248 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 1980, bad PEBs: 4, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 72/12, WL threshold: 4096, image sequence number: 69872204
ubi0: available PEBs: 0, total reserved PEBs: 1980, PEBs reserved for bad PEB handling: 36
ubi0: background thread "ubi_bgt0d" started, PID 633

UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery deferred
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 244936704 bytes (233 MiB, 1929 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 550A2E95-035A-451D-8F25-26076F8AA896, small LPT model
VFS: Mounted root (ubifs filesystem) readonly on device 0:14.

what does this error means?

Re: help with UBIFS error

Posted: Wed Mar 28, 2018 11:17 pm
by blue_z
One approach to investigating such issues is to determine if power cuts are a factor.
See this old linux-mtd mailing-list thread for ideas: ... decompress