Problems with/after update issue Vero 4K +

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

A few days ago, during an automatic update, the update got stuck halfway through, similar to what has been described in the other topics.

The hotfix did not seem to make any difference, and after rebooting, the Vero would get stuck in the update process again.

I eventually modified the sources.list manually. Since then, updates complete without any errors.

deb https://deb.debian.org/debian bullseye main contrib non-free

deb https://deb.debian.org/debian/ bullseye-updates main contrib non-free

deb https://apt.osmc.tv bullseye main

deb https://apt.osmc.tv bullseye-security main

However, after a reboot, it now takes a very long time (around 5 minutes) before the user interface becomes available, very annoying.

I have also noticed that the drives configured in /etc/fstab are no longer mounted automatically during boot. This seems to be related to some kind of network timeout.

Apart from the long delay and the missing mounts, I don’t see any other problems. If I manually run:

sudo mount -a

after the reboot, the drives mount successfully and everything works perfectly again.

Does anyone have any suggestions on where I should look to determine what is causing the delay/timeout during boot?

Which logs or commands would be most useful to check what is actually waiting or timing out?

Grabbed logs can be found here: https://paste.osmc.tv/oxafolidow

Kind regards,

Victor

2

Maybe It hangs because you network/NAS isn’t up, when fstab mount is called.

Try to enable “Wait for network” in OSMC setting → Network

Or try changing your fstab to:

10.0.2.2:/volume1/DOWNLOADS/DOWNLOADARR/media /mnt/MEDIA_NFS nfs noauto,x-systemd.automount 0 0

This way the mount won’t happen at boot directly, but systemd creates an automount unit that triggers the actual mount on first access. This avoids boot hangs if the NAS is slow to come up or unreachable.

But I am not an expert, but this works for me :slight_smile:

3

Thanks for the reply.

I also tested commenting out the NFS mount in /etc/fstab, but the restart still takes a very long time. So it doesn’t seem to be related to the NFS mount.

4

You have a bunch of errors

2026-09-21 21:46:26.960 T:3174    error <general>: GetDirectory - Error getting /mnt/MEDIA_NFS/movies/Despicable Me 4 (2024)/
2026-09-21 21:46:26.960 T:3174    error <general>: GetDirectory - Error getting /mnt/MEDIA_NFS/movies/Frankenstein (2025)/
2026-09-21 21:46:26.960 T:3174    error <general>: GetDirectory - Error getting /mnt/MEDIA_NFS/movies/Gaga Chromatica Ball (2024)/
2026-09-21 21:46:26.961 T:3174    error <general>: GetDirectory - Error getting /mnt/MEDIA_NFS/movies/I Swear (2025)/
2026-09-21 21:46:26.961 T:3174    error <general>: GetDirectory - Error getting /mnt/MEDIA_NFS/movies/Marty Supreme (2025)/

So for some reason you cannot reach your /mnt/MEDIA_NFS/movies/
Have you tried what i wrote?

5

As a matter of fact, I did. After the restart/reboot, it took about five minutes before the user interface appeared.

The problem is that since the latest update, the device doesn’t get an IP address during the initial boot process.

When I assign a static IP address to the device, it also seems to mount the drives correctly, but the reboot still takes a very long time.

I suspect that some network-related packages may have been accidentally updated or changed in the latest update, and that my Vero doesn’t handle these changes correctly.

6

Ok, sorry about that.

I suggest that you enable debug logging, to get more info about the problem then, so someone more clever than me can help you :slight_smile: