Hello everyone,
Thank you very much for your answers.
The 4kp60 is another good tip. I don't even remember why I activated it in the first place because, as you said popcornmix, the movies usually end up below 30FPS.
I've just removed the parameter.
I've mentioned that earlier:
Post
[…]
Does it matter which log level I use for the current troubleshooting, 1 or 2?
[…]
I had already read that, but it can't be that.
I have the same problem with a Raspi 4 in the original Kodi Case with SD card in the bedroom and have exactly the same problem here. It is also completely irrelevant what quality the medium has, SD, HD, 4k, the same problem everywhere.
When I started troubleshooting months ago, I tried everything. The first thing I did was to put the Raspi in the Argon One in the…
Hunduster
January 10, 2024 at 10:07 PM
Yes, Argon One cases are known for soldering problems on HDMI contacts, but then it wouldn't try to buffer before it crashes. A network issue is much more likely. If I remember correctly, log level 2 includes more network data.
Hunduster Can you provide another log file for that error at log level 2? We still haven't found the real cause in the log.
As I said, I don't think it's the case. I first replaced it during my own troubleshooting because I thought it could be the SD card. I also run all my Ubuntu servers in the case on other Raspis, as I kept burning SD cards. But well, that's not an argument, the servers are all headless, connected to the network and are only operated via SSH 
However, I still have a Kodi running in the bedroom with the same config in the original Kodi case and SD card, where the same error occurred with exactly the same behavior. I therefore suspect the error is also in the network and had completely replaced the network equipment at the time. The only thing that is still 1:1 the same is the NAS itself and the connection to the NAS. I will replace the Gbic and Fibre Channel cable prohylactically at the end of the week.
I will be happy to provide a log as soon as the error occurs again. Since I changed the NFS settings from NFSv3 to NFSv4 the day before yesterday and also made granular adjustments to the NFS settings on my NAS, the error has no longer occurred.
We'll see if it had anything to do with that. It would be nice, although I've been fine with NFSv3 for the last few years. As I said, I've only had the bug since late summer 2023 and that from now on.