Multiple Intermittent Hard Crashes during playback in last week Vero V

Help and Support Vero V
1

Was travelling overseas from mid-July to mid-August so was not watching anything on my Vero V.

This last week on 3 different occasions the screen has randomly frozen. Once when skipping backwards and twice just in the middle of playback. Whenever this has happened before it has usually been a KODI fault of some kind and I can still SSH into the Vero and reboot from the CLI.

However, in all of these cases the Vero goes completely offline. SSH is not responding and it doesn’t even answer to pings. The only option is to pull the power plug out to reboot it.

I can try and upload logs, but I have no idea how to reproduce this and I’m not sure even that kind of low-level crash would show up in the logs?

I did apply the August OSMC update when I got back last week so I’m wondering if it’s related to the latest update?

Everything was working perfect up through July and I have had no issues with the Vero V in general.

I don’t have any external devices plugged into the Vero either. Just the power supply it came with and it’s connected via ethernet and HDMI. All my libraries are stored on a locally connected NAS via an NFS share.

2

Is there a specific clip you can reproduce it with and are you able to reliably reproduce it? If so, that would be extremely helpful.

Is it possible to try transfer a file to local storage and play from that as a test?

Sam

3

it’s happened on different videos and when it crashed out, I just pulled the power plug and after it booted back up went to the exact same spot in the video and it played through just fine. So it doesn’t seem reproducible. The Vero V didn’t feel hot to the touch in either instance so I’m just not sure what to say or do.

This feels like a pretty low-level crash/freeze…almost like kernel-panic. Is there some kind of kernel logs I can access the next time it happens? Or do I need to do something to enable some kernel logging that might capture it when it happens next?

4

Kernel Logs by default are only temporary in the memory and not persistent.
As a first step I suggest after next crash upload logs via MyOSMC - Log Uploader that would at least from Kodi have the crash logs.

If you really want persistent kernel logs here the details

  1. login via SSH to the OSMC device, user osmc, password osmc
  2. cd /var/log
  3. sudo journalctl --rotate
  4. sudo journalctl --vacuum-time=1s
  5. sudo mkdir journal
  6. (from now, kernel messages are written to new directories for every boot)
  7. sudo shutdown -r now
  8. now wait for the issue/event which is the problem of this topic
  9. once it happens again and you are forced to reboot the OSMC device or it rebooted automatically, you’ve to identify the right kernel message log:
    9.a) login via SSH and invoke
    sudo journalctl --list-boots --no-pager
    9.b) the lines start with an index id like 0, -1, -2, etc. and contain the date and time when log was started
  10. also, upload the appropriate full log using
    sudo journalctl -o short-full -b <identified index> --no-pager|paste-log
    (replace <identified index> with the real index id, see above)
  11. provide the returned URLs here
  12. don’t forget to remove the created journal directory otherwise your system’s root file system gets filled
    12.a) login via SSH
    12.b )cd /var/log
    12.c) sudo rm -R -f journal && sudo reboot (repeat this line if you get a ‘cannot remove’ error until it works and your ssh connection gets lost by the reboot)

Thx for your time. We hope to help you, soon.

1 Like