jffs2: wrong data CRC in data node at

[bibikalka]

Started getting these CRC messages during reboots, 1 per reboot:

admin@RT-AC86U-9988:/# grep CRC messages-20231203
Dec  1 04:05:10 kernel: jffs2: notice: (1110) check_node_data: wrong data CRC in data node at 0x02cd2874: read 0x57c3845c, calculated 0xd86ecad6.
admin@RT-AC86U-9988:/# grep CRC messages
Dec  1 04:05:17 kernel: jffs2: notice: (360) check_node_data: wrong data CRC in data node at 0x02cab298: read 0xd765beb5, calculated 0x3bd17671.
Dec  1 04:05:07 kernel: jffs2: notice: (360) check_node_data: wrong data CRC in data node at 0x00e27b34: read 0xa787e4e7, calculated 0x66ebf91b.
Dec  4 04:05:11 kernel: jffs2: notice: (1110) check_node_data: wrong data CRC in data node at 0x01a12f8c: read 0x1a757116, calculated 0xe39c1e96.

I am thinking - with appropriate reboots:
scripts off
backup /jffs
reformat /jffs
restore jffs contents back
scripts on

I had good success hammering NVRAM in another router to set flash straight, so I'd hammer /jffs, but I think it's not easy. Perhaps 2-3 reformats? Once the router is booted, /jffs is usually mounted, so it's not possible to hammer it like I could do with NVRAM here:

AC68u fast blinking power light from time to time (nvram issue)

I have this flaky AC68u which from time to time totally forgets its NVRAM. Usually power light is blinking rapidly. I can usually restore the router after multiple attempts of pressing WPS button upon turning on. It'll come back up fully factory reset. But it'll forget again soon. I am using...

www.snbforums.com

Other thoughts?

 

[bibikalka]

I tried to see if there is anything obvious with /jffs. Below is some output from the nice utility here:

mtd_check - an application to give information and scan mtd partitions

After reading about another member that experienced jffs issues, there was a pointer to some links about mtd devices. One of them had a small application that would print out information about a flash/nand partition - nand_check. I downloaded the code and did various updates/addons that...

www.snbforums.com

The only obvious thing is lots of blocks are partially occupied. But no bad blocks are reported. So on paper everything is good.

admin@RT-AC86U-9988:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 05aa0000 00020000 "rootfs"
mtd1: 05a80000 00020000 "rootfs_update"
mtd2: 00800000 00020000 "data"
mtd3: 00100000 00020000 "nvram"
mtd4: 05f00000 00020000 "image_update"
mtd5: 05f00000 00020000 "image"
mtd6: 00460000 00020000 "bootfs"
mtd7: 00480000 00020000 "bootfs_update"
mtd8: 00100000 00020000 "misc3"
mtd9: 02f00000 00020000 "misc2"
mtd10: 00800000 00020000 "misc1"
mtd11: 0557e000 0001f000 "rootfs_ubifs"
admin@RT-AC86U-9988:/# df |grep jffs
/dev/mtdblock9           48128     25660     22468  53% /jffs
admin@RT-AC86U-9988:/# /jffs/scripts/mtd_check -V /dev/mtd9
Version: 0.9
admin@RT-AC86U-9988:/# /jffs/scripts/mtd_check -v /dev/mtd9
Flash type of /dev/mtd9 is 4 (NANDFLASH)
Flash flags are 0x400 - WRITEABLE
Block size 131072 (128K)  Page size 2048 (2K)  OOB size 64
Device: 49283072 (47M) bytes, 376  blocks
MTD Stats:  Bad Blocks: 0  ECC Corrected: 0  ECC Uncorrected: 0

No Region Information on device
B Bad block; . Empty; - Partially filled; * Full; R Reserved (BBT); S has a JFFS2 summary node

*****.****.****..**.*.******.****.*****.****.**.*******...**..*******.**********
***.***.*..****.****.*****..*.********..*********.*.****..***.*..******.***.****
.****.*.**.***.****.*************.*****..****..***..******.***********.********.
.**..****.****************..****.*********.*******.************.*****.****..****
****************************-***.*.***.*..******.*.*****
Summary /dev/mtd9:
Empty Blocks: 73, Full Blocks: 302, Partially Full: 1, Bad Blocks: 0, Reserved Blocks (BBT) 0