Bug 1471240

Summary: timed out wainting for device dev-mapper-luks\[funny\letters].device
Product: [Fedora] Fedora Reporter: Łukasz Posadowski <mail>
Component: luks-toolsAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: extras-orphan, renault
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 17:51:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Łukasz Posadowski 2017-07-14 19:16:42 UTC
Description of problem:
I'm unable to mount encrypted /home partition at boot time.

Version-Release number of selected component (if applicable):
Fedora Rawhide with lastest updates on 14th July 2017.

How reproducible:
Always, at boot time.

Steps to Reproduce:
1. Boot a PC with encrypted partitions
2. wait for luks password prompt
3. be able to boot only in emergency mode

Actual results:
I can login as root and mount partition manually:
# cryptsetup luksOpen /dev/sda5/ crypthome
# mount /dev/mapper/crypthome /mnt/somedir

All the data is here, but for some reason it can't mount as a /home at boot time.

I read some journalctl and it mentions those errors:
Timed out wainting for device dev-mapper-luks\[funny\letters].device
deendency failed for File System Check on /dev/mapper/luks-[funny-letters]
home.mount: Job home.mount/start failed with result 'dependency'

I have very little experience with encryption, so I don't know where to look next. I'll be thankful for some guides.

Thanks.

Comment 1 Couret Charles-Antoine 2017-07-16 20:26:06 UTC
I have exactly the same issue with my Fedora Rawhide after a update the 14th July...

Comment 2 Couret Charles-Antoine 2017-07-21 15:01:24 UTC
Issue is goe after another set of update (kernel + systemd)

Comment 3 Łukasz Posadowski 2017-07-21 20:04:26 UTC
(In reply to Couret Charles-Antoine from comment #2)
> Issue is goe after another set of update (kernel + systemd)

Those sneaky kernels. :) Thanks for the info. Thanks for the patches and updates, too.

Comment 4 Jan Kurik 2017-08-15 09:16:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 5 Ben Cotton 2018-11-27 18:29:52 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2018-11-30 17:51:29 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.