Hello, The prompt for the LUKS password is handled by the /scripts/local-top/cryptroot script which is where the prompt for the passphrase happens. So the kdump-tools scripts have no way to interact with that phase of the boot.
The problem you seem to be facing is console redirection. When testing with Debian stable in a VM, the password prompt do appear but most often in the middle of garbled console output. If the console is redirected to TTYS0 (by adding console=ttyS0 to the boot params), it does appear at the console : > [ 81.689863] Call Trace: > [ 81.690088] [<ffffffff8ce098f5>] ? __handle_sysrq+0xe5/0x140 > [ 81.690592] [<ffffffff8ce09d7b>] ? write_sysrq_trigger+0x2b/0x30 > [ 81.691243] [<ffffffff8cc6697d>] ? proc_reg_write+0x3d/0x60 > [ 81.691826] [<ffffffff8cbfb0c3>] ? vfs_write+0xb3/0x1a0 > [ 81.692382] [<ffffffff8cbfc4a2>] ? SyS_write+0x52/0xc0 > [ 81.692927] [<ffffffff8cc1a365>] ? SyS_dup2+0x95/0x100 > [ 81.693719] [<ffffffff8cfe8cb6>] ? system_call_fast_compare_end+0xc/0x96 > [ 81.694456] Code: c4 08 48 c7 c7 a1 04 23 8d 5b 5d 41 5c 41 5d 41 5e 41 5f > e9 a1 96 d0 ff 90 66 66 66 66 90 c7 05 b9 2a 89 00 01 00 00 00 0f ae f8 <c6> > 04 25 00 00 00 00 01 c3 0f 1f 44 00 00 66 66 66 66 90 53 8d > [ 81.698673] RIP [<ffffffff8ce091d2>] sysrq_handle_crash+0x12/0x20 > [ 81.699379] RSP <ffff9399389b3e88> > [ 81.699746] CR2: 0000000000000000 > WARNING: Failed to connect to lvmetad. Falling back to device scanning. > Volume group "debian8-vg" not found > Cannot process volume group debian8-vg > WARNING: Failed to connect to lvmetad. Falling back to device scanning. > Volume group "debian8-vg" not found > Cannot process volume group debian8-vg > Please unlock disk vda5_crypt: So kexec-tools has no solution for this issue as it lies outside of its control. The problem happens long before kdump-tools even gets involved. Kind regards, ...Louis -- Louis Bouchard Software engineer, Ubuntu Developer / Debian Maintainer GPG : 429D 7A3B DD05 B6F8 AF63 B9C4 8B3D 867C 823E 7A61
