Alright, not sure why it took me this long to notice, but for a few months I've been shown the error in the title of this post on my fix-common-problems report.

I found that the backup of my flash from the day before it started does not have the corrupt file - not sure if other files are corrupt on the previous backups and I don't know if the error began happening due to some action somewhere else 🤷‍♂️

In any case, there appears to be a few more errors in the logs potentially with my btrfs mirrored ssd cache-pool, which is not really used for anything at the moment but I have been looking to update to move my boot from a USB thumb drive to the SSD.

I only noticed this error because I noticed that reordering my docker images didn't seem to stick, and one of my docker containers could not be upgraded.

I would like to think I could just find a thumb drive and restore a non-corrupted backup to it and be on my way, but my concern is that the backup may be too far out of date for any recent changes I may have made, which shouldn't include any array configurations.

Anyway, just looking for someone to analyze my diagnostics and advise me on what my next steps ought to be. Should I just overwrite the monitor.ini with an uncorrupted version, and perform a reboot, or is there more to consider?

mimir-diagnostics-20260405-2243.zip

Syslog is being spammed with errors and already rotated. Reboot and post new diags after array start.

You could probably safely just delete (or rename) monitor.ini and let a new one be created by going to Settings->Display and making sure the settings there are what you want and hitting Apply.

The diagnostics should still be supplied to see if they show other issues.

@JorgeB I still have not rebooted because I am unable to disable VMs or Docker, which I would like to be able to do before stopping the array and restarting. I was able to stop all running containers and VMs.

@itimpi I am unable to delete or mv the file "Read-only file system". Updating anything in Setting->Display do not save.

I suppose the only thing to do is attempt to stop the array and reboot and provide another diagnostics after starting the array back up.

Stopping the array from the "STOP" button didn't stop the array, so I selected "REBOOT" which lead to an unclean shutdown of the array. I have attached a diagnostics from before starting the array after reboot and another after I started the array. It appears one of my SSD's in my cache pool no longer exists 😢

The monitor.ini is readable again.

Parity check is running.

Let me know if anything about the diagnostics requires attention.

mimir-diagnostics-20260407-1544.zip mimir-diagnostics-20260407-1548.zip

Apr 7 15:38:57 Mimir emhttpd: error: put_config, 577: Read-only file system (30): fopen: /boot/config/ident.cfg.new

Flash drive is read-only, try running chkdsk on it or backup and recreat it.

Booted onto a live disk of system rescue 13 and ran dosfsck -l -v -a -t /dev/sdi1 rebooted and my ssd showed up for my cache pool. Running a parity check. I'm able to add/edit/order docker containers, settings are saving, etc. So all appears okay for now. I'll continue monitoring.