For all to work correctly I would still have to see 12.0 update channel in manual update process instead of empty list.
Set delay to more than 10 seconds and rebooted. Now I could select update channel in manual update.
Will flash sd card with 12.2.
Ignore comments about samba. Just noticed that selector is on by default in setup.
/.kodi/temp # cat kodi.log
2024-02-27 17:26:18.521 T:1010 info <general>: -----------------------------------------------------------------------
2024-02-27 17:26:18.522 T:1010 info <general>: Starting Kodi (21.2 (21.2.0) Git:21.2-Omega). Platform: Linux ARM 64-bit
2024-02-27 17:26:18.522 T:1010 info <general>: Using Release Kodi x64
2024-02-27 17:26:18.522 T:1010 info <general>: Kodi compiled 2025-01-20 by GCC 13.2.0 for Linux ARM 64-bit version 6.6.70 (394822)
2024-02-27 17:26:18.522 T:1010 info <general>: Running on LibreELEC (official): 12.0.2, kernel: Linux ARM 64-bit version 6.6.70
...
2024-02-27 17:26:21.765 T:1032 error <general>: SETTINGS: load_url # Error loading url: http://releases.libreelec.tv/releases.json
Reason: [Errno -3] Temporary failure in name resolution
2024-02-27 17:26:21.964 T:1032 info <general>: SETTINGS: __init__ # updateThread Started
2024-02-27 17:26:21.966 T:1032 info <general>: SETTINGS: set_auto_update # manual
2024-02-27 17:26:22.009 T:1093 error <general>: SETTINGS: load_url # Error loading url: https://update.libreelec.tv/updates.php?i=9076dd061576a19c7f880f7065de1b2c&d=LibreELEC&pa=RPi4.aarch64&v=12.0.2&f=raspberrypi%2C4-model-b-4g
Reason: [Errno -3] Temporary failure in name resolution
2024-02-27 17:26:22.065 T:1094 info <general>: SETTINGS: run # Waiting
Libreelec SD card setup using Raspberry Pi imager. They are still on 12.0.2 image. I know that I can manually go to 12.2, but I want to see normal update working. Network is on wifi. DNS is provided by caching dns on router and google dns.
If update is set to manual, release and available versions lists are empty. I haven't seen automatic update kick yet.
Also I did not ask to enable Samba during setup and it is enabled.
Do I have to delay kodi startup for update to fetch release information after network is up and ntp sets up clock?
OP did not tell, if they are using Jellyfin or Homerun. You can get dumb NAS box and then regret it as its CPU can't handle transcoding and case does not have option for second GPU.
Lots of questions to answer when selecting or building NAS.
NAS setup would also depend if user wants to run network media server on libreelec or on nas.
Your ssd should be automatically mounted in /media directory.
/storage/8tb-ssd is not standard libreelec directory and it would exist on /storage only if some of your actions created it. That directory does not contain librelec system data. It can contain only your personal data files and maybe indexing information that librelec created when indexing those files.
If I were you, I would be moving all /storage/8tb-ssd data into dedicated directory on 8TB SSD. It is relatively easy to do, if system utils addon is installed. If you never needed to install that addon, you probably won't be able to add it with full /storage and only Unix CLI commands can be used to move stuff out.
64GB SD card won't be enough, if you continue filling up /storage/8tb-ssd while thinking that you are writing to 8TB device.
Linux du command calculates disk usage. If you have Libreelec system utils installed, you also have mc graphical UI instead of shell CLI.
du -xhs -d 1 /storage
If you have SMB enabled, you can access logs directory over windows network too.
reduce your logs and housekeep existing logs
or find what is using filesystem.
First step in file system capacity problem is to figure out what is using it and only then look for appropriate action.
"Driver does not support the 0x2572 PCI ID."
Use different video card or try using legacy version.
..
Basically, I've been using plex on my NAS to allow me to watch media on the go, but they are putting the price up, so I would like a cheaper (ideally free) option.
Main part of NAS cost is hardware kit and storage devices. Kodi/Libreelec is stuff that you attach to your tv. Jellyfin and NAS are things attached to your network. You can put your Jellyfin server on your media kit next to tv or on your NAS kit in your basement. Libreelec does not have NAS functions for storage management and resilience. If you are looking for your qnas replacement, you are on wrong forum.
Sorry to revive this.
I have my media on a QNAP NAS, and I know I can run jellyfin directly on there, but it seems like it will be a real pain.
Is it possible to run jellyfin on LibreElec, and point it at the media on the NAS, and to then be able to use a jellyfin app on AppleTV or similar to be able to watch those videos from a remote location?
Mount your NAS share on Libreelec and Jellyfin addon on Libreelec will see your media.
If you install Kodi package on Ubuntu, you will have other solution for missing LVM support on Libreelec as Ubuntu can work with LVM.
See LE 12.0 added lvm2, luks (dm-crypt, veracrypt), mdraid, ext4 encryption
Stock Libreelec does not have LVM support.
Maybe connect your drives to raspberry via USB hub that has independent power source?
Transparent proxy is just one step further from running a proxy.
You can edit files via SSH by running command via SSH. You probably do not want to learn sed
ssh root@libreelec sed -i 's/old/new/g' /storage/test.txt
If you are about editing metadata in video files, commands depend on video format.
google has Mongolian and Khmer fonts under open font license. For some reason they prefer not to design their site to work on system which has Mongolian and Khmer support, if javascript is not enabled.
Old Italic and Linear B support in subtitles was a joke.
It might be better, if UI did not depend on single font for subtitles and could use any font that supports text in specific unicode block.
Arial Unicode MS does not support Khmer or Mongolian or Old Italic or Linean B. 
vmware workstation can start both generic-legacy and generic ovas.
lspci shows that libreelec/linux recognizes video card as VMWare SVGA II adapter.
Maybe configure your video card in hypervisor properly or use different virtualization software. VGA (640x480) emulation is likely not enough for the system.
Maybe also start new topic instead of hijacking something unrelated to virtualbox.
