IDs for entries in files are linked with various other tables in the video database. Deleting only the entries in the 'files' table will get you a corrupted database.
If video entries are still there after a 'Clean Database', then it's probably because the files are somehow still accessible.
It's a good thing we can still decide for ourselves what we choose to do. Just throwing a bunch of hardware info and unknown file links on the table will not accomplish anything. Apparently OP thinks that we are some "ask-and-you-shall-receive" service. Money can get a lot of things done, but OP needs to do a rethink here IMO.
You can check the syntax by simply running the mount command directly in the CLI.
If the mount is successful, there will be no (error) output.
The autostart.sh file is to be created in the "/storage/.config" folder.
How did you update, via the internal update mechanism or via downloaded .tar/.img.gz files?
Because there are still people who manage to try & update a RPi device with the update for a x86-64 PC, and that does not work well.
[hr]
Thnx for the help. I will look into to backup the data using a ext4 tool. I used the libreelec USB/SD creator. I installed the Horus build from TDB wizard i think the probleem is there.
But do you have a program that can backup ext4 =
EXT4 is a Linux disk format. You can easily access it via any modern Linux distro. Try Ubuntu and run/test it without installing. Once it runs, plug in the SD card, and copy the files via the Nautilus File Manager. Drag&drop is easy enough.
The "Horus build from TDB wizard" is a 3rd party tool thing. If LibreELEC gets f*cked up by using it, contact the TDB developer(s). We have no desire to be other people's clean up crew.
[hr]
I tried to update my RPi(1) yesterday from OE6.0.3 to LE7.0.2 via Update-Folder (tar-File). I got stuck in a Bootloop too. I saw the update process, then the LE logo and then 10-20 times the Kodi-Jarvis logo until I unplugged the Raspi.
Normally, going from OE 6 to LE 7 should be possible, but having the older AEON skin active, might disrupt the process.
I didn't have time to try via Backup - Clean-Install - Restore.
Well, you probably need to do that now anyway. A fresh start never hurts, it will also clean up your video and/or music libraries of unnecessary clogging and stuff that's no longer usefull. Suggestion: get a 2nd SD card, and keep the old as backup.
Bootloop... Could be from a number of things, from sdcard corruption to crappy (illegal) addons.
Sometimes it's better/faster to start with a clean slate.
To save your data, place the sd card into a Linux machine (or Windows with some EXT4-compatibility tool) and copy the necessary folder(s).
Install a fresh copy of LE via the LibreELEC USB-SD Creator tool, and start from there. If you have no bootloop, restore your backed up files.
If the bootloop reappears, it's best to reconfigure & install everything from scratch.
The only user in LibreELEC/Kodi is 'root', and it has all permissions for reading and writing.
Plenty of people have used the Generic build on Intel systems, and so far you are the first one describing this type of problems.
Please provide a full kodi.log file for starters. Look here for details.
As long as any of the enclosed addons are not machine-specific, it's possible to copy the Kodi config. Just keep a backup of the guisettings.xml file ready on the Intel machine ready, just in case.
No need to use Rufus anymore, LibreELEC has its own USB creation tool now.
Which OE version was running previously on the Lenovo box?
Currently we are working on LibreELEC 7.90.005 Alpha. Try to install that one and report back.
Ehh... Have you already looked at the URL given to you, or perhaps read the title of the topic or its first line of text?
"New LibreELEC Retroplayer builds!"
So no, it's not an addon. The available downloads are .tar files, so place the .tar file into the Update folder after that, and reboot.
To create a fresh setup on a SD card, use our already (in)famous LibreELEC USB-SD Creator tool.
FYI: This is NOT for updating an existing & running LibreELEC setup.
Via the commandline (SSH) you can partition your attached devices.
See this webpage for a tutorial.
They will constantly be bugging you to come fix it.
I don't know what you are doing to a RPi box to make it crash or whatever, but I don't have those experiences. Not in the last couple of years using Raspberry Pi's, or now during the testing of the next LibreELEC alpha/beta/stable builds. Things work fine with the official addons. If you are planning to also add the 'not so legal' addons, then yes you are on your own.
Should the bugs come from things that got altered, deleted or damaged by the user, then that's too bad. There is no real fix for stupidity. Make yourself an all-working setup on the micro sdcard, and then make a full backup of it. And if there is a problem, restore the backup.
"Not too expensive"... Okay: Raspberry Pi 3.
(Don't forget to also buy a 4GB+ class 10 micro-sd card, 2 amps power adapter, HDMI cable, and/or mouse, keyboard if necessary).
some movies ( MKV 's )
Sorry, but that limited info does not help at all.
MKV is a container format that can hold various types of video formats.
At the moment we are at version 7.90.005 alpha. Update your RPi box, run one of those MKV files, and give us your full kodi.log file.
See HOW TO:Provide Logfile - LibreELEC for more details.
LibreELEC does not contain an NFS server, so creating an /etc/exports files has no use whatsoever. It does have Samba server built-in.
It is most likely a Linux kernel hiccup because of some incompatibility with your older hardware. Something not that easy to fix by us.
Suggestion: just turn the box fully off. It'll save you a couple of extra Watts as well. The boot time of LibreELEC shouldn't be that long anyway.
Ah, was that you? 
I guess it is time for a full kodi.log file.
HOW TO:Provide Logfile - LibreELEC
How about a screendump of your Video acceleration settings? Just press PrtScn, the image(s) will be in the screenshots folder.
Perhaps Kodi defaults to VDPAU acceleration (=Nvidia), instead of VAAPI (=Intel).
The option is there. You probably need to (re)enable the option to delete files in the Kodi GUI.
