MikroTik

Hi,

Recently my Chateau LTE12 - ROS 7.11.2 (stable) has started to lose my configuration when rebooted. For example, I have a number of static DNS entries which keep being deleted on each reboot.

They are definitely being added, as I can use them and it shows " static dns entry added by $user" in the logs, but as soon as I reboot these all disappear! Strangely the DHCP static leases and other settings are fine after a reboot.

Also another weird log entry is "router was rebooted without proper shutdown, probably kernel failure" when I know for sure I rebooted via the Mikrotik Andriod app or the web UI. So why has my router suddenly started playing silly beggars and more importantly, how to I fix it!?

Confirmed.
hAP ax^2 configured router with 4 Vlans, Wifi e.c.

After 6 hours plugged out to transfer to another location , powered on and ...
no Vlans , wifi settings so config resets to some point before my configuration

ROS 7.11.2 (stable)

P.s. in LOG just usual message when powerOff: router rebooted without proper shutdown, probably power outage

I have same model and ROS version, none of these issues occurs. Maybe some configuration or connected peripherals affects stability?

This issue is doing my head in. Now every-time I reboot or have a power cut, the router won't boot. I have to take it down from the roof space and reset the configuration EVERY time now. Once I reset the config and boot into default config, I can restore from backup and everything works fine until the next power cut or reboot.

There must be something wrong with my config, but I don't know what it is! I've basically had the same config for years, across a number of Mikrotik devices and only having problems with it now!

I can restore from backup

Just an idea: try to restore from export, not from backup. Backup (the binary configuration itself) could be corrupted.

Also, check free disk memory. If it is near zero it could cause these problems.

I would even suggest netinstall and then import earlier exported config line by line, really scrutinizing what goes in again.
Depending on what happened to that device in the past, some rogue bits and pieces of config may be lurking around causing havoc.