Bug 26337 - Booting encrypted system: "warning /run/cryptsetup is missing" but works.
Summary: Booting encrypted system: "warning /run/cryptsetup is missing" but works.
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL:
Whiteboard: MGA7TOO, 8rc take 5
Keywords: 8rc1
Depends on:
Blocks:
 
Reported: 2020-03-13 00:25 CET by Morgan Leijström
Modified: 2021-02-03 17:24 CET (History)
1 user (show)

See Also:
Source RPM: cryptsetup
CVE:
Status comment:


Attachments

Description Morgan Leijström 2020-03-13 00:25:58 CET
Description of problem:
I dont remember seeing this before Mageia version 7.
I dont know if it may be pose reliability issue.
Clearly, it is not looking beautiful.

How reproducible:
Every boot, at the stage of entering LUKS key
(Not visible unless splash quiet is removed from kernel boot line)

Steps to Reproduce:
Install mga7 with unencrypted /boot (and EFI) and then make an encrypted partition for LVM, and in that have your /, /home, swap

After a short diggin i found this that may be relevant:
https://github.com/systemd/systemd/issues/7794#issuecomment-355112499
"cryptsetup upstream decided to switch default path to /run/cryptsetup/. As the last element of the path is created as a fallback (and /run/ exists anyway)"
Maybe we should adapt something?

I have no idea as to what to set this bug against?
Comment 1 Frank Griffin 2020-03-20 17:12:40 CET
The link you provided indicates that this is fixed in the latest cryptsetup, so assigning to shlomi as he seems to have the most commits.

Source RPM: (none) => cryptsetup
Assignee: bugsquad => shlomif
CC: (none) => ftg

Comment 2 Morgan Leijström 2021-02-03 17:24:13 CET
See it on mga8 Live w persistence

It is not in journal, only visible on screen if splash quiet is removed.

Keywords: (none) => 8rc1
Whiteboard: (none) => MGA7TOO, 8rc take 5
Version: 7 => Cauldron


Note You need to log in before you can comment on or make changes to this bug.