My ZimaOS crashes every few days (sometines hours) due to an index error. For example the immich database location /media/…/pg_stat_tmp/global.stat: “Error 1064 (42000): table zimaos_files: parse error: unknown column: i”, “func”. This error repeats every few seconds and in multiple index locations in my /media/…/ folder and spams my log files until its crashes.
Any ideas of how to fix that table issue with the unknown column?
To better help you, let me check a couple of things here.
What’s the version of your ZimaOS? What are the specs of your machine?
How did you find that error info like: “Error 1064 (42000): table zimaos_files: parse error: unknown column: i”, “func”.
Could you please provide the screenshots of this error?
Look forward to your feedback.
The ZimaOS was v1.4.1 (until I updated to v1.4.2 today). I was reading out the log before the crash (last 100 lines in the log, from last boot). I can PM the last 100lines if needed.
Also there was an issue with ‚getent shadow root’. This was triggered every few seconds.
Hope this helps.
Sorry, to better help you, please follow my questions.
What are the specs of your machine?
How did you find that error info like: “Error 1064 (42000): table zimaos_files: parse error: unknown column: i”, “func”. Like, in which screen? Use what tools?
Could you please provide the screenshots of this error?
Hi, sorry I was on holiday.
The ZimaOS is constantly crashing everytime after 2-3 days, without a user interaction. During holidays I was trying to remotely access the ZimaOS through tailscale, but the zima wasn´t reachable and appeared offline. After coming back from holidays I have hard-restarted the device by pulling the cable. It crased again this week without any specific reason. I could not find that error again, which I have seen before. I have a Zimablade 3760 installed with ZimaOS.
I have reviewed the logfile with this command: journalctl -b -1 (and some minor variations to get only the last x amount of lines).
Any tipps? Thanks. Flo
My current advice is to first ensure your system is updated to the latest stable version. Secondly, whenever an error occurs, take screenshots of as many of the remaining parts as possible. This helps you pinpoint the specific issue, rather than just the perception of a system problem. Once all issues are resolved, you’ll have a much smoother operating experience. Please believe that all engineering-related problems can be solved.