I'm experiencing a weird problem when using kodi with removable disks. System is a 2Gb Pi4b, 32 bit os loaded via PINN just the other day, then updated to latest software. Kodi is from the standard repo and version 19.4
If I boot the pi, plug the disk in, wait a few seconds (for udisks2 to complete the mount), then start kodi, kodi sees the disk as a media source and adds an icon. Expected behaviour.
I have modified the udisks2 mount options page such that the disk is always mounted read-only. I do this as a) this system has no requirement to write to the disk, and b) I want to be able to hotplug the drive (in and out) without damage.
If I now unplug the disk, kodi gives me an 'unsafe removal message' which should not matter, but the icon is not removed. It does not do anything either (ie does not show any files on the device), but it seems odd that the icon remains.
OK, new test. If I boot the pi, do not plug the disk in then start kodi, kodi does not show the disk. Which again would be expected.
If I now plug the disk in ... nothing happens. Kodi does not add the disk as an icon. Not only that, but kodi does not show that the disk has been mounted to its expected mountpoint (/media/pi/yaddayadda). If I ssh into the pi whilst kodi is still running, the *system* has not actually mounted the disk, even tho' there seems to be no errors or other problems with the udisks2 subsystem. If I exit kodi, I can now see that the disk has suddenly been mounted by udisks2, and is now available at the usual mountpoint.
It's as if kodi is suspending the udisks2 service whilst it runs ...
Kodi also has it's own automounting gizmo that can be enabled via the advancedsettings.xml file. I read somewhere that this operates via udisks2 ... but I'm not sure this is true, and anyway this approach has it's own significant disadvantages.
1) It ignores my udisks2 mount options settings, so the disks are mounted rw,, not read-only. This means that unplugging the disk could lead to a corrupted fs on the removable drive, and is something I wished to avoid.
2) It insists on mounting the pi RECOVERY and SETTINGS partitions ... I have tried the usual tricks of marking them ignored in the udev rules, but to no avail, the kodi automounter still mounts them. I would prefer that these partitions just remain not mounted unless I choose to mount them.
So does anyone know how I can either get kodi and the system service udisks2 to work together, or how I can use the kodi automounting gizmo to behave the way I need ?
(Question also raised on the kodi forum ... so far without response ...).
2 posts • Page 1 of 1