StrangeOrange wrote:admitr2 wrote:May be you know, why completely power off and power on - configuration loaded to default?
For some reason the JFFS2 filesystem was not initialized properly:
[ 44.470000] jffs2: Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
Reflashing the firmware again should solve this problem (it always did for me). If not, other options include erasing the partition before flashing the new firmware or building a custom image with an increased padding size.
Unfortunately re-flashing not help to me. Can you detailed write about "other options include erasing the partition before flashing the new firmware"?
Are you flashing it according to the instructions in my post or using some other way?
What are the exact steps that you do?
What was the previous firmware that you had on the router?
Did you run jffs2reset -y beforehand?
Option #1: Run mtd erase firmware and then flash.
Option #2: Pad the firmware image with 0xff to size 0xf80000 (16252928) bytes, and then flash the modified image. This can also be done by changing the BuildFirmwareImage.sh script in the patch source.
Either should be enough on its own but I've never had the chance to try them. Option #1 is the fastest but if you cannot flash the new firmware after you already erased the previous one, for example because you are disconnected or the power goes off, the router will not start again and you'll need to recover from this situation through some other way, for example using the Breed bootloader.
If you're not comfortable with the above, there's also yet another, roundabout way that should work:
Option #3: Flash an older, smaller version, say r1216 U2. Make sure the /overlay filesystem is set up correctly there, and then flash the newest image again.
(Last edited by StrangeOrange on 4 Feb 2016, 05:37)