Hi there,
I'm trying to build an embedded NAS device using OMV, and need to protect the microSD card from corruption during power-off, which CANNOT be done cleanly, based on the environment it is being deployed in.
The idea is to configure the system for accessing single usb mass storage device, which will only ever be read from, and never written to. The configuration will stay as-is for as long as the device is deployed (indefinitely), to periodically access the read-only data on the usb drive, i.e. power up, grab data, power down (not clean, simply cut power).
So, /var/run and /var/log will be set up as tmpfs (not concerned about holding onto logs). All partitions will have 'noatime' enabled (to disable any writing after reads), and swapping will be disabled (don't need it anyhow, plenty of ram available).
Ideally, after the initial configuration, I would like to mount the root filesystem as readonly, which should fully protect the microSD card. However, is this possible when running OMV, if we don't need to change the configuration? Is there some other functionality that causes OMV to write to the root filesystem, e.g. caches or logs, and can I also point them to tmpfs or /dev/shm? If I wasn't able to run OVM on a fully read-only filesystem, perhaps there is a way to minimize writes so when they happen, they are expected (e.g. say if we did want to allow configuration changes, we would make sure the configuration write was complete before cutting the power.)
Any insight would be appreciated!