Bug 718601

Summary: "Password entry required for 'Please enter passphrase for disk" appears after network connection is established
Product: [Fedora] Fedora Reporter: Keywan Najafi Tonekaboni <bugzilla>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: harald, jdornak, johannbg, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-05 09:00:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg output none

Description Keywan Najafi Tonekaboni 2011-07-04 00:15:06 UTC 
Description of problem:

I'have the problem that everytime a network connection is established this message appears in any open shell:

"Password entry required for 'Please enter passphrase for disk TOSHIBA_FOOBAR (mycrypt)!' (PID 3778).


Version-Release number of selected component (if applicable):


How reproducible: every time


Steps to Reproduce:
1.open a terminal
2.connect to ethernet, wifi or broadband via applet (GUI)
3.message appears in every open shell
  
Actual results:
message appears

Expected results:
nothing, cause crypted partition is in use since hours

Additional info:
i'm using a lvm vg (with root, home, swap) inside a crypted partition called mycrypt. I changed the luks-partition name (/etc/crypttab) as well as the name of the vg (from the longname given bei the F15-installer to a shorter one)
Comment 1 Michal Schmidt 2011-07-04 11:14:09 UTC 
Please boot with "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg", reproduce the bug and then attach the output of the "dmesg" command. Thanks.
Comment 2 Keywan Najafi Tonekaboni 2011-07-04 23:42:37 UTC 
Created attachment 511227 [details]
dmesg output

hi, I hope this helps
Comment 3 Michal Schmidt 2011-07-05 00:40:54 UTC 
Your /etc/crypttab and initramfs disagree over the LUKS name of the device. Your initramfs opens it as "luks-3978fb1b-3f40-4a5f-a6d4-44f0a8b4af80" but the booted system attempts to unlock the same disk but to a different name "fbcrypt".
This fails repeatedly with "Failed to activate: Device or resource busy".

Either put the old name back to /etc/crypttab, or see if regenerating the initramfs (using dracut) helps. You may need to edit the rd_LUKS_UUID boot parameter too. I have not tested it.
Comment 4 Keywan Najafi Tonekaboni 2011-07-05 07:37:45 UTC 
ah, thanks, right, I changed the name in the /etc/crypttab. thanks for your help. But why this appears, when I establish a network connection?
Comment 5 Michal Schmidt 2011-07-05 09:00:36 UTC 
This part of the log provides a clue:

[  248.318639] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StartUnit() on /org/freedesktop/systemd1
[  248.318680] systemd[1]: Trying to enqueue job iscsi.service/start/replace
[  248.319247] systemd[1]: Installed new job iscsi.service/start as 923
[  248.319262] systemd[1]: Installed new job cryptsetup/start as 988

A start of iscsi.service is requested. The service Requires basic.target. basic.target Requires sysinit.target. sysinit.target Wants cryptsetup.target.

The start of iscsi.service is requested by /etc/NetworkManager/dispatcher.d/04-iscsi
Comment 6 Keywan Najafi Tonekaboni 2011-07-07 00:20:01 UTC 
Hi Michal,

thanks for the detailed explanation and your help. Sorry for the noise.

Kind Regards,

Keywan
Comment 7 Jakub Dorňák 2014-10-21 22:04:12 UTC 
But this is UX bug anyway §:o(

This happens to me any time I restart memcached.
It even breaks the shell.
Comment 8 Michal Schmidt 2014-10-22 09:15:20 UTC 
(In reply to Jakub Dorňák from comment #7)
Does your system have a similar mixup of LUKS names as described in comment #3?