Jeremy Davis's picture

Yeah it does seem related to if/when it's not closed "cleanly". Although I'm not really sure why it seems to happen reliably on first reboot after install - and so far, only seems to affect the Redmine appliance. It's bizarre!

As per you, I also tried a raft of "fixes" and some seemed to work, but not consistently or reliably. Nuking all the MariaDB data, reinitializing the MariaDB setup and reloading the Redmine data was the only thing that seemed to work reliably.

TBH while my script does seem to work and it didn't corrupt for me again on multiple reboots, I would really like to understand why it happens in the first place. Then I can be assured that it won't happen under "normal" circumstance.

Obviously I can't guarantee it'll never happen again. Data corruption does happen sometimes - hence why backups are always a must. Although it should generally only happen under specific circumstance, such as hardware corruption/failure - e.g. faulty RAM or disk corruption. And it certainly shouldn't happen to all or even most Redmine users of our v18.0 build on firstboot!