OSMC crash during backup creation and other operations

Help and Support Vero 4K / Vero 4K +
1

Hello everyone,

I’m aware that my device is not supported any more, but I’m hoping for some pointers in narrowing the issue down.

I’ve got a Vero 4 running as my media center for a while now (pre 2018). I’ve using the advanced settings to store my database in a mariadb on a synology NAS. The mariadb is run as a docker container.

Recently, during certain operations (e.g. scanning new files into the library) but also during creation of a backupt, OSMC crashes and reboots. Occasionally it did so multiple times as soon as I navigated to the respective show/movie.

I’ve detached the vero from the power for a few hours and restarted the mariadb container and everything went back to normal (ish).

Yesterday I wanted to do a backup through “my OSMC” and it crashed again. Interestingly the last automatic backup before that (04.03.2026) was successful. Once I’ve selected addons for the backup the backup ran through but obviously is was smaller now (without all the addons).

Frankly, I don’t really care too much about the addons. I believe the only meaningful one is a skin. I’m more worried about a general issue, that I want to narrow down and the backup is the most reliable way to maybe narrow it down.

Anyhow, I’ve repeated the issue on the backup (with activated debugging) and uploaded the logs here: https://paste.osmc.tv/nidefulojo

Now a few ideas of what could be the problem:

  • database size and response times and kodi 21.1 not handling it properly ?
  • hardware wear and tear?
  • anything in the log, I’m not able to identify?

I’m trying to figure out, what the issue could be, neither vero nor nas nor db has changed as far as i know in the last 2 years. the only thing was the extension of the data base.

Thank you for any ideas that I could try.

2

Your log isn’t showing Kodi crashing.
Is it possible you rebooted to upload the log?

Sam

3

I’ve (think) I’ve done the following steps:

  1. Activate Debug
  2. Start the Update
  3. Crash + automatic reboot of Vero
  4. Upload of the Log

I was not aware that the reboot “cleans” the log. Since it is happening as part of the crash, how can I prevent it? And I probably need to extract the logs through SSH then?

I can retry tomorrow (Thursday) evening, since I’m not close to the vero right now.

Thank you,

Drunal

4

Hello Sam,

I’ve now performed the following steps:

  • Restarted the Vero
  • Activated Debug
  • Performed the Update → Crash + Restart
  • Uploaded the Logs
  • Deactivated the Debug.

You can find the logs here: https://paste.osmc.tv/guxuvogimu

I’ve also done the same before without the manual restart and OSMC then told me that the log is too big for the upload, so I saved them to the SD card and can retrieve them via SSH if needed.

5

Update:

Yesterday, Vero crashed during scrolling/navigating through the library.

I’m kinda looking into wether it is something on my setup (which has not changed since I bought the Vero) or whether it is wear & tear, memory or something, that a Vero V would solve.

However, while I had “debug” activated I did not notice that RAM or CPU usage spiked unexpectedly.

Anything visible, which could give some pointers, in the log that I’ve uploaded?

6 
2026-04-05 22:23:37.852 T:2956  warning <general>: FileNFS::OpenForWrite() called with overwriting enabled! - //Projekte/Raspberry Pi - Vero/OSMC/VEROBackups/temp_write_test

Thx. So, you’re making backups on an NFS location using the NFS stack of the mediacenter. I vaguely recall a problem when trying to back up to Kodi NFS paths if the file size exceeded 2 GB. I don’t know if this was ever fixed.

You should be able to get an update through if you disable settings -> system -> my osmc -> updates -> backups -> backup before each backup. Then retry the update.

I can’t say what updates will be released for this device after that (the last update of your system was on March 7, 2025), or whether this problem will be resolved by them.

As a precaution, you can check the /home/osmc/.kodi/temp directory for any orphaned OSMCBACK... files. You should definitely delete these.

To avoid the NFS path in this area of the mediacenter, setup an NFS mount point using autofs or fstab and use the local mount point in my osmc -> -> updates -> backups as target location.

7

Thank you for the input.

The last successful backup was done on 04.03.2026, and it is ~700MB big. so the 2GB does not seem to be an issue.

I’m not too worried about the updates (since there won’t be many), but it was one location where I could reproduce the crash. And it also involves the network in some way.

As said, yesterday it crashed while navigating through the library, but I can’t reproduce this reliably.

Do you see anything else in the logs that could give me any pointers?

Thank you

8

Hello everyone,

short update: the Vero 4 did work for a while okayish. Yesterday it crashed and restarted multiple time shortly after each other. After 4-5 crashes/restarts I switched to a different input on my tv and let it do its thing.

When I came back later this evening, the skin has “changed”. Not completely different but more like updated version of my used skin. (using Arctic Zephir - reloaded).

I’ve also switched to the standard OSMC skin before to check whether that fixes the crashes, but it did not.

Howerver, since then it runs without issues again. Just like if it knew that one day prior i’ve ordered a Vero V and it now wants to show me, that everything is still good. I’ve ordered the V5, because I’m suspecting a hardware issue on my V4 at this point, due to the unpredictability of the crashes.

All the best

/edit: … and I was too optimistic. Its going down again unpredictably.