Posts by trogggy

Looking at your error I'd guess you have fast startup enabled. Your drive hasn't been ejected cleanly in windows.

And have you run chkdsk?

Quote from Da Flex

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.

if you're using a shell script I'm pretty sure you have to use kodi-send to run a built-in function.

xbmc.executebuiltin('Action(reloadkeymaps)') will work directly from python - I'd use a python script myself.

I guess either would work in this case then. I vaguely remember having to use noop for something years ago.

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

<up>noop</up>

to specify no action (ie override the default).

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

<?xml version="1.0" encoding="UTF-8"?>
<keymap>
<global>
<keyboard>
<blue>XBMC.RunScript(/storage/switch_keyboard.py)</blue>
</keyboard>
</global>
</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.

Use the built-in backup addon in libreelec. That copies your files rather than an image, so if you're only using 1GB that's how big (ish) your backup will be.

Literally the first line of the link:

'autoexec.py is an optional python script that users can create in their userdata folders'

Quote from kostaman

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.

Reboot.

Quote from Shoog

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.

Shoog

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?

Yes, it works. Use either label or uuid to point at the wanted partition. Just edit cmdline.txt.

eg to use 'wibble' as storage:

boot=/dev/mmcblk0p1 disk=LABEL=wibble quiet ssh

For the default skin you can either rename or just raise the addon version in addon.xml to stop changes being overwritten.

Unless things have changed recently with keymap editor the file you need is /storage/.kodi/userdata/keymaps/gen.xml

Connect via SSH and run :

systemctl stop kodi

When you're done run:

systemctl start kodi

The errors are there because you're putting categories into your remote.xml that kodi doesn't recognise. Take a look at the default remote keymap (here) and use the same categories as that.