No automatic reboot after resetting settings

Installing and Using OpenWrt
1

Hi!
On my TP-Link Archer C6 v2 EU, the automatic reboot after resetting the settings (System->Backup and flash firmware->Perform reset) does not happen and the settings reset only happens after I reboot the device manually. I can reproduce this issue.

OpenWrt 23.05.5 (r24106-10cc5fcd00) / LuCI openwrt-23.05 branch (git-24.264.56413-c7a3562) with an image created by the OpenWrt Firmware selector. Additional packages: strongswan-minimal wpad-mbedtls

Relevant logs:

Sat Nov  9 15:32:19 2024 daemon.info jffs2reset: /dev/mtdblock5 is not mounted
Sat Nov  9 15:32:19 2024 daemon.info jffs2reset: /dev/mtdblock5 will be erased on next mount

Is this a known issue? I think this worked fine in OpenWrt 23.05.3.

2

Does the behavior also occur if you use a completely default release build (no added packages)?

3

No, a default release build without any added packages does not exhibit this issue. I'll try a build from the firmware selector with an unchanged package list next.

4

A build from the firmware selector with unchanged package list doesn't have the problem either.
The only lead I have so far is that installing my additional packages after booting the build from the firmware selector seems to fail due to insufficient space.

5

The custom image shouldn't even be able to install if it is too big (in fact, the image should fail to build).

If you start with a default image install, and then attempt to install those packages using opkg install, does it fit, and does the reboot issue manifest?

6

Nope, strongswan-minimal doesn't install. Well, it does say 1.54 MiB required for the installation, total disk space is 1.31 MiB, so in theory the installation should be rejected before it even starts. However, the installation proceeds and fails in the middle with "no space left on device" and a subset of packages is installed. Installing the full wpad-mbedtls after that made no sense since the flash was already full.

7

Ok... the reason the custom image fits is because it is compressed (squashfs), but it looks like you're really at the edge here.

Back on your customized image, I'm not really sure why reboot isn't working, but it could be related to an improperly configured daemon or something.

Maybe build your image with just one of the two packages to see which one is causing the problem.

8

Strangely building the image with just one of the packages didn't result in the same problem, just if both were active. Even after multiple attempts with different package combinations I was unable to discern a pattern aside from "image might be on edge from a size perspective". In the end, I moved to hardware with more flash storage which works perfectly well with the same package selection.

Thanks again for the helpful pointers @psherman !

9

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.