Hello again,
Milhouse could not find something. He recommends me to post the problem here again. So i link to the Posts in KODI Forum, where you can find my logs and the problem description. Hope someone could help me with this problem.
Answer of milhouse:
LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)
Post with Logs and description:
LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)
Greetings
Deepjungle
K i will wait for milhouse. I posted the problem in his thread before. i thought i could find the solution by myself but i think im lost with kernel problems.
thanks for your explanations and help.
No problem with the device drive. These are two different raspi 3 one with 12TB and the other one with 9TB Raid. 
[hr]
You have to replace %k with your partition. Just a guess, but perhaps the disk is not quite ready somehow at the time when udevil runs.
I tried the command on 1022 and 1023
/usr/bin/systemctl restart udevil-mount@/dev/sda2.serviceOn build 1022 it works fine on 1023 not. I made a sha1 checksum compare of the udev rules on both builds... no difference
Here the blkid Logs:
1022
/dev/mmcblk0p1: SEC_TYPE="msdos" UUID="176D-2AFE" TYPE="vfat" PARTUUID="99176dab-01"
/dev/mmcblk0p2: UUID="f2c26989-d7ab-4c16-9d6a-36e40c02035b" TYPE="ext4" PARTUUID="99176dab-02"
/dev/loop0: TYPE="squashfs"
/dev/sda2: LABEL="RAID3" UUID="8CC8F603C8F5EB7A" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="df1b0053-a29b-483e-8550-4592ca85f9a8"
/dev/mmcblk0: PTUUID="99176dab" PTTYPE="dos"
/dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="f40f75aa-7f98-4d6e-9507-86e2944e7673"
1023
/dev/mmcblk0p1: SEC_TYPE="msdos" UUID="176D-2AFE" TYPE="vfat" PARTUUID="99176dab-01"
/dev/mmcblk0p2: UUID="f2c26989-d7ab-4c16-9d6a-36e40c02035b" TYPE="ext4" PARTUUID="99176dab-02"
/dev/loop0: TYPE="squashfs"
/dev/mmcblk0: PTUUID="99176dab" PTTYPE="dos"
/dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="f40f75aa-7f98-4d6e-9507-86e2944e7673"On 1023 the sda2 partition gets not recognized.
Greetings.
But why does it work with less than 8.388.240 MB without any problems. I dont know the exact value when it is overturning but it must be between 8.388.240 MB (working) 8.399.999 MB (not working).
I compared the working and the not working rules. Both are identical.
# dont run in "installer" mode
IMPORT{cmdline}="installer"
ENV{installer}=="1", GOTO="exit"
# check for blockdevices, /dev/sd*, /dev/sr* and /dev/mmc*
SUBSYSTEM!="block", KERNEL!="sd*|sr*|mmc*", GOTO="exit"
# check for special partitions we dont want mount
IMPORT{builtin}="blkid"
ENV{ID_FS_LABEL}=="EFI|BOOT|Recovery|RECOVERY|SETTINGS|boot|root0|share0", GOTO="exit"
# /dev/sd* and /dev/mmc* ith partitions/disk and filesystems only and /dev/sr* disks only
KERNEL=="sd*|mmc*", ENV{DEVTYPE}=="partition|disk", ENV{ID_FS_USAGE}=="filesystem", GOTO="harddisk"
KERNEL=="sr*", ENV{DEVTYPE}=="disk", GOTO="optical"
GOTO="exit"
# mount or umount for hdds
LABEL="harddisk"
ACTION=="add", RUN+="/usr/bin/systemctl restart udevil-mount@/dev/%k.service"
ACTION=="remove", RUN+="/usr/bin/systemctl stop udevil-mount@/dev/%k.service"
GOTO="exit"
# mount or umount for opticals
LABEL="optical"
ACTION=="add|change", RUN+="/usr/bin/systemctl restart udevil-mount@/dev/%k.service"
GOTO="exit"
# Exit
LABEL="exit"Greetings,
i'm new to kodi and libreelec and i have trouble with the automount functionality. I have a raspi 3 with libreelec and kodi 18 (milhouse testbuilds). These working fine since build 1023. I have a raidsonic RAID5 external hdd case with 4x3TB (9TB as RAID 5). In build 1022 the drive is correctly attached but after update to 1023 not. I tried the newest build with no effort. I did some tests and found out, that partitions greater 8.399.999 MB are not mounted on boot. I can mount them manually and then they work as expected but automount did not work anymore.
How das automount work on libreelec and are there any config options or restrictions that id dont know ?
Greetings Deepjungle