cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
252 Views
Registered: ‎03-27-2019

ubi0 error: vtbl_check: bad CRC at record 1: 0xe7aa8d6d, not 0xf116c36b

my nand part number is MT29F4G08ABAFAWP-AAT:F

I want to attach mtd1 to ubi.

after booting, I tried ubiattach on version 4.19 of Linux.

when i try ubiattach, why occured issue?

i'm using petalinux 2019.2. when i'd used petalinux 2018.3, there is no issue such as this.

in 2019.2 project, petalinux kernel config is same petalinux 2018.3.

in 2019.2 project, i'd set MTD, UBIF same such as petalinux 2018.3 project config.

hw is zynqMP custom board.

hw is same in petalinux 2019.2 project and petalinux 2018.3 project.

I simply changed the Petarinux version, leaving the hardware intact.

Of course, the fpga image may have changed, but I think it has nothing to do with this phenomenon.

my kernel log is below.

root@2019:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 0a000000 00040000 "nand-boot"
mtd1: 15000000 00040000 "nand-app"
root@2019:~# ubiformat /dev/mtd1
enter code hereubiformat: mtd1 (nand), size 352321536 bytes (336.0 MiB), 1344 eraseblocks of 262144 bytes (256.0 KiB), min. I/O size 4096 bytes
libscan: scanning eraseblock 1343 -- 100 % complete
ubiformat: 1344 eraseblocks have valid erase counter, mean value is 0
ubiformat: formatting eraseblock 1343 -- 100 % complete
root@2019:~# ubiattach /dev/ubi_ctrl -m 1
[ 1845.819118] ubi0: attaching mtd1
[ 1846.696783] ubi0: scanning is finished
[ 1846.731907] ubi0 error: vtbl_check: bad CRC at record 1: 0xe7aa8d6d, not 0xf116c36b
[ 1846.732888] Volume table record 1 dump:
[ 1846.733388]  reserved_pebs   0
[ 1846.733792]  alignment       0
[ 1846.734195]  data_pad        0
[ 1846.734598]  vol_type        0
[ 1846.735001]  upd_marker      0
[ 1846.735412]  name_len        0
[ 1846.735818]  name            NULL
[ 1846.736260] ubi0 error: vtbl_check: bad CRC at record 1: 0xe7aa8d6d, not 0xf116c36b
[ 1846.737239] Volume table record 1 dump:
[ 1846.737739]  reserved_pebs   0
[ 1846.738142]  alignment       0
[ 1846.738543]  data_pad        0
[ 1846.738946]  vol_type        0
[ 1846.739357]  upd_marker      0
[ 1846.739759]  name_len        0
[ 1846.740160]  name            NULL
[ 1846.740599] ubi0 error: ubi_read_volume_table: both volume tables are corrupted
[ 1846.741690] ubi0 error: ubi_attach_mtd_dev: failed to attach mtd1, error -22
ubiattach: error!: cannot attach mtd1
           error 22 (Invalid argument)

 

0 Kudos
2 Replies
Highlighted
Visitor
Visitor
174 Views
Registered: ‎06-07-2018

Hello Lim Junhyoung,
This seems like a returning issue with the 2019.2 driver.

please check https://forums.xilinx.com/t5/Embedded-Linux/Arasan-NAND-controller-Suspected-DMA-problems-in-Petalinux-2019/td-p/1050954

Kind regards,

 

Tom

0 Kudos
Highlighted
Adventurer
Adventurer
167 Views
Registered: ‎03-27-2019

thank you!!
0 Kudos