Syncthing errors with insufficient space

  • I have a fresh install of Libreelec on an Odroid C4. I should have plenty of storage on the 32GB EMMC, but I also have an 8TB SSD plugged in. I'm getting this error:

    2025-09-09 02:32:49: Error on folder "Shared Movies" (7g7zm-6hrmi): insufficient space on disk for database (/storage/.kodi/userdata/addon_data/service.system.syncthing/index-v0.14.0.db): current 0.00 % < required 1 %

    2025-09-09 03:01:38: Saving config: write /storage/.kodi/userdata/addon_data/service.system.syncthing/.syncthing.tmp.793318938: no space left on device

    Is there a way to configure these files to be put on the 8TB drive instead? Or can I fix this by changing partition sizes? Something else? in System Information, it shows mmcblk1p2 is 28G, with 28G being used 100%.

    Thanks!

  • 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.

  • 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.

  • Is there a way to configure these files to be put on the 8TB drive instead? Or can I fix this by changing partition sizes? Something else? in System Information, it shows mmcblk1p2 is 28G, with 28G being used 100%.

    The initial image that you wrote to the SD card has 512MB for /flash (boot) files and 32MB for /storage; the second partition should be removed and resized to 100% (32GB) on first boot. If you have run out of space, either something has dumped a ton of data to the SD card and filled 32GB up, or perhaps the remove/resize didn't happen and you've filled up 32MB not 32GB?

    Boot params on the SD card in extlinux/extlinux.conf show boot=UUID=<string> disk=UUID=<string> .. if you check the UUID for the partition on the USB drive using blkid you can change disk=UUID=<string> to use that UUID and on boot it should use the USB drive for /storage and you'll start with a clean Kodi instance that you can move config over to. You can also mount using disk labels, e.g. boot=LABEL=LIBREELEC disk=LABEL=MYDRIVE assuming partitions are labelled or boot=/dev/mmcblk1p1 disk=/dev/sda1 style params. Note that you will need to use a Linux filesystem on the USB drive, e.g. EXT4, else the ssh daemon will fail to start since it depends on Linux filesystem permissions, and non-Linux filesystems (NTFS, exFAT) don't support Linux permissions.

    In theory the SD card image can be written direct to the USB drive and it should boot from that too; although I have fuzzy recall that the Amlogic bootrom only checks for bootable USB drives in specific ports, e.g. the OTG port.

  • 2025-09-09 03:01:38: Saving config: write /storage/.kodi/userdata/addon_data/service.system.syncthing/.syncthing.tmp.793318938: no space left on device

    Well that kind of says it all doesn't it ? Syncthing uses temp files wearing out your emmc on top of your free space issue.

    Best thing to do is to relocate tempfiles if the addon has that option.

    If 'not' you can:

    Code
    # Move addon_data to hdd
    mv /storage/.kodi/userdata/addon_data/service.system.syncthing /path/to/hdd/service.system.syncthing
    
    # Create a soft link to the new location
    ln -s /path/to/hdd/service.system.syncthing /storage/.kodi/userdata/addon_data/service.system.syncthing
    
    # Set the immutable attribute to prevent accidental deletion
    chattr +i /storage/.kodi/userdata/addon_data/service.system.syncthing

    To undo it:

    Code
    # Remove the immutable attribute that prevents deletion
    chattr -i /storage/.kodi/userdata/addon_data/service.system.syncthing
    
    # Remove the soft link to the new location
    rm /storage/.kodi/userdata/addon_data/service.system.syncthing
    
    # Move addon_data back to emmc
    mv /path/to/hdd/service.system.syncthing /storage/.kodi/userdata/addon_data/service.system.syncthing

    Good luck :thumbup:

    PS: dont forget to backup LE, before doing this, just in case.

  • I'm still working on relocating temp files. I just ran DU. I suspect I just don't know how to read it properly but it looks like most of the 32GB (25.3G) is stored on the 8tb-ssd, which should have at least a terabyte free.

    COREELEC:~ # du -xhs -d 1 /storage
    4.0K /storage/downloads
    2.7G /storage/.kodi
    16.0K /storage/lost+found
    4.0K /storage/tvshows
    4.0K /storage/backup
    4.0K /storage/pictures
    12.0K /storage/picons
    4.0K /storage/emulators
    264.0K /storage/.config
    4.0K /storage/screenshots
    1.7M /storage/.cache
    4.0K /storage/videos
    4.0K /storage/music
    4.0K /storage/.update
    4.0K /storage/recordings
    4.0K /storage/logfiles
    4.0K /storage/.ssh
    25.3G /storage/8tb-ssd
    28.0G /storage


    Also: This is LibreElec. I was running Coreelec, the network name was Coreelec, didn't want to break anything so I changed it to Coreelec.


    Well, I looked closer. That storage/8tb-ssd is not my SSD. It's a directory with what I'm guessing is storage for pictures and data. Is there a way to trim that down a little? Or is 64GB a more reasonable amount of space?

    Edited once, last by RChadwick: Merged a post created by RChadwick into this post. (September 9, 2025 at 5:24 PM).

  • 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.