Posts by trogggy

    It probably doesn't get enough power over USB. Every detected device will be visible on the /dev folder (like sda, sdb... use SSH login to see it). If it doesn't appears in that folder, then it's definitely an USB power issue.

    Except it's not a usb-powered drive. ;)

    First thing I'd do is to plug it into a windows pc and run chkdsk. If that doesn't fix it it's time to start looking at logs.

    FWIW the only problems I've ever had with openelec / libreelec and ntfs drives have been when they've either not been ejected properly or they've been used on a win10 machine with fast startup enabled. Chkdsk has always fixed it for me.

    Might be wrong, but I was under the impression you needed to use noop, eg


    to specify no action (ie override the default).

    I'd use one keymap that was just something like:

    1. <?xml version="1.0" encoding="UTF-8"?>
    2. <keymap>
    3. <global>
    4. <keyboard>
    5. <blue>XBMC.RunScript(/storage/</blue>
    6. </keyboard>
    7. </global>
    8. </keymap>

    and make another one like vpeter's example full of 'noop's (ie disabling keys) that you could either move in / out or rename (the extension) before reloading keymaps. Then have your script bring up a notification to say the remote's been enabled or disabled as appropriate.

    If you use a python script linked to a remote button or shortcut / favourite to move keymaps in and out of storage/.kodi/userdata/keymaps you can then use xbmc.executebuiltin('Action(reloadkeymaps)') to load the new map. Hacky but it works reliably.

    I totally agree. I thought it was too obvious to ask.

    I NEVER use USB powered Hard Drive Enclosures NEVER.

    I had one where it mounted but i could hear clicking noises from the hard drive inside.

    That is a recipe for hard drive failure and corruption.

    So use a powered hub / a y cable. Then there's no issue.

    @ the op...

    If it's worked before then I would try:

    - sticking the drive in a windows pc and running chkdsk from the command prompt;

    - if that doesn't fix it try a new LE install on a fresh sd card, see if the drives are recognised;

    - if still no joy try a new LE install using the LE version that's worked for you in the past.

    FWIW I'm using a raspberry pi v1 (costs basically the price of a coffee now) connected to the router and a couple of 5TB (powered) drives. It's only a temporary arrangement (we're between houses) but it hasn't missed a beat so far, so the server has stayed in its box.

    The reality is that if you want to run a box off the latest Kodi/LE you would be stupid to choose any ARM based solution. Intel products cost a bit more but offer a level of stability/dependability and future support just not possible with the shifting ecosystem of ARM. I made a mistake this time round (believing dubious marketing speak) but will never make the same mistake again. Intel every time.


    I bought a couple of s905 boxes for about £30 each in 2016. They've played everything I've thrown at them, cost peanuts and use bugger-all power. If they don't work with anything after Leia I'd happily buy an equivalent - if there is one.

    What would I have to spend on intel hardware to get equivalent performance?

    I don't have much love for Samba reliably moving stuff about - ensuring that correct permissions are maintained on a system which doesn't use permissions. SAMBA has always been somewhat unreliable on Linux systems.


    That's not been my experience with libreelec / openelec.

    I've also edited directly in ubuntu in the past without any issues.

    I'm honestly failing to see why you'd go to all that trouble. I edit stuff on libreelec via smb regularly (from windows) with no issues. Either run 'systemctl stop kodi' first in ssh if changing stuff on a working install, or stick the new sd card in an already running libreelec if it's for something else.

    Isn't that easier?

    I prefer the CE/LE built-in (if only because it doesn't require any other addons). The choice is yours, both of them just copy /storage/.kodi and some other key folders :)

    Robweber's addon doesn't copy the whole .kodi folder. The built-in LE backup will restore on another card to give an identical (functionally) setup. Unless things have changed recently the backup addon will leave 3rd party addons disabled (on krypton and later).