All of it.
You'd too want all the pieces if you were to solve a puzzle, right?
All of it.
You'd too want all the pieces if you were to solve a puzzle, right?
Perhaps the READonly switch on the side of the SDcard adapter has moved by accident when inserting it?
How can I further troubleshoot this?
You can start by providing the FULL log file, via a pastebin website.
There is not much we can do with 3 identical error messages alone.
My first guess would be a corrupted database, but we'll find out once the rest of your log is known.
and what can i do to fix it?
Keep updating your add-ons, a fix should already be in the works or even already available.
I either get the Fil not found or it's hangs on 0% cache.
Setup is 2 x NUC with shared Maria DB on a Synology NAS
NFS does fine for me.
- LibreELEC 9.2.0 on x86-64 Generic
- Ubuntu 16.04.6 as NFS file server + Ubuntu mate 18.04.3 on Raspberry Pi as NFS server
Both servers show up while browsing for NFS sources in LibreELEC. NFS browsing in Kodi in Ubuntu doesn't work for me.
So this time I think your Synology NAS is to blame.
As far as SMB is concerned, I think this is broken Kodi-wide. I tried a WetekHUB with CoreELEC 9.2.1 for Kodi 18.5, and just about every video had buffering issues when connected to a (old) Synology NAS via SMB. When I connected the WetekHUB to my NFS servers and played the same movies, the buffering was gone.
Earlier I tried filling up the thumbnail cache on the WetekHub by copying the thumbnails to it from my office (Ubuntu) computer via SMB. Even that went wrong as I encountered multiple timeouts. So something is quite crapped up in either the Linux kernel(s) or the Kodi internals as far as SMB is concerned.
Vero 4k+ plus OSMC
i think your issue is the pi is underpowered.
Under powered RPIs will show a yellow bolt in the top right corner. I don't think that is the case.
I resolved the issue: I've just recompiled the file from the original disk, and now it works.
'Recompiled' as in copied it again from a Bluray disc? Okay. I'm glad it all now works.
Looks like you guys are happy with how your sw works, and I cannot do much about it. It was my first interaction with an open source project, sorry if I couldn't manage my expectations.
We are happy with the basics, Kodi itself is already some 15 yrs old. But it can always be improved and extended. Open source software via f.e. Github offers any programmer to add to the application. Those additions and/or changes will be reviewed and added when accepted.
my Libreelec draws a blank when it browses the Windows (SMB).
Microsoft relegated SMBv1 for obvious reasons. For SMBv2+, you require a Windows user account with a password. Also network browsing was disabled. Use Kodi's "Add network location..." for creating a source, enter all credentials and stuff should work (tm).
This happens e.g. on a 4:3 TV program with 16:9 commercials inserted.
Before we start ordering our new crystal ball for the year 2020, can we start by you providing us a full debug-enabled kodi.log file, so we can look at some internals? We will need more details on the what, how, and when (and why).
And which of the 7-8 RPi models is this about?
1) I'm not a Kodi developer, so whatever is (im)possible in terms of error-skipping voodoo I can't tell you. The ffmpeg boys might have a clue.
2) "Our" OS... is a standard vanilla Linux kernel with just a couple of bells and whistles to run Kodi. Why it is tripping so heavily in your case, I have no clue at this time. I cannot recreate the problem/bug here no matter how many times I play a 4K video.
For now I've seen only 1 debug log file, and a couple of "metoo" posts. The more log files we have, the more we can perhaps pinpoint the issue.
If some input is broken and processed by your program, you should get a deterministic result.
On average, three quarters of a software program is already expected to making that application 'foolproof'. You can do only so much, and a 100% bugfree application will never happen. Kodi uses a 3rd party tool ffmpeg for decoding videos. Team Kodi didn't create it, but we use it because it helps us play Kodi on just about every electronic gadget there is. There isn't much else to choose AFAIK.
And do you know why the log does report problems? To help the developers with fixing them.
I've been part of Kodi and XBMC since 'Eden'. I also have a ISTQB certification. I know what testing software is. I think I know what the log file is for. What we cannot do is yank all available Frozen rips from the internet sites, and test all of them. Would you believe me if I said that my Frozen bluray disc rip didn't freeze (how poetic) when played on my RPi?
I'm using CoreELEC so I'm not sure if that's the right place to report my logs to.
Yeah, that is a touchy subject in itself. Generic Kodi stuff could be addressed, but when it comes to the more technical stuff sending the log to CE is preferable in my view.
it still shows the bolt icon at the top right corner and randomly shutts down (or unmounts the hdd)
In that case, you have a really crappy power adapter. An RPI2/3 needs at least 2.5 Amps, the RPi4 preferably at least 3 amps. And some adapter stickers simply lie about their capabilities.
0.7 Amps for a RPI is way too low. Also "latest" is not a version number.