(21.08.2025, 13:33)managementboy Wrote: I can't access the System Config since I flashed the beta... get a 404 error

(21.08.2025, 13:35)Daniel Wrote: Cache? Did you try accessing via manual url typing? http://192.168.0.10/flashsys

(25.08.2025, 10:24)Daniel Wrote: Looks like you must flash the card. Something got corrupted.

(02.09.2025, 11:19)managementboy Wrote:

(25.08.2025, 10:24)Daniel Wrote: Looks like you must flash the card. Something got corrupted.

do you have a How To? best if I don't loose all the work I've got on it

(05.09.2025, 12:55)managementboy Wrote:

(02.09.2025, 11:19)managementboy Wrote:

(25.08.2025, 10:24)Daniel Wrote: Looks like you must flash the card. Something got corrupted.

do you have a How To? best if I don't loose all the work I've got on it

I get this error

• “System start” entries (reboot log list)
  
• Daily trend charts showing flat segments after a reboot
  
• System load (CPU/RAM) view
  
• Alertas.
  

• Device: LogicMachine Lite IMx6 (2023) with SD storage mounted 
  
• Power: controller fed by a UPS (no brownouts)
  
• Firmware tested:
  • 2025.08 → many more reboots per day
    
  • 2024-04-26 → noticeably fewer reboots with the same project
    
• Workload: trends enabled (we’ve heavily reduced the number and retention)
  

• After a reboot, trends often show a flat line (last held value) until the next internal save.
  
• On 2025.08 we see frequent “System start” entries, whereas 2024-04-26 is more stable.
  
• CPU and RAM look normal in the system load page (no clear overload).
  
• SD card looks healthy: mounted, writable, plenty of free space; simple write/read checks pass.
  
• Power is stable (UPS).
  

• Reduced the number of trends and long retentions to rule out storage/retention pressure.
  
• Compared behavior across two firmware versions (2025.08 vs 2024-04-26).
  
• Basic SD diagnostics (mount state, free space, simple writes)—no obvious errors.
  
• Checked system load—no spikes that correlate with reboots.
  

• Compared with the older behavior (save once per 24 h at midnight), the system now seems to write trend data more frequently, which is good—but unexpected reboots still create gaps/flat segments until the next save.
  
• Reboot cadence is significantly higher on 2025.08 for us.
  

• Nov 3–4: Tested on LM 2025.08 with the full set of trends enabled. Result: numerous spontaneous reboots across both days (see Alerts.gif
  → “System start” entries).
  
• Nov 13: Upgraded again to LM 2025.08, this time with almost all trends removed to rule out load/retention. Result: the reboot pattern persisted—multiple restarts per day despite the minimal trend load.
  
• Nov 15 ~22:00: Rolled back to LM 2024.04.26. Under the same conditions (UPS power, SD verified OK, same project minus cosmetic changes), reboot frequency dropped noticeably and the unit behaved much more stably.