From: Julian Wolf <juwolf-l3A5Bk7waGM@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: 90crypt and disk-by-id in crypttab
Date: Fri, 30 May 2014 13:59:07 +0200 [thread overview]
Message-ID: <6741208.yq6nlQL6aV@e117> (raw)
Hi all,
there seems to be a problem with 90crypt (especially parse-crypt.sh) when the
disk is specified by-id in /etc/crypttab.
I'm not quite sure how and where to tackle this issue reasonable so I'll start
with what I found out until now:
I'm running dracut with systemd, $LUKS is not empty.
If devices are specified by-id (/dev/disk/by-id/...) in /etc/crypttab,
'crypttab_contains "$luksid"' always returns false, so udev rules
are created which try to start "systemd-cryptsetup@luks$$(dev_unit_name
-$env{ID_FS_UUID}).service" which doesn't exist and results in error messages
(No such file or directory).
In my case this doesn't break the system as the correct systemd-
cryptsetup@$(disk-by-id) services are created and linked to
cryptsetup.target.requires. The system comes up fine.
The error messages are just confusing and misleading, especially when
searching for other errors.
So where would be a good point to fix this problem? Extend the
"crypttab_contains" function not only to check uuid but all other possible
device identifiers, too?
Regards,
Julian
--
Julian Wolf, Working student
SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
Maxfeldstr. 5 / D-90409 Nürnberg
reply other threads:[~2014-05-30 11:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6741208.yq6nlQL6aV@e117 \
--to=juwolf-l3a5bk7wagm@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.