ubi问题总结

挂载成功有时出现：

UBIFS error (pid 76): ubifs_read_node: bad node type (255 but expected 1)
UBIFS error (pid 76): ubifs_read_node: bad node at LEB 31:20480, LEB mapping status 0
UBIFS error (pid 76): do_readpage: cannot read page 0 of inode 70, error -22

1.在uboot里，setenv nand_root ubi0:rootfs rw ubi.mtd= (此处对应),2048
2.制作imgae时，mkfs.ubifs -c 这个参数要仔细计算，些参数影响较大，再就是改一下ubinize.cfg这个文件的相关参数，要经过计算

３.看驱动，以用硬件连接，不要造成flash的只读情况出现

ubifs_read_node 报错，还会有类似oops的错误

UBIFS: default compressor: LZO
UBIFS: reserved for root:  0 bytes (0 KiB)
UBIFS error (pid 0): ubifs_read_node: bad node type (255 but expected 9)
UBIFS error (pid 0): ubifs_read_node: bad node at LEB 85:60448
UBIFS error (pid 0): ubifs_iget: failed to read inode 1, error -22
Machine check in kernel mode.
Caused by (from msr): regs 0fe7ca88 Unknown values in msr
NIP: 0FFB7C80 XER: 00000000 LR: 0FFB7C5C REGS: 0fe7ca88 TRAP: 0200 DAR: 00000000
MSR: 0000b032 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11

GPR00: 0004434C 0FE7CB78 0FE7CF50 FFFF7FFF 0FFF8020 00000000 0FFF8020 FFFF7FF7 
GPR08: 00021AE8 DC0FFF80 0FFF83F8 0FFF83F8 22044024 7037FFBF 0FFFB000 00000000 
GPR16: 0FFECF7C 0FFF691C 00000000 00000000 0FEE1310 0FEDFB28 FFFFF000 0FEE0BA0 
GPR24: 00000000 00000003 0FEE129C 00000001 00000001 0FFF9100 0FFFBFA8 0FEE0C88 
Call backtrace: 
0FEE0C88 0FFCABFC 0FFCBEE8 0FFCC050 0FFB6590 0FFBC468 0FFBBB78 
0FFBBD98 0FFBD728 0FFBC468 0FFBBB78 0FFBBD98 0FFBE7D0 0FFA188C 
0FFA05F0 
machine check
Resetting the board.

解决办法：

关于这个oops的错误参考以下链接的修改

http://lists.denx.de/pipermail/u-boot/2011-October/103864.html

On Tue, Oct 4, 2011 at 6:08 PM, larsi <larsi at atlantis.wh2.tu-dresden.de> wrote:
 This patch fixes an issue when ubifs reads a bad superblock. Later it
 tries to free memory, that was not allocated, which freezes u-boot.
 This is fixed by looking for a non null pointer before free.

 Signed-off-by: Lars Poeschel <larsi at wh2.tu-dresden.de>
 Cc: Kyungmin Park <kmpark at infradead.org>
 ---
 The message I got before u-boot freezes:
 UBI: max/mean erase counter: 53/32
 UBIFS: mounted UBI device 0, volume 1, name "rootfs"
 UBIFS: mounted read-only
 UBIFS: file system size:   49140 bytes (50319360 KiB, 0 MiB, 49140 LEBs)
 UBIFS: journal size:       49 bytes (6838272 KiB, 0 MiB, 6678 LEBs)
 UBIFS: media format:       w4/r0 (latest is w4/r0)
 UBIFS: default compressor: LZO
 UBIFS: reserved for root:  0 bytes (0 KiB)
 UBIFS error (pid 0): ubifs_read_node: bad node type (255 but expected 9)
 UBIFS error (pid 0): ubifs_read_node: bad node at LEB 330:13104
 UBIFS error (pid 0): ubifs_iget: failed to read inode 1, error -22
 Error reading superblock on volume 'ubi:rootfs'!

  fs/ubifs/super.c |    6 ++++--
  1 files changed, 4 insertions(+), 2 deletions(-)

 diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
 index 63b2164..20fb244 100644
 --- a/fs/ubifs/super.c
 +++ b/fs/ubifs/super.c
 @@ -848,8 +848,10 @@ void ubifs_umount(struct ubifs_info *c)
        ubifs_debugging_exit(c);

        /* Finally free U-Boot's global copy of superblock */
 -       free(ubifs_sb->s_fs_info);
 -       free(ubifs_sb);
 +       if (ubifs_sb != null) {
 +               free(ubifs_sb->s_fs_info);
 +               free(ubifs_sb);
 +       }
Which statement is problem? Basically free() check the null address.
so If ubifs_sb->s_fs_info doesn't have value its skipped. and ubifs_sb
is similar.

Thank you,
Kyungmin Park
  }

但是关于ubifs_read_node: bad node type (255 but expected 9)

这个错误一直没找到精准的解决办法，开始的时候怀疑mkfs.ubifs的参数问题，各种修改也没好转

后来发现kernel的大小（烧写的时候的大小）不对，

kernel_img=a36800（写入大小）

ubi write 0x3000000 kernel$kernel_img


Load address: 0x3000000
Loading: #################################################################
         ################################################################
         ####################
done
Bytes transferred = 10792960 (a4b000 hex)（实际大小）

我记得修改过这个参数啊，唉

但不可否认的是改了这两个地方后，问题就解决了，如果写入的文件不完全或被破坏，ubimount时就会出错

：http://www.360doc.com/content/14/1018/14/18578054_417913216.shtml

配置内核，使其支持ubifs文件系统

　　　　1)Device Drivers --->Memory Technology Device (MTD) support --->UBI - Unsorted block images --->Enable UBI
　　　　2)File systems --->Miscellaneous filesystems --->UBIFS file system support

制作ubifs格式的根文件系统镜像

先说明一下，板子上既有NorFlash，又有NandFlash，其中根文件系统和应用程序放在NandFlash上，uboot和kernel放在NorFlash上，而根文件系统所在的mtd设备为mtd2，分区大小为34MiB

./mkfs.ubifs -v -r ./rootfs -o rootfs.img -m 2048 -e 129024 -c 272

　 -r：制定文件内容的位置 -m：页面大小 -e：逻辑擦除块大小 -c：最大的逻辑擦除块数量

1. mkfs.ubifs -m 2048 -e 129024 -c 1984 -o rootfs.ubifs -x none
2.  
3. -m 2048   (Minimum input/output unit size: 2048 bytes)
4. -e 129024 (Default UBI LEB size:           129024 bytes, 126.0 KiB)
5. -c 1984   (Amount of eraseblocks:          1984 (260046848 bytes, 248.0 MiB))
6. -o rootfs.ubifs (output file)
7. -x none   (no compression)

./ubinize -v -o rootfs.ubi -m 2048 -p 128KiB -s 2048 hi.cfg

-p：物理擦除块大小

-m：页面大小

-s: 最小的硬件输入输出页面大小，如：k9f1208为256(上下半页访问)

配置文件hi.cfg如下：

[ubifs]
mode=ubi
image=rootfs.img
vol_id=0
vol_size=34MiB
vol_type=dynamic
vol_alignment=1
vol_name=rootfs
vol_flag=autoresize

然后修改uboot的环境变量：

setenv bootargs 'mem=288M console=ttyAMA0,115200  root=ubi0:rootfs rw rootflags=sync rootfstype=ubifs ubi.mtd=2  mtdparts=hi_sfc:5M(boot),1M(picture);hinand:34M(rootfs),8M(config),86M(app)';

保存环境变量，执行如下命令

setenv ipaddr 192.168.253.132;

setenv serverip 192.168.253.130;

setenv ethaddr 40:61:86:67:33:47;

mw.b 82000000 ff 2200000;

tftp 82000000 rootfs.ubi;

nand erase 0 2200000;

nand write 82000000 0 $(filesize);

sf probe 0;

sf read 0x82000000 0x100000 0x400000;

bootm 0x82000000

说明：

其实从上面的烧写命令可以看出，ubifs格式的镜像中是不包含oob信息的。

参见：http://www.cnblogs.com/pengdonglin137/p/3399071.html

出现如下错误信息：

UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 0
UBI error: vtbl_check: volume table check failed: record 0, error 9
UBI error: ubi_init: cannot attach mtd2
Fixed MDIO Bus: probed

原因：

参考 http://wiki.linpert.de/index.php?title=UBIFS#record_0.2C_error_9

http://lists.infradead.org/pipermail/linux-mtd/2009-April/025127.html


But I took a look into the code, and the following is error 9:

if (reserved_pebs > ubi->good_peb_count) {
dbg_err("too large reserved_pebs %d, good PEBs %d",
reserved_pebs, ubi->good_peb_count);
err = 9;
goto bad;
}

This means you created a too large UBI volume in the image,
and your real flash is smaller.

Try to enable UBI debugging, and type dmesg, then you'll see
reserved and real eraseblock numbers.

原因就是：在配置文件中，volume设为34MiB，太大了，因为整个mtd2分区总共才34MiB。

解决办法：将配置文件改为：

[ubifs]
mode=ubi
image=rootfs.img
vol_id=0
vol_size=32MiB
vol_type=dynamic
vol_alignment=1
vol_name=rootfs
vol_flag=autoresize

说明：

vol_id 表示volume的编号，一个ubi设备中可以有多个volume。（这种情况下，/dev下会出现 ubi0 和 ubi0_0）
vol_size 表示ubi0_0的大小，即volume0的大小
vol_type 表示volume0的类型，分为dynamic和static两种，其中dynamic类型的设备表示可以读写，static类型的设备表示只读
vol_name 表示volume0的名称，在挂载ubi分区是会使用到，如在bootargs中的root=ubi0:rootfs

然后重新执行： ./ubinize -v -o rootfs.ubi -m 2048 -p 128KiB -s 2048 hi.cfg

当再次重启后，又出现如下错误信息：

UBIFS: parse sync
UBIFS error (pid 1): validate_sb: LEB size mismatch: 129024 in superblock, 126976 real
UBIFS error (pid 1): validate_sb: bad superblock, error 1

原因：

参考：http://www.linux-mtd.infradead.org/faq/ubifs.html#L_lebsz_mismatch

I see this UBIFS error: "validate_sb: LEB size mismatch: 129024 in superblock, 126976 real"

When you create an UBIFS image using the mkfs.ubifs utility, you specify LEB size using the -e option. This is a very important parameter and you should specify it correctly in order to have working UBIFS image. Indeed, LEB size is the major UBIFS storage unit, e.g., UBIFS nodes never cross LEB boundaries, garbage collection is performed on individual LEBs, etc. See this section for more information.

The error message means that LEB size information which is stored in the UBIFS superblock does not match the real LEB size, which UBIFS takes from UBI. The superblock was created by the mkfs.ubifs utility, therefore you failed to pass the correct LEB size to the utility. Fix this by passing correct LEB size via the -e option.

原因是：逻辑块的大小与实际的大小不符

解决办法：

将-e选项的值由129024改成126976

重新执行：

 ./mkfs.ubifs -v -r ./rootfs -o rootfs.img -m 2048 -e 126976 -c 272

 ./ubinize -v -o rootfs.ubi -m 2048 -p 128KiB -s 2048 hi.cfg

重新烧写并重启。

还有一个需要注意的问题是，如果将-s选项的值搞错，如将2048写成了512，那么会有如下错误信息

UBI error: validate_ec_hdr: bad VID header offset 512, expected 2048
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd2
Fixed MDIO Bus: probed

从错误提示中就可以看到解决方法：将-s选项的值改为2048即可。

参考：http://www.cnblogs.com/pengdonglin137/p/3404685.html

UBI headers

UBI stores 2 small 64-byte headers at the beginning of each non-bad physical eraseblock:

erase counter header (or EC header) which contains the erase counter of the physical eraseblock (PEB) plus some other not so important information;

volume identifier header (or VID header) which stores volume ID and logical eraseblock (LEB) number this PEB belongs to (plus some other not so important information).

This is why logical eraseblocks are smaller than physical eraseblock - the headers take some flash space.

UBI headers position

The EC header always resides at offset 0 and takes 64 bytes, the VID header resides at the next available min. I/O unit or sub-page, and also takes 64 bytes. For example:

in case of NOR flash which has 1 byte min. I/O unit, the VID header resides at offset 64;

in case of NAND flash which does not have sub-pages, the VID header resides at the second NAND page;

in case of NAND flash which has sub-pages, the VID header resides at the second sub-page.

UBI utilizes sub-pages to lessen flash space overhead. The overhead is less if NAND flash supports sub-pages (see here). Indeed, let's consider a NAND flash with 128KiB eraseblocks and 2048-byte pages. If it does not have sub-pages, UBI puts the the VID header at physical offset 2048, so LEB size becomes 124KiB (128KiB minus one NAND page which stores the EC header and minus another NAND page which stores the VID header. In opposite, if the NAND flash does have sub-pages, UBI puts the VID header at physical offset 512 (the second sub-page), so LEB size becomes 126KiB (128KiB minus one NAND page which is used for storing both UBI headers). See this section for more information about where the UBI headers are stored.

也就是说，对于上面的例子，如果有subpage（可以到/sys/class/mtd/其中的一个目录下使用cat命令去查看某个mtd设备的subpagesize参数），如果是512B,这有如下参数搭配（对于块大小是128KiB，页大小是2KB的NandFlash来说）：

 ./mkfs.ubifs -v -r ./rootfs -o rootfs.img -m 2048 -e 129024 -c 272 
 ./ubinize -v -o rootfs.ubi -m 2048 -p 128KiB -s 512 hi.cfg

其中 -e表示的是逻辑块的大小，因为subpagesize大小是512（也就是-s选项的值），第一页的前512存放EC（实际用了前64B），接下来的512B（前64B）存放UBI headers，逻辑块的大小就是128KiB-2KiB=126KiB，转化成十进制就是129024。

假如没有subpagesize，那么有如下搭配：

./mkfs.ubifs -v -r ./rootfs -o rootfs.img -m 2048 -e 126976 -c 272 

./ubinize -v -o rootfs.ubi -m 2048 -p 128KiB -s 2048 hi.cfg

其中，逻辑块的大小：128KiB-2KiB-2KiB=124KiB，转换成10进制就是126976，-s后面的值为页大小，即2048B。

https://blog.csdn.net/davion_zhang/article/details/47400553

http://www.360doc.com/content/14/1018/14/18578054_417913216.shtml

posted @ 2019-12-30 14:07 schips 阅读(4949) 评论(0) 编辑收藏举报

会员力量，点亮园子希望

刷新页面返回顶部

黄树超

非典型嵌入式行业从业者；C/C++，Linux/Android

ubi问题总结

ubi问题总结

挂载成功有时出现：

ubifs_read_node 报错，还会有类似oops的错误

I see this UBIFS error: "validate_sb: LEB size mismatch: 129024 in superblock, 126976 real"

UBI headers position