Modify

Opened 8 years ago

Closed 6 years ago

Last modified 3 years ago

#6415 closed defect (worksforme)

"JFFS2 notice: (225) check_node_data: wrong data CRC" after writing to flash and reboot

Reported by: nenad@… Owned by: developers
Priority: highest Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: Cc:

Description

Writing to flash (opkg install, config file modification, etc) and rebooting device afterwards often brings up CRC data errors:

JFFS2 notice: (225) check_node_data: wrong data CRC in data node at 0x001f32fc: read 0x678eb416, calculated 0xfaf6a910.

Device is UBNT routerstation.

Attachments (0)

Change History (8)

comment:1 Changed 8 years ago by mmitar@…

I also got errors to serial console while upgrading Fonera:

Appending jffs2 data to from /tmp/sysupgrade.tgz to rootfs...
Node CRC 0003bb64 != calculated CRC fd148b6d for node at 002112fc
Node CRC 0003bb64 != calculated CRC 33a006cf for node at 0021621c
Node CRC 0003bb64 != calculated CRC 64a98a76 for node at 002169d0
Node CRC 0003bb64 != calculated CRC 2c040660 for node at 00217154
Node CRC 0003bb64 != calculated CRC cd00a185 for node at 002188e8
Node CRC 0003bb64 != calculated CRC e5872e43 for node at 00219200
Node CRC 0003bb64 != calculated CRC 45d34f4d for node at 00219ae0
Node CRC 0003bb64 != calculated CRC 1168b0c1 for node at 0021a20c
Node CRC 0003bb64 != calculated CRC 343aa3c0 for node at 0021aa10
Node CRC 0003bb64 != calculated CRC 1030d99e for node at 0021b39c
Node CRC 0003bb64 != calculated CRC d54110ad for node at 0021b9e0
Node CRC 0003bb64 != calculated CRC 33a006cf for node at 0021621c
Node CRC 43a8d36f != calculated CRC 848a6f24 for node at 0007dcd0
Node CRC ec6c8a2f != calculated CRC af2ebf76 for node at 0007e4c8
Node CRC c944f712 != calculated CRC 51196842 for node at 0007eb80
Node CRC 26bb9366 != calculated CRC 7e301ff3 for node at 0007f1cc
Node CRC 0fb058b0 != calculated CRC ff0edb5c for node at 0007f8e0
Node CRC 9590188e != calculated CRC 9b227cae for node at 0007fc78
Node CRC 093d490f != calculated CRC 0e9f8473 for node at 000803d8
Node CRC ccb93d2c != calculated CRC 1fc5437e for node at 00080800
Node CRC 34080182 != calculated CRC df678c60 for node at 00080d38
Node CRC 3a742404 != calculated CRC dd9b6143 for node at 00081184
Node CRC 3d948235 != calculated CRC 4217c0f1 for node at 0008159c
Node CRC 5e190386 != calculated CRC 92c2da06 for node at 00081b58
Node CRC 6b4a907a != calculated CRC daa921d6 for node at 00082ca0
Node CRC d9f4c10f != calculated CRC 0ebd7f1c for node at 00083598
Node CRC 093d490f != calculated CRC 0e9f8473 for node at 000803d8
Node CRC 3a742404 != calculated CRC dd9b6143 for node at 00081184
Node CRC ccb93d2c != calculated CRC 1fc5437e for node at 00080800
Kernel panic - not syncing: Attempted to kill init!
Rebooting in 3 seconds..

But after reboot everything seems to work and there were no errors.

comment:2 Changed 7 years ago by anonymous

Is this a hard reboot (via reset switch or powercycle), or soft reboot (shutdown -r within terminal)?

If this happened with a software reboot, it suggests that the filesystem wasn't properly unmounted. If this happened during a hardware reboot, all bets are off.

comment:3 follow-up: Changed 7 years ago by Mitar

It is during an upgrade. Not reboot. So first you start doing upgrade. Then those errors are issued. And after that system reboots itself.

comment:4 in reply to: ↑ 3 Changed 7 years ago by anonymous

Replying to Mitar:

These messages can happen whenever the system was powered off without flushing pending changes completely to the flash. Usually they are harmless.

See http://www.linux-mtd.infradead.org/faq/jffs2.html#L_messages

comment:5 Changed 7 years ago by Mitar

Yes, but while flashing/upgrading the system? Why would then this happen?

comment:6 Changed 6 years ago by nbd

  • Resolution set to worksforme
  • Status changed from new to closed

these errors should be gone in recent versions

comment:7 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:8 Changed 3 years ago by devendranaga4@…

What was the fix then ? Can some one paste a patch to the fix ?

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.