Bug 1050299 - systemd, udev 228-25.6.1 encrypt partitions on (NVMe)-SSDs are not identified, decrypted and mounted propery
Summary: systemd, udev 228-25.6.1 encrypt partitions on (NVMe)-SSDs are not identified...
Status: RESOLVED DUPLICATE of bug 1048679
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Leap 42.2
Hardware: x86-64 openSUSE 42.2
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: systemd maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-24 17:57 UTC by Max Moritz
Modified: 2017-07-24 19:00 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Max Moritz 2017-07-24 17:57:01 UTC 
While boot process encrypted partitions on SSDs are not identified, decrypted and mounted properly. Therefore such partitions are neither available after boot nor mountable by hand. It seems at identify by UUID something goes wrong.

The relevant log-output is:
dev-disk-by\x2did-nvme\x2d[proper UUID]\x2dpart6.device


With version 228-13.1 the boot process goes correctly. In this case the log-output is:
device /dev/disk/by-id/nvme-[proper UUID]-part6

Only encrypted partition on (NVMe)-SSDs are affected. Notencryped partition and patitions on HDDs are not effected.
Comment 1 Franck Bui 2017-07-24 18:57:05 UTC 
Already reported and we're working on a fix.

*** This bug has been marked as a duplicate of bug 1048679 ***
Comment 2 Franck Bui 2017-07-24 19:00:42 UTC 
In the meantime, you can solve the problem manually by replacing the by-id paths used in /etc/crypttab with the new relevant "by-id" format that you can find out by doing "ls /dev/disk/by-id/nvme-*".

That's actually the best fix as you will switch to the new by-id format supported by upstream.