Solve the problem of settings not being saved after restarting the OpenWRT router

shihabsayed11 · February 18, 2024, 7:41pm

Solve the problem of settings not being saved after reboot the OpenWRT router

psherman · February 18, 2024, 7:52pm

There isn't enough information to help you.

Let's start here:

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:

ubus call system board
df -h
mount

frollic · February 18, 2024, 7:53pm

Ubiquity ?

github.com/openwrt/openwrt

Ubnt Nanostation AC loco fails to store config after upgrade to 23.05

opened 02:48PM - 20 Oct 23 UTC

closed 11:44AM - 24 Dec 23 UTC

pswilde

bug

### Describe the bug I have many Ubiquiti Nanostation 5 AC loco devices, that… have been running 22.03 fine for ages. I thought I'd try upgrading to 23.05 but it appears after upgrade configuration cannot be stored. Anything configured is fine at runtime, and operates well while the device is on, but if anything interrupts the power or if the device is manually rebooted, all configuration is lost. I have spare devices, and have reverted one back to 22.03.5 which is again working fine (although I had to use Ubiquiti's TFTP factory image process as downgrading from OpenWRT didn't work.... because a reset just applies the current 23.05 image again) I think it may be something to do with the mounts, but I am by no means an expert here. I have performed an upgrade on two different Nanostation AC locos, one brand new, and the result is the same. Thanks, ### OpenWrt version r23389-5deed175a5 ### OpenWrt target/subtarget ath79/generic ### Device Ubiquiti Nanostation AC loco (WA) ### Image kind Official downloaded image ### Steps to reproduce 1. Flash 23.05 (tried both rc3 and release 23.05) to device 2. Configure anything i.e. system name, password, wireless, dhcp, etc. 3. Reboot 4. Configuration is lost. ### Actual behaviour Device does not keep any information after reboot or power loss ### Expected behaviour Device should persist configuration ### Additional info Output of df -h on **23.05** ``` Filesystem Size Used Available Use% Mounted on /dev/root 4.0M 4.0M 0 100% /rom tmpfs 27.9M 76.0K 27.8M 0% /tmp /dev/mtdblock5 9.3M 9.3M 0 100% /overlay tmpfs 27.9M 84.0K 27.8M 0% /tmp/root overlayfs:/tmp/root 27.9M 84.0K 27.8M 0% / tmpfs 512.0K 0 512.0K 0% /dev ``` Output of df -h on **22.03** ``` Filesystem Size Used Available Use% Mounted on /dev/root 4.0M 4.0M 0 100% /rom tmpfs 28.0M 232.0K 27.8M 1% /tmp /dev/mtdblock5 9.3M 436.0K 8.8M 5% /overlay overlayfs:/overlay 9.3M 436.0K 8.8M 5% / tmpfs 512.0K 0 512.0K 0% /dev ``` Output of cat /proc/mtd on **23.05"" ``` dev: size erasesize name mtd0: 00040000 00010000 "u-boot" mtd1: 00010000 00010000 "u-boot-env" mtd2: 00f60000 00010000 "firmware" mtd3: 00240000 00010000 "kernel" mtd4: 00d20000 00010000 "rootfs" mtd5: 00950000 00010000 "rootfs_data" mtd6: 00040000 00010000 "cfg" mtd7: 00010000 00010000 "art" ``` Output of cat /proc/mtd on **22.03"" ``` dev: size erasesize name mtd0: 00040000 00010000 "u-boot" mtd1: 00010000 00010000 "u-boot-env" mtd2: 00f60000 00010000 "firmware" mtd3: 00230000 00010000 "kernel" mtd4: 00d30000 00010000 "rootfs" mtd5: 00940000 00010000 "rootfs_data" mtd6: 00040000 00010000 "cfg" mtd7: 00010000 00010000 "art" ``` Output of cat /proc/mounts on **23.05** ``` /dev/root /rom squashfs ro,relatime,errors=continue 0 0 proc /proc proc rw,nosuid,nodev,noexec,noatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,noatime 0 0 cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0 tmpfs /tmp tmpfs rw,nosuid,nodev,noatime 0 0 /dev/mtdblock5 /overlay jffs2 rw,noatime 0 0 tmpfs /tmp/root tmpfs rw,noatime,mode=755 0 0 overlayfs:/tmp/root / overlay rw,noatime,lowerdir=/,upperdir=/tmp/root/upper,workdir=/tmp/root/work 0 0 tmpfs /dev tmpfs rw,nosuid,noexec,noatime,size=512k,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,noatime,mode=600,ptmxmode=000 0 0 debugfs /sys/kernel/debug debugfs rw,noatime 0 0 bpffs /sys/fs/bpf bpf rw,nosuid,nodev,noexec,noatime,mode=700 0 0 ``` Output of cat /proc/mounts on **22.03** ``` /dev/root /rom squashfs ro,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,noatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,noatime 0 0 cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0 tmpfs /tmp tmpfs rw,nosuid,nodev,noatime 0 0 /dev/mtdblock5 /overlay jffs2 rw,noatime 0 0 overlayfs:/overlay / overlay rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work 0 0 tmpfs /dev tmpfs rw,nosuid,noexec,noatime,size=512k,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,noatime,mode=600,ptmxmode=000 0 0 debugfs /sys/kernel/debug debugfs rw,noatime 0 0 none /sys/fs/bpf bpf rw,nosuid,nodev,noexec,noatime,mode=700 0 0 ``` If any more outputs will be useful, let me know I will keep a device on 23.05 for troubleshooting for now. I can also test any adjustments if you like. ### Diffconfig _No response_ ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

Wallbanger · February 18, 2024, 8:13pm

wtf?
No crystal ball here, sorry...