Posts by DimaKompot

Currently I'm using Odroid XU4 + Cloudshell 2. On the system itself I have OMV, few samba shares with movies/series for Kodi, nextcloud, transmission and not much more.

But seems that XU4 isn't enough to run full disk encryption: during torrent downloads system is really slow and unresponsive.

So I need something with hardware encryption acceleration, on par or faster that XU4 (it's 6 years old already), have ability to connect 2-4 full size HDD, have some alive community around it. I don't care about video out or video decoders.

Is there anything available on the market in 2022 that suits my needs? Or should I just give up on idea of having ARM board and invest in x86_64 mini PC?

Just find out that it will hang upgrade of the package docker-ce because it waits for the service to start. So before the upgrade you should unlock your LUKS volume.

For everybody, like myself, who was searching answer on this question - I wrote small guide on it:

[How-To] Wait for LUKS unlock before start Docker containers

For everybody, like myself, who was searching answer on this question - I wrote small guide on it:

[How-To] Wait for LUKS unlock before start Docker containers

Problem

I have my hard drives encrypted with LUKS. Passphrase to unlock drives can be only typed in in the OMV WebUI. I don't want to use auto unlock. Encrypted hard drives have directories that are in use by some of mine Docker containers (nextcloud, transmission). I don't want let those containers to start before the unlock. It will fail, produce some garbage on the filesystem and then I will have manually restart those containers.

Fix

We need script that will wait for the unlock and only then start Docker service

Script

You can copy the code from my GitHub (wait-for-unlock.sh) and put it to /usr/local/bin/ or just download it directly from your device:

sudo wget -P /usr/local/bin/ https://raw.githubusercontent.com/Virusmater/OdroidXU4-Cloudshell2-OMV/master/usr/local/bin/wait-for-unlock.sh
sudo chmod a+x /usr/local/bin/wait-for-unlock.sh

Docker Service

Make an override of an existing configuration

sudo systemctl edit docker

and add the script execution before the start

[Service]
ExecStartPre=/usr/local/bin/wait-for-unlock.sh

that will create file /etc/systemd/system/docker.service.d/override.conf with that configuration. You can also check it on GitHub (override.conf)

Final

Script wait-for-unlock.sh is quite dummy and checks only for "/dev/mapper/sda-crypt" device. Any other ideas and PRs are welome!

From now on Docker service will wait for the unlock before starting any containers.

Quote from Matze Kalle

My disks also don't auto mount after unlocking the encryption. I'm using OMV5 on a RasPi3B. There is no env var called OMV_LUKS_MOUNT_ON_UNLOCK in

/etc/default/openmediavault on my machine.

If there is no variable - add one. Restart few times after. Now it works for me somehow.

Hello ryecoaaron,

I'm using Ordoid XU4 (Raspbian). I installed a new fresh system today with OMV on top of it with your installation script. And now I don't have any /dev/zram device and also don't have any swap anymore. Went through latest changes and find that topic. Is it an expected behavior?

root@odroidxu4:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    0  5.5T  0 disk 
mmcblk0      179:0    0 29.1G  0 disk 
└─mmcblk0p1  179:1    0 28.8G  0 part /
mmcblk0boot0 179:16   0    4M  1 disk 
mmcblk0boot1 179:32   0    4M  1 disk 

root@odroidxu4:~# free
              total        used        free      shared  buff/cache   available
Mem:        2043820      191824     1533760       28384      318236     1761480
Swap:             0           0           0

Personally I ended up with unlocking LUKS disk from the Web UI and making simple cron job: check if disk was unlocked - then mount and restart docker.

@Marshin I can confirm it. On OMV5 unlocked partition doesn't auto mount