Could not save configuration changes, read-only file system detected

RouterOS General
1

CCR1009-7G-1C-1S+ RouterOS v7.19.1 shows this message in logs:

system,error,critical could not save configuration changes, read-only file system detected.

This router is a PPPoE concentrator with 800 users connected
i think the source of the problem comes from that by mistake tool graphing interfaces was enabled for all interfaces storing it to disk :speak_no_evil_monkey:

in system resources storage state show this:

free-hdd-space: 67.2MiB
write-sect-since-reboot: 11905027
write-sect-total: 58550072
bad-blocks: 0%

there is a way to solve this without going to site to do netinstall procedure?

2

I have a similar scenario, RB750 running 7.16.1, currently behind a Starlink at a remote site.

Interestingly, changes to the configuration can be done, and /tool/graphs are being stored to disk, updated, and are viewable

There is no warning, and the only external symptoms are that /file/print always return empty, and userspace access to the filesystem fails:

 > /file/print detail 


> export file=test
invalid file name

Also, no Bad-Blocks, and mine is not a case of the "graphing" process hogging 100% of the CPU due to corrupted RRD store

                   uptime: 4w3d2h33m14s
                  version: 7.16.1 (stable)
               build-time: 2024-10-10 14:03:32
              free-memory: 25.1MiB
             total-memory: 64.0MiB
                      cpu: MIPS 24Kc V7.4
                cpu-count: 1
            cpu-frequency: 400MHz
                 cpu-load: 12%
           free-hdd-space: 47.7MiB
          total-hdd-space: 64.0MiB
  write-sect-since-reboot: 351972
         write-sect-total: 4184135
               bad-blocks: 0%
        architecture-name: mipsbe
               board-name: RB750
                 platform: MikroTik

/export to terminal is possible,
but /system/backup/save fails due to no userspace file writes being possible.

I haven't messed much with this, being a remote site.
Currently scheduled for "substitute with netinstalled new box at the next visit"

I've also had several cases of the corrupted RRD store variety, "graphing" process hangs, consuming 100% of one core, and breaking /export .

The fix for those , is temporary reboot to allow for /export, and netinstall to reformat RRD store.

But this "fix" is temporary, because (over several tickets) Mikrotik never pointed to the root-cause, or provided a runtime way to fix this corrupted state... and eventually this will happen again

Kind of like "cosmic karma" throwing a "now go schedule a Netinstall" in your lap.

3

I would not even try an onsite netinstall.... go to the site with a new device and bring this one back to see if it can be recovered/repaired.