[systemd-devel] luks - a particular device systemd treats differently?
lejeczek
peljasz at yahoo.co.uk
Wed Jun 2 09:00:49 UTC 2021
On 01/06/2021 22:05, Lennart Poettering wrote:
> On Di, 01.06.21 16:55, lejeczek (peljasz at yahoo.co.uk) wrote:
>
>> Hi guys.
>>
>> I have a crypttabl here:
>>
>> luks-devs /dev/mapper/dev1-devs /etc/.etc.enc.loop/crypttab.key
>> discard,nofail,timeout=3s,noauto
>> luks-home /dev/mapper/dev1-home /etc/.etc.enc.loop/crypttab.key
>> discard,nofail,timeout=3s,noauto
>> ...
>> plus a few more lines with all options just as those two. I have a fstab
>> here:
>>
>> /dev/mapper/luks-home /home ext4
>> noauto,nofail,noatime,nobarrier,noatime,x-systemd.device-timeout=3s 1 2
>> /dev/mapper/luks-devs /devs ext4
>> noauto,nofail,noatime,nobarrier,noatime,x-systemd.device-timeout=3s 1 2
>> ...
>>
>> when I check devices manually here:
>> ...
>> systemctl is-failed "systemd-cryptsetup at luks\x2ddevs.service" -q && {
>> systemctl restart "systemd-cryptsetup at luks\x2ddevs.service" && fsck.ext4
>> /dev/mapper/luks-devs && mount /devs; }
>>
>> then I get asked for passphrase and the rest gets going (intentional, as
>> those luks devs do not get opened at boot time) for all the devices except
>> for "devs"
>> As I understand systemd here does not see, mark that one device as "failed"
>> and I have no idea why systemd would do that for that one device.
>> Would somebody care to share so ideas?
> I am not sure I properly grok what you are trying to say, but: did you
> check the logs?
>
> Lennart
>
> --
> Lennart Poettering, Berlin
Yes I did, in logs is nothing in terms of errors or warning,
well, I could not find anything.
This I'll say if I try to rephrase my words earlier - I have
an number of luks devices which _all_ are "ignored" at boot
(as snippets from crypttab & fstab show) and are meant to be
opened & mounted only manually: so I check to open & mount
as above snippet shows and...
for all devices but one, I get from 'systemd' to mount manually.
Conditional check - systemctl is-failed ... - works for all
devices but that one.
Why?? no idea.
Would there be something specific I should be looking in
logs for?
many thanks, L.
More information about the systemd-devel
mailing list