Bug 1159987
| Summary: | Systemd prevents to mount an encrypted home directory | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pierre Juhen <pierre.juhen> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | gordon+rhbugs, johannbg, jsynacek, lnykryn, msekleta, pierre.juhen, s, systemd-maint, vpavlin, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-11-14 04:56:27 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
Pierre Juhen
2014-11-03 19:28:18 UTC
This bug is NOT corrected by 208-26 !!! Relevant log messages is : Unit home-pierre.mount is bound to inactive service. Stopping, too. I have a LUKS-encrypted home and it always mounts correctly on boot. Please, provide output of "journalctl -b" when the mount fails, your /etc/fstab and /etc/crypttab (minus any sensitive info that might be there, of course). I just did a "yum update" and rebooted my F20 laptop and encountered what sounds like the same problem. I would attempt a manual mount of my encrypted partition ("mount /dev/mapper/hax-crypt /crypt") and it would be immediately unmounted per these messages in /var/log/messages:
Nov 10 17:37:25 hax kernel: [ 67.075132] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov 10 17:37:25 hax kernel: EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov 10 17:37:25 hax systemd: Unit crypt.mount is bound to inactive service. Stopping, too.
Nov 10 17:37:25 hax systemd: Unmounting /crypt...
Nov 10 17:37:25 hax systemd: Unmounted /crypt.
If I made a directory named /crypt2 and mount to there instead, all worked fine. I checked /etc/fstab and I had this entry:
/dev/mapper/luks-05da92de-5fc1-495a-8c07-5ea8bf931a55 /crypt ext4 defaults,x-systemd.device-timeout=0,noauto 1 2
I don't think this is a new entry since /etc/fstab is dated from last December. Anyway, I'm commented out that entry and rebooted and things seem to be working fine again, at least for now. I'm hoping that dropping this entry won't cause any problems.
For completeness, I'll mention that I also had this corresponding entry in /etc/crypttab (but I didn't change it):
luks-05da92de-5fc1-495a-8c07-5ea8bf931a55 UUID=05da92de-5fc1-495a-8c07-5ea8bf931a55 none noauto
After the comment of Gordon, I did a check of /etc/fstab. Here is the correspondending entry : LABEL=home_pierre /home/pierre ext4 defaults,noauto,noatime,discard 1 2 I discoverde that the corresponding volume lost its label during maintenance operations, probably a long time ago. After putting the right label, it works. So it seems that systemd verifies more thoroughly the consistency of /etc/fstab. Thank you, Regards |