There are plenty of dead links to wiki.
We'll have a firm talk with our new wiki creator in the new year.
There are plenty of dead links to wiki.
We'll have a firm talk with our new wiki creator in the new year.
So you are using RPi to store the files? Is it powerful enough for such a task?
1) Yes, but it recommended to either usb a SSD for the /storage partition (or have LE boot entirely from the SSD). Running a database on an SDcard will sooner or later wreck the SDcard.
2) The RPi4, with gigabit and USB3.0 has enough grunt to handle Kodi databases. Even if that database is stored on a proper SDcard.
but a while a go this option disappeared.
Kodi and LibreELEC now default to SMBv2, as is well recommended. SMBv1 contains countless of security holes.
So it's possible your NAS is only capable of doing SMBv1.
There are settings in the LibreELEC addon and in the Kodi GUI to still do SMBv1, but for obvious reasons, not very recommended. Also, SMBv2 and up requires the network user of the SMBv2 server to have a password in its credentials.
The RPI3B+ supports USB booting, I'm not sure about the maximum drive/card/stick size.
Once you have booted LE 9.2.6 via an SDcard, the firmware will also be updated. So no need for config.txt editing.
So just write the image to the USB stick, and try and boot it.
You can also split the log file into smaller pieces...
If you already scraped your entire library using local sources, then yes, the database is kinda useless. You could fix things with a bandaid of sorts on the local/server machine and play with pathsubstitution in your advancedsettings.xml file, but I would set up things correctly and scrape the media collection properly.
It's best to also delete the Thumbs folder and the Textures13.db file, and also drop the current MyVideos116 database, as currently there will be thumbs and references to obsolete files once you use the SMB source(s).
What do I wrong?
You need to connect your server to the files as if you are connecting to the server (itself) as well. And not connect to the files as local files. Otherwise the wrong paths will be entered into Kodi's video database.
Check your filter setting of "All/Watched/Unwatched" movies in the left side blade menu.
Please note that this is an English only forum. If necessary, you can try to use translation services such as Google Translate.
If your Awow AK41 runs Windows 10, then it should be technically capable of running LibreELEC as well. You can try installing/running LibreELEC from a USB stick first as a test drive.
You can see the log file
We can also see that there has been a shitload of banned add-ons installed (at least 10 repositories of them), which automatically halts all support to you and your Kodi. You are of course allowed to install whatever you please on your computer, but we reserve the right to not give support whenever a problem arises.
See either you come back with a fully clean Kodi setup, or you are encouraged to find support elsewhere.
You could activate log level 2 at advancedsettings.xml and read kodi.log after boot.
Level 1 also enables debugging, but without the onscreen debug OSD.
"More powerful" is one way of looking at it. For HTPC purposes however, your thin client is currently a dead duck floating in the water.
2020-12-22 16:07:14.807 T:1307 ERROR <general>: X11 Error: No Display found
2020-12-22 16:07:14.807 T:1307 FATAL <general>: CApplication::CreateGUI - unable to init windowing system
Radeon HD is a couple of generations old already. And AMD support was kind of a lottery in those days: then it worked, then it didn't work...
I think the graphics card in those thin client boxes cannot be replaced with something more recent, but they will now make for an excellent door stop. I suggest you get yourself a simple Raspberry Pi, or a more recent board like a J5005 or J5040, whatever is your preference. Those have much more uptodate graphics engines, and are more than capable for Kodi usage.
Do you know why it can´t start X11-server?
ERROR <general>: X11 Error: No Display found
What exact graphics card is in that Thin Client? Those things are not known for their spectacular video graphics.
Both LE versions showing the same problem is a bit odd. The common factor is the SD card.
Other than that in a rare case, perhaps it's some type of hardware (GPU) failure.
Try a different SD card for starters.
I end up having to restart the pi manually to reconnect.
If a restart will reconnect you, then it's not the settings.
Nothing has changed on the network settings
Any updates on the Windows server lately? Perhaps SMBv1 has not been disabled, and SMBv2 has taken over.