faffe

Aaaand a few seconds after submitting that post, a disk died. Perhaps that was the problem all along? Will be working on replacing/rebuilding, we'll see if the database corruption disapperars.

Yeah, I saw that, but my limited Unraid experience means I'm not sure what's "normal". The "invalid" line seems fishy. Fixed after fiddling with the schedule of theauto updater plugin. The sqlite database is regularly corrupted, runs a few days at best. # Generated btrfs balance data schedule: 0 0 1 * * /usr/local/emhttp/plugins/dynamix/scripts/btrfs_balance start /mnt/data -dusage=50 &> /dev/null # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check &> /dev/null # Generated languages version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/languagecheck &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 0 */1 * * * /usr/local/sbin/mover start &> /dev/null # Generated parity check schedule: 0 7 * * * /usr/local/emhttp/webGui/scripts/parity_control pause &> /dev/null 0 2 * * * /usr/local/emhttp/webGui/scripts/parity_control resume &> /dev/null 0 2 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated TRIM schedule: 0 7 * * * /usr/local/emhttp/plugins/dynamix/scripts/ssd_trim cron|logger &> /dev/null # Generated Unraid OS update check schedule: 11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated cron settings for plugin autoupdates Invalid frequency setting of /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # CRON for CA background scanning of applications 55 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 # Crontab for Disk Location plugin to retrieve SMART data, power status and run backup in the background. 56 */12 * * * php -f /usr/local/emhttp/plugins/disklocation/pages/cronjob.php start silent &> /dev/null */5 * * * * php -f /usr/local/emhttp/plugins/disklocation/pages/cronjob.php start status silent &> /dev/null */5 * * * * php -f /usr/local/emhttp/plugins/disklocation/pages/cronjob.php start syslogread silent &> /dev/null 0 0 * * * php -f /usr/local/emhttp/plugins/disklocation/pages/page_system.php backup auto silent &> /dev/null 0 5 1 * * php -f /usr/local/emhttp/plugins/disklocation/pages/benchmark.php auto silent &> /dev/null

Thanks. I generated the diagnostics when the sqlite corruption happened again, also attaching come Crafty4 logs, not that they seems to say much except that the database is corruptcrafty database corruption.logcrafty sqlite3 integrity check.logcrafty support_logs.zipzimacube-diagnostics-20250226-2135.zip

I'm a new Unraid user who is starting to question my life choices. I have tried installing a few docker apps, that report sqlite database corruption after running for a few hours or days. Most recently binhex-crafty-4. Ran fine for a while, kid happy, bot now the log says "peewee.DatabaseError: database disk image is malformed". No power outages or other issues detected. I started on Unraid 7 to avoid a major version upgrade as the first thing to handle. Is this sort of thing common on Unraid? I would like to think that file integrity would be one of the highest priorities for Unraid.