Kernel 4.19 MTD failed CRC error on Samsung NAND
Jupiter
jupiter.hce at gmail.com
Sat Jul 31 18:13:40 PDT 2021
Hello,
I am able to run kernel 4.19 to boot Winbond W29N02GVSIAA, due to
unavailable Winbond NAND, I switched to use Samsung K9F2G08U0D-SCB0
but failed UBI:
=> ubi part storage
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0 error: vtbl_check: bad CRC at record 2: 0x9832d5d9, not 0x2a015d08
Volume table record 2 dump:
reserved_pebs 496
alignment 1
data_pad 0
vol_type 1
upd_marker 0
name_len 13
name rootfs-volume
crc 0x2a015d08
ubi0 error: vtbl_check: bad CRC at record 2: 0x9832d5d9, not 0x2a015d08
Volume table record 2 dump:
reserved_pebs 496
alignment 1
data_pad 0
vol_type 1
upd_marker 0
name_len 13
name rootfs-volume
crc 0x2a015d08
ubi0 error: process_lvol: both volume tables are corrupted
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd1, error -22
UBI error: cannot attach mtd1UBI error: cannot initialize UBI, error -22UBI ini2
The difference between Winbond W29N02GVSIAA and Samsung K9F2G08U0D-SCB0 are:
(a) use different ECC bit lengths which I can manage.
(b) Samsung uses on-chip ECC
Does MTD support on-chip ECC NAND? Or what could I be missing?
Appreciate your help.
Thank you.
Kind regards,
Jupiter
More information about the linux-mtd
mailing list