LE 12 added lvm2, luks (dm-crypt, veracrypt, bitlocker), mdraid, ext4 encryption

    Do the N150 builds include the virtio* devices (net/balloon etc)?

    I have network access in a VM with your latest generic image, but trying to set wake on lan on eth0 throws an error:

    I don;t especially like the unknown speed/duplex etc above... Also no reference to the virtio-net driver used, see

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    No worries buddy!

    Your nightly runs just fine (the LE12 does not run due to the kernel version, whereas LE13 nightly also runs just fine). So there's no pressure really :)

    It's just strange the way virtio-lan works with the kernel; it does not "present" its features (unless it's a dummy driver). Same behaviour in LE13 nightly as well (see also Does the STANDARD LE (not the virtualized image) support the virtio devices (especially virtio net)? )

    And thank you for your build <3

    *** for testing only ***

    please don't ask for support, it is just the 1st compiled version i have done
    this is just for testing
    i only use Generic so far

    version 12.2-preview-#250803 of the upcoming LE 12.2
    full set of images for Allwinner Amlogic Generic NXP Rockchip RPi

    If you have trouble try https://test.libreelec.tv/12.2/

    download link https://sky42.libreelec.tv/testing/12.2/
    based on https://github.com/LibreELEC/Libr…/libreelec-12.2
    my source diff https://github.com/LibreELEC/Libr…ibreelec-12.2.x

    upstream updates from 12.0 to 12.2 include e.g.
    - kernel 6.12 RPi
    - kernel 6.16 for all other
    - mesa 2.5
    - and many more

    Quote from sky42

    uploaded full 12.2.1 release


    still very busy at work

    Is it possible to automatically mount an unencrypted Linux software RAID 5 array using Sky42's LibreELEC version when the operating system boots?

    Otherwise, I would always have to manually type the commands myself in the terminal on another PC.

    I'm not getting anywhere with a store-RAID.mount file.

    When I check the status, it always asks for a dependency, even though I've entered the RAID's UUID.

    Please help!

    Quote from sky42

    the kernel should have already started the raid 5

    No, the kernel doesn't automatically assemble the RAID 5 system.

    I have to assemble it manually via the terminal, using the following command:

    mdadm --assemble --force /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1

    Then I need to create a folder:
    mkdir /media/RAID
    and then the mount command:
    mount /dev/md0 /media/RAID

    Quote from sky42

    write a systemd mount unit file like

    https://wiki.libreelec.tv/how-to/mount_network_share

    but for a local Filesystem

    I already did that.

    I described how it doesn't work with the .mount file.
    I did follow Artembutusov's description, but there's no difference.
    LibreELEC RAID support – Artem Butusov Blog

    I inserted that into the mount file, perhaps you'll see an error:

    [Unit]
    Requires=local-fs.target
    After=local-fs.target

    [Mount]
    What=/dev/e27295f5:9fb13d9b:85b5bf5e:381f895d
    Where=/storage/RAID
    Type=ext4

    [Install]
    WantedBy=multi-user.target

    Use the wireguard systemd service as a template for something that runs after the network is up and before Kodi starts; change the systemctl command for whatever commands you need to mount the array. Add more ExecStart= lines as you need to run the commands in sequence. If you need more logic and error handling put the commands in a script in /storage/.config and then run the script from the systemd service.

    Quote from chewitt

    Use the wireguard systemd service as a template for something that runs after the network is up and before Kodi starts; change the systemctl command for whatever commands you need to mount the array. Add more ExecStart= lines as you need to run the commands in sequence. If you need more logic and error handling put the commands in a script in /storage/.config and then run the script from the systemd service.

    I really have no idea what all this is supposed to look like.

    I've posted my complete mount file here, the UUID, and how I'm assembling and mounting the RAID via SSH on another PC using the terminal.

    Now I've also created a wireguard.service file, as I understood from your description, and it's still not working.

    My question for you:

    Have you connected a software RAID 5 to your LibreELEC distribution from sky42 and gotten it working?

    If so, please post how and what you entered in your wireguard.service file or storage.mount file.

    If you don't have a RAID 5 running on your distribution, then unfortunately you can't help me.
    I need helf from a user who has managed to get a Raid 5 on sky42 version.

    I still wish you a Merry Christmas ;)

    Quote from Lordy

    Have you connected a software RAID 5 to your LibreELEC distribution from sky42 and gotten it working?

    No, because I use a Synology NAS in the network with a hardware RAID6 configuration /shrug

    Create as /storage/.config/system.d/raid5.service and then enable/start the systemd service. If you can run the same commands over SSH to mount the array the sky42 image contains all the software bits needed. If you cannot then it doesn't. NB: Check the actual path for mdadm in the image, I've assumed it's in /usr/bin.

    But that's exactly how I did it, even added the Before=kodi.service because you wrote that it should start before kodi.
    O.K., my lines looked like this:

    exactly as described on the page:

    https://wiki.libreelec.tv/configuration/wireguard

    I have now even made the corresponding corrections according to your specific instructions and it still doesn't work.


    Quote from chewitt

    No, because I use a Synology NAS in the network with a hardware RAID6 configuration /shrug

    You haven't included software RAID5 in your distribution and you can't help me at all.
    I had already said that only someone who has a Raid5 software running in their system, which was mounted when the system started, can help me

    Quote from chewitt

    Your version executes connmanctl to run mount commands, which it cannot do, thus guaranteeing failure.

    If you read carefully, you'll see that I corrected it according to your instructions, and it still didn't work.

    So your version doesn't help, and you don't need to repeat the obvious.

    It doesn't work.

    For my knowledge chewitt unit file looks absolutely the right way, but i spotted a letter missing. He does not run my image and could not check and see that mdadm is in /usr/sbin/mdadm not /usr/bin/mdadm.

    So take chewitt unit file and correct the path of mdadm should do the job.

    Does "systemctl status raid5.service" show any errors from the commands when they are run? - Are there any errors in the systemd journal or showing in dmesg? I'm wondering whether some sleep delays might be required space out commands? - filesystem tasks can need time to complete/settle before you run the next command; systemd ExecStart sequences need the same considerations as putting commands in a bash script.