[Bug 716136] New: systemd: doesn't mount my encrypted /home
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c0 Summary: systemd: doesn't mount my encrypted /home Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vuntz@suse.com QAContact: qa@suse.de Found By: --- Blocker: --- My encrypted /home doesn't get mounted with systemd. I do get the prompt, but nothing happens afterwards. Note that doing "systemctl restart cryptsetup@cr_sda3.service" doesn't help. This is my /etc/crypttab: cr_sda3 /dev/disk/by-id/ata-ST9160412AS_5VG1695C-part3 none none -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c1 --- Comment #1 from Vincent Untz <vuntz@suse.com> 2011-09-06 13:40:03 UTC --- Created an attachment (id=449359) --> (http://bugzilla.novell.com/attachment.cgi?id=449359) dmesg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c2 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #449359|0 |1 is obsolete| | --- Comment #2 from Vincent Untz <vuntz@suse.com> 2011-09-06 13:51:44 UTC --- Created an attachment (id=449362) --> (http://bugzilla.novell.com/attachment.cgi?id=449362) dmesg with systemd debug info :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c3 --- Comment #3 from Vincent Untz <vuntz@suse.com> 2011-09-06 13:57:19 UTC --- Relevant fstab line: /dev/mapper/cr_sda3 /home ext4 acl,user_xattr,noauto 0 0 Could it be the noauto? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c4 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@novell.com Component|Basesystem |Release Notes AssignedTo|bnc-team-screening@forge.pr |ke@suse.com |ovo.novell.com | QAContact|qa@suse.de |coolo@suse.com --- Comment #4 from Vincent Untz <vuntz@suse.com> 2011-09-06 14:10:08 UTC --- So apparently, removing noauto is enough for this. An alternative is to change the flags to "...,noauto,comment=systemd.automount". As I certainly didn't add noauto myself, I can only assume we used to create encrypted partitions this way, and so on upgrade to 12.1, this will possibly be an issue people will hit. So it should at least get documented in the release notes that people should remove the noauto flag themselves. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c5 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com --- Comment #5 from Ludwig Nussel <lnussel@suse.com> 2011-09-09 13:55:21 CEST --- YaST can in theory correct such things on upgrade. It should be nofail instead of noauto though (boot.crypto can time out and you don't want to fall into single user mode then). The noauto is probably from a time when nofail wasn't supported. It needs to be clarified whether yast still adds 'noauto' nowadays. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c6 --- Comment #6 from Frederic Crozat <fcrozat@suse.com> 2011-09-09 12:05:22 UTC --- just for the record, boot.crypto isn't used at all under systemd (but similar feature in systemd can also timeout ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c7 --- Comment #7 from Ludwig Nussel <lnussel@suse.com> 2011-09-09 14:12:35 CEST --- I know but if the installation is not migrated to systemd just removing noauto would be wrong. nofail is needed to prevent emergency mode in boot.localfs then. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c8 --- Comment #8 from Frederic Crozat <fcrozat@suse.com> 2011-09-09 12:14:03 UTC --- boot.localfs is also disabled under systemd ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c9 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |vuntz@suse.com --- Comment #9 from Karl Eichwalder <ke@suse.com> 2011-09-22 09:06:20 CEST --- To write a proper release notes entry (without doing research first), I need a summary, please ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c10 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|vuntz@suse.com | --- Comment #10 from Vincent Untz <vuntz@suse.com> 2011-09-22 14:04:32 UTC --- Karl, something like this would do it: "If you are using encrypted partitions, and you notice they are not automatically mounted with systemd, a likely cause is the 'noauto' flag in /etc/fstab for these partitions. Simply remove this flag. For instance, change the following line: /dev/mapper/cr_sda3 /home ext4 acl,user_xattr,noauto 0 0 to /dev/mapper/cr_sda3 /home ext4 acl,user_xattr 0 0 " -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c11 --- Comment #11 from Ludwig Nussel <lnussel@suse.com> 2011-09-22 16:15:37 CEST --- /dev/mapper/cr_sda3 /home ext4 acl,user_xattr,nofail 0 2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c12 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de --- Comment #12 from Christian Boltz <suse-beta@cboltz.de> 2011-10-09 19:33:46 CEST --- If the example is changed to use "nofail", then the sentence Simply remove this flag. should be changed to Simply replace the "noauto" flag with "nofail". That said: I'd really welcome if this was fixed automatically by YaST or zypper dup. Shouldn't be too hard IMHO - the following sed command in %post of cryptsetup (or another package) should work: (Warning: untested!) sed -i '/^\/dev/mapper/cr_/ s/,noauto,nofail/' etc/fstab -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c13 --- Comment #13 from Christian Boltz <suse-beta@cboltz.de> 2011-10-10 12:32:25 CEST --- (In reply to comment #12)
dup. Shouldn't be too hard IMHO - the following sed command in %post of cryptsetup (or another package) should work: (Warning: untested!) sed -i '/^\/dev/mapper/cr_/ s/,noauto,nofail/' etc/fstab
Argh, obviously untested :-/ sed -i '/^\/dev\/mapper\/cr_/ s/,noauto,/nofail/' etc/fstab Untested again, but at least the syntax should be correct now ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c14 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ke@suse.com Component|Release Notes |Basesystem AssignedTo|ke@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|coolo@suse.com |qa@suse.de --- Comment #14 from Karl Eichwalder <ke@suse.com> 2011-10-13 16:44:11 CEST --- Once again, it too confusing to write a release notes entry. Please, fix the reported bug first; see comment 12 and 13. Once done, please provide an update RN entry and assign the bug to me again. (I hope that this procedure is ok with you.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c15 --- Comment #15 from Vincent Untz <vuntz@suse.com> 2011-10-13 14:57:25 UTC --- Karl: is comment 10 not enough? (with the change mentioned by Luwdig and Christian in comments 11 & 12) I'm unsure what package would fix this on upgrades anyway -- the way you reassigned the bug, nothing will get fixed :/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c16 --- Comment #16 from Christian Boltz <suse-beta@cboltz.de> 2011-10-13 21:25:58 CEST --- (In reply to comment #15)
I'm unsure what package would fix this on upgrades anyway
The boot.crypto initscript and /etc/crypttab are both owned by cryptsetup, which is maintained by Ludwig. I'm sure he's a better assignee than the screening team for this bug. Ludwig, what do you think about fixing this bug with sed on /etc/fstab in %post of cryptsetup? See comment #13 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c17 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|bnc-team-screening@forge.pr |ke@suse.com |ovo.novell.com | --- Comment #17 from Karl Eichwalder <ke@suse.com> 2011-10-14 09:30:04 CEST --- (In reply to comment #15)
Karl: is comment 10 not enough? (with the change mentioned by Luwdig and Christian in comments 11 & 12)
Literal diffs are always a PITA ;) But otherwise, you are right. Here is the merged version that I'm going to add to the RN: <title>Mounting Encrypted Partitions with systemd</title> <para> If encrypted partitions are not automatically mounted with systemd, the 'noauto' flag in <filename>/etc/fstab</filename> for these partitions could be the cause. Replacing this flag with 'nofail' will fix it. For instance, change the following line:</para> <screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr,noauto 0 0</screen> <para> to </para> <screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr 0 0</screen> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c18 --- Comment #18 from Karl Eichwalder <ke@suse.com> 2011-10-14 09:35:22 CEST --- (In reply to comment #16)
(In reply to comment #15)
I'm unsure what package would fix this on upgrades anyway
The boot.crypto initscript and /etc/crypttab are both owned by cryptsetup, which is maintained by Ludwig. I'm sure he's a better assignee than the screening team for this bug.
Ludwig, what do you think about fixing this bug with sed on /etc/fstab in %post of cryptsetup? See comment #13
I cloned the bug: bnc#724113 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c19 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #19 from Karl Eichwalder <ke@suse.com> 2011-10-14 10:40:31 CEST --- Done (sr to Factory). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c20 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #20 from Christian Boltz <suse-beta@cboltz.de> 2011-10-14 13:46:36 CEST --- (In reply to comment #17)
Literal diffs are always a PITA ;)
Yes, seems so ;-)
<screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr,noauto 0 0</screen> <para> to </para> <screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr 0 0</screen>
The last line should contain acl,user_xattr,nofail (the ",nofail" is missing). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c21 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #21 from Karl Eichwalder <ke@suse.com> 2011-10-14 16:00:29 CEST --- Thanks for spotting (no, I did not do this intentionally)! Now fixed in SVN: <sect3 id="crypto-part-systemd"> <!-- bnc#716136 --> <title>Mounting Encrypted Partitions with systemd</title> <para> If encrypted partitions are not automatically mounted with systemd, the <literal>noauto</literal> flag in <filename>/etc/fstab</filename> for these partitions could be the cause. Replacing this flag with <literal>nofail</literal> will fix it. For instance, change the following line:</para> <screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr,noauto 0 0</screen> <para>to</para> <screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr,nofail 0 0</screen> </sect3> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c22 --- Comment #22 from Ludwig Nussel <lnussel@suse.com> 2011-10-14 16:05:29 CEST --- now if you also change the last zero to 2 you get fsck too -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c23 --- Comment #23 from Karl Eichwalder <ke@suse.com> 2011-10-17 10:53:07 CEST --- Thanks, fixed in SVN. To avoid confusion, I changed both entries (old and new): .. <screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr,noauto 0 2</screen> <para>to</para> <screen>/dev/mapper/cr_sda3 /home ext4 acl,user_xattr,nofail 0 2</screen> </sect3> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=716136 https://bugzilla.novell.com/show_bug.cgi?id=716136#c24 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #24 from Karl Eichwalder <ke@suse.com> 2011-10-21 09:34:29 CEST --- submitted again -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com