@ddelamarre and @jolla4ever,
I am sorry for coming across so grumpy here, because you both were kind and did not demand anything. Specifically @ddelamarre offering his support (and assuming @carmenfdezb would be also willing to test) lets me consider to pick this up, again. Additionally this has become the main reason why I am using outdated SailfishOS releases on my production phones, as Jolla seems to have addressed many of the flaws of 3.4.0 and the early 4.x.y releases (a time where I had the impression that every new release was even buggier than its predecessor).
@ddelamarre, I remember to have the latest release of crypto-sdcard
working nicely on SailfishOS 4.0.1, when plugging in an external USB-stick (or any other USB attached mass storage device) with LUKS volume(s) on it after SailfishOS has booted. Using an USB-attached storage device (can be almost any old USB-stick with a USB-C / µUSB to USB-A adapter (cable)) is the most convenient way to test, because observing the auto-mounting to succeed or fail is just a matter of re-plugging, in contrast to rebooting with an SD-card as DUT. And the current work-item of auto-mounting when booting can be tested with an USB-stick and a SD-card alike.
I am planning to pick this up again in the upcoming weeks where I stopped 1,5 years ago: With one of my testing phones on SFOS 4.0.1. When I have that working, I plan start to upgrade SFOS and check if crypto-sdcard
is still working on every subsequent release (currently 4.1.0, 4.2.0, 4.3.0 and 4.4.0).
AFAIR remember, the remaining issue on 4.0.1 was that unlocking LUKS volumes happened “too early” in the boot process, thus failing. But it should happen as early as possible in order not to slow down the boot process and the timing was fine on SFOS < 4. Systemd allows for thorough analysis of the startup process (“bootchart”) and dependency chains (forward and reverse) of units. One has to find the culprit, i.e., the specific unit which has to run before the unlocking for it to succeed.
As a first step it would be helpful to know is SFOS 4.4.0 still behaves like SFOS 4.0.1 when using USB-attached storage.
And, please let us move this conversation to GitHub, because any further discussion is misplaced as FSO, as it solely deals with crypto-sdcard
. You may continue in the old thread there, i.e., issue #115.