Yes, which is worrying in itself since Kodi can make frequent writes to the memory to update the log.
This is what killed my SD Card on my Pi. Since I was displaying jpeg images as a slideshow during music playback, often a few hours a day, and the Pi can’t handle jpegs by hardware Kodi writes a warning to the log file and in my case this was happening every 10 seconds.
Re-installed on a new SD Card and that problem went away but I also converted my images to PNG which doesn’t produce the warnings. Also stopped the log file generation.
eMMC though, should have a better life than SD Cards
Please, can we refrain from cluttering threads with posts that are irrelevant to the context? The failure of your SDcard on your Pi has no bearing on this thread and OP’s issues while using a Vero4k+.
I just managed to make it crash: I have a fresh install, changed a few settings (video resolution, audio passthrough and a few other things) and have installed Netflix add-on (Watch Netflix and Amazon Prime in Kodi - Making Stuff Work).
Now, when I try to install FTP on Vero through My OSMC it crashes.
What exactly do you mean by crash? Your logs don’t indicate a crash at all. They actually indicate that FTP installed without issue.
When we use the word crash, we are referring to an unexpected reboot of the device, or the Kodi app crashing, resulting in the frowning face screen followed by a return of Kodi after the app restarts.
Screen goes black, and tv says “no signal”. Connection through FTP, Putty and Yatse is lost. So that’s what I call a crash And when it crashed during FTP install and I went into My OSMC again, FTP wasn’t registered as installed, and I could choose to install FTP from scratch.
That log is apparently too large for the paste site to handle, therefore empty. If you can’t reliably create this crash and must wait for it to randomly manifest, resulting in excessively sized logs, maybe you could share the kodi.old.log on google drive or some other well known fileshare site?
Sure I’ll try again Right now it crashes every time I try to play a video file. Weird, yesterday I watched at least three video files, both from beginning and resuming. And both UHD and 3D files. Today I have been listening to music (mp3 from NAS connected through NFS) with no problem at all.
Here’s another log file. I have checked that it’s not empty.
2020-03-23 20:43:40.063 T:3645129440 ERROR: Open - Error, could not open file nfs://192.168.1.30/volume1/Video/Film/Monty Python - And Now For Something Completely Different (1971).avi
That looks like it could be a Synology NAS. So, (1) are you sure the file exists on the NAS and (2) do you have any spindown/hibernate function(s) enabled on the NAS?
Oh sorry @sam_nazarko, I thought it already was enabled.
Here’s another crash. This time OSMC has just finished playing music, and it crashed while returning to the main screen. And I hope the log file looks like it should now
No “sad smiley”. The screen goes black and TV says “no signal”. Connections to Vero fails (FTP, SSH and Yatse remote). That’s what I call a crash The issue with NAS is probably because it went in sleep mode (I had paused the music, and started playing again after an hour) WOL is working fine.
Yes, I have updated today, apparently that didn’t help. I’ll try removing .Kodi, but my guess is that it won’t make a difference, since it can “crash” almost immediately after s fresh install…
And when it crashed during FTP install and I went into My OSMC again, FTP wasn’t registered as installed, and I could choose to install FTP from scratch.
Right now it crashes every time I try to play a video file. Weird, yesterday I watched at least three video files, both from beginning and resuming. And both UHD and 3D files. Today I have been listening to music (mp3 from NAS connected through NFS) with no problem at all.
The issue with NAS is probably because it went in sleep mode (I had paused the music, and started playing again after an hour) WOL is working fine.