Hello Sky42 and all developers, thanks a lot for developing this wonderful LE system. After using XBMC/KODI for a while, often having difficulties with drivers and the like (I'm not a Linux expert at all), I am now very satisfied with LE11.0.6 (Generic X86_64) on my INTEL NUC.
The one thing I miss versus the Kodi install on Ubuntu is the ability to read and write BITLOCKER disks attached to USB, they simply are not recognized by LE.
Is this the correct binary for gaining that ability? shall I backup my "standard" LE11 htpc and install this version with encryption support, then restore the LE config? will it mount NTFS BITLOCKER encrypted disks (USB attached) and be able to use them? This would be GREAT.
By the way I also currently use SYNCTHING which works nicely.
Thanks for your support and please help me if I posted on the wrong forum (but I was unable to find any othe BITLOCKER related info). 
The one thing I miss versus the Kodi install on Ubuntu is the ability to read and write BITLOCKER disks attached to USB, they simply are not recognized by LE. Is this the correct binary for gaining that ability?
No.
Thanks chewitt.
I wanted to give it a try, to see if anything changed since 2022 when I saw a similar post from Netizens, so I took the opportunity to install LE12.1.6 by sky42 .
Same problem as in 2022:
LE12:/dev # cryptsetup open /dev/sdb1 Windisk --type bitlk
Enter passphrase for /dev/sdb1:
device-mapper: reload ioctl on Windisk (253:0) failed: Invalid argument
Cannot activate device, kernel dm-zero module is missing.Eventually I decided to setup a new USB disk with ext4 and LUKS2, so that my data in encrypted since I use "syncthing" to spread it on my local network. It won't work when hooked to a Windows box, but at least it shouldn't be that trivial to read the disk if stolen.
It took some time but I think I suceeded, so if anybody is interested here below are the steps (and please correct me if anything wrong 
).
edit /etc/crypttab to ensure the disk is "open" when the system boots. In my case I used the UUID to make sure it will work regardless the USB port I connect the disk. Also used a plain text file (/storage/.config/k in this case) to hold the passkey so I don't need to type it every boot. In the example below, the disk is mapped to "SABRENT"
HTPC:/etc # more crypttab
# <target name> <source device> <key file> <options>
SABRENT UUID=24cf6569-8971-4406-975a-231de94a95e7 /storage/.config/k luks
HTPC:/etc # ls -la /dev/mapper/
total 0
drwxr-xr-x 2 root root 80 Sep 26 11:47 .
drwxr-xr-x 19 root root 3820 Sep 26 11:47 ..
lrwxrwxrwx 1 root root 7 Sep 26 11:47 SABRENT -> ../dm-0
crw------- 1 root root 10, 236 Sep 26 11:47 controlnext step would be to modify /etc/fstab to mount the disk at boot, but for reasons I don't know the file is read-only. So I found the example file "cryptsetup.mount.sample" and modified it according to its content. The resulting file in this example is called "storage-HDD250.mount". Remember to launch "systemctl enable storage-HDD250.mount" to ensure the disk is mounted at boot. I also created the directory "/storage/HDD250" where the disk is mounted.
HTPC:~/.config/system.d # ls -la
total 76
drwxr-xr-x 4 root root 4096 Aug 18 12:57 .
drwxr-xr-x 20 root root 4096 Sep 26 11:47 ..
-rw-r--r-- 1 root root 28816 Jul 15 2023 README
-rw-r--r-- 1 root root 1772 Aug 18 12:34 cifs.mount.sample
-rw-r--r-- 1 root root 2015 Aug 18 12:34 cryptsetup.mount.sample
drwxr-xr-x 2 root root 4096 Sep 25 20:55 kodi.target.wants
drwxr-xr-x 2 root root 4096 Sep 25 20:55 multi-user.target.wants
-rw-r--r-- 1 root root 1754 Aug 18 12:34 nfs.mount.sample
-rw-r--r-- 1 root root 1145 Aug 18 12:34 openvpn.service.sample
lrwxrwxrwx 1 root root 89 Sep 25 20:55 service.system.syncthing.service -> /storage/.kodi/addons/service.system.syncthing//system.d/service.system.syncthing.service
-rwxr--r-- 1 root root 2321 Sep 25 23:28 storage-HDD250.mount
-rw-r--r-- 1 root root 421 Aug 18 12:57 wireguard.service.sample
HTPC:~/.config/system.d #so in the end the disk should be useable by the system when boot is finished.
HTPC:~/.config/system.d # mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=3651348k,nr_inodes=912837,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=1515200k,nr_inodes=819200,mode=755)
/dev/sda1 on /flash type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/flash/SYSTEM on / type squashfs (ro,relatime,errors=continue)
/dev/sda2 on /storage type ext4 (rw,noatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
tmpfs on /var type tmpfs (rw,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=3788000k,nr_inodes=1048576)
/dev/mapper/SABRENT on /storage/HDD250 type ext4 (rw,nosuid,nodev)
HTPC:~/.config/system.d #Hope it helps, since I'm not an expert on Linux.
My next challenge will be to setup LE12 on a single internal SATA SSD with two partitions -- LE itself plus a LUKS partition for data & syncthing, so that I can get rid of the USB. Learning.... 
My next challenge will be to setup LE12 on a single internal SATA SSD with two partitions -- LE itself plus a LUKS partition for data & syncthing, so that I can get rid of the USB.
Well, here is what worked for me.
Installed LE12 ( sky42 version) on an internal 120GB SSD.
Then cloned the SSD with Clonezilla, towards a 1TB SSD in USB.
Ended up with a LE partition (EXT4) and 880GB of free space. With a suitable Linux distro (used Ubuntu to be on safe side), formatted the extra space as EXT4 with LUKS, the swapped the SSD on the LE PC. The rest is the same as in my previous post.
Did some experiment trying to resize the LE partition, with a Linux distro. Not sure why, but it worked only 1 time, the rest of tests resulted in a "no boot", so it's better to keep the LE partition unchanged.
Hope it helps.
Display Moreversion 12.0.1-#241005 (not for RockChip)
download link https://sky42.libreelec.tv/release/12.0/
based on LE 12.0.1 https://github.com/LibreELEC/LibreELEC.tv/tree/12.0.1
changelog
- upstream update
- enabled kernel option CONFIG_DM_ZERO=m ( Pinot62 reported a error for bitlocker)
- functions: BUILD dir marked with CACHEDIR.TAG
- linux: update to 6.6.54 (Rockchip needs work)
my source diff https://github.com/LibreELEC/Libr…v:12.0.1-241005
Thanks you so much sky42 !
Gave it a try, and seems to be working fine! Below my tests with an existing BITLOCKER volume.
LE12:~ # ls -la /dev/sd*
brw-rw---- 1 root disk 8, 0 Oct 7 11:39 /dev/sda
brw-rw---- 1 root disk 8, 1 Oct 7 11:39 /dev/sda1
brw-rw---- 1 root disk 8, 2 Oct 7 11:39 /dev/sda2
brw-rw---- 1 root disk 8, 3 Oct 7 11:40 /dev/sda3
brw-rw---- 1 root disk 8, 16 Oct 7 11:42 /dev/sdb
brw-rw---- 1 root disk 8, 17 Oct 7 11:42 /dev/sdb1
LE12:~ #
LE12:~ #
LE12:~ # blkid
(...)
/dev/sdb1: TYPE="BitLocker" PARTUUID="000b1971-01"
(...)
LE12:~ #
LE12:~ #
LE12:~ # cryptsetup open /dev/sdb1 disk1 --type bitlk
Enter passphrase for /dev/sdb1:
LE12:~ #
LE12:~ #
LE12:~ #
LE12:~ # ls -la /dev/mapper
total 0
drwxr-xr-x 2 root root 100 Oct 7 11:47 .
drwxr-xr-x 19 root root 3780 Oct 7 11:47 ..
crw------- 1 root root 10, 236 Oct 7 11:39 control
lrwxrwxrwx 1 root root 7 Oct 7 11:47 disk1 -> ../dm-1
LE12:~ #
LE12:~ # mount /dev/mapper/disk1 /storage/NAS
LE12:~ #
LE12:~ # cd NAS/
LE12:~/NAS # ls -la
total 60865381
drwxr-xr-x 1 root root 8192 Nov 20 2023 $RECYCLE.BIN
drwxrwxrwx 1 root root 24576 Sep 13 18:06 .
drwxr-xr-x 21 root root 4096 Oct 7 11:22 ..
-rwxr-xr-x 1 root root 649664 Sep 3 2015 DLB2410.dll
drwxr-xr-x 1 root root 8192 Oct 4 2015 DaneElec
-r-xr-xr-x 1 root root 528 Feb 1 2015 MediaID.bin
drwxr-xr-x 1 root root 131072 Sep 13 18:14 Musica
drwxr-xr-x 1 root root 8192 Sep 13 13:07 Musica DTS
drwxr-xr-x 1 root root 8192 Apr 10 19:11 Posta
drwxr-xr-x 1 root root 0 Jan 28 2014 RECYCLER
drwxr-xr-x 1 root root 16384 Feb 8 2020 Software
drwxr-xr-x 1 root root 8192 Nov 16 2023 System Volume Information
drwxr-xr-x 1 root root 0 Nov 23 2023 Utility
drwxr-xr-x 1 root root 8192 Sep 13 18:00 Video
LE12:~/NAS #sky42: ran into some trouble with the version 12.0.1-#241005.
Some of the video content does not play smooth, video is chunky and frequent audio-video resync.
Probably something due to the different version of Kodi embedded in this release.
Switch back to the august version solved the issue.
Just to let you know... thanks so much anyway for your job! 
As these builds are based on nightlies, I guess no official addon repos will work?
LE12 nightlies use the same repo as official LE12 releases. There's nothing particularly special about nightlies.
i'm really not familiar with the udev process to mount raid arrays on boot, I appreciate this isn't a LibreELEC issue, but can anyone point me in the direction of which rules I would need to create/edit?
The raid array is assembled at boot
LibreELECpc:/sys/devices/virtual/block/md0/md # journalctl | grep md0
Nov 01 06:09:16 LibreELECpc kernel: md/raid1:md0: active with 2 out of 2 mirrors
Nov 01 06:09:16 LibreELECpc kernel: md0: detected capacity change from 0 to 976508928
Nov 01 06:09:16 LibreELECpc systemd[1]: Started [email protected].
Nov 01 06:09:16 LibreELECpc systemd[1]: [email protected]: Deactivated successfully.
Nov 01 06:09:16 LibreELECpc systemd[1]: Stopped [email protected].LibreELECpc:/usr/lib/udev/rules.d # fsck /dev/md0
fsck from util-linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
/dev/md0: clean, 12/30523392 files, 2197339/122063616 blocksagain any pointers would be so helpfull
I can mount the raid array with the command below.
/usr/bin/systemctl restart udevil-mount@/dev/md0.servicenot sure why it doesn't happen automatically