Description of problem: If the root partition was encrypted during installation, kdump service fails to start/enable/arm. Version-Release number of selected component (if applicable): kexec-tools-2.0.4-11.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1. Install system with encrypted / 2. Look at kdump service status 3. Actual results: kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: failed (Result: exit-code) since Tue 2014-03-18 11:13:55 CET; 14min ago Process: 1392 ExecStart=/usr/bin/kdumpctl start (code=exited, status=1/FAILURE) Mar 18 11:13:54 pintsize.usersys.redhat.com kdumpctl[1392]: No kdump initial ramdisk found. Mar 18 11:13:54 pintsize.usersys.redhat.com kdumpctl[1392]: Rebuilding /boot/initramfs-3.13.5-103.fc19.x86_64kdump.img Mar 18 11:13:55 pintsize.usersys.redhat.com kdumpctl[1392]: Device /dev/sda2 is encrypted, can not be used in kdump. Mar 18 11:13:55 pintsize.usersys.redhat.com systemd[1]: kdump.service: main process exited, code=exited, status=1/FAILURE Mar 18 11:13:55 pintsize.usersys.redhat.com systemd[1]: Failed to start Crash recovery kernel arming. Mar 18 11:13:55 pintsize.usersys.redhat.com systemd[1]: Unit kdump.service entered failed state. Expected results: Service active Additional info:
Please test with latest build to see if this still exists...
Similar to Bug 1028397
This problem should have been fixed with latest kexec-tools. Following is the kexec-tools commit. commit 906dc0bca0c7056cd2cc4d9bed9a9b304af6d0a9 Author: arthur <zzou> Date: Wed Feb 19 10:02:19 2014 +0800 Relax restriction of dumping on encrypted target Description: Currently kdumpctl will fail to create kdump initramfs and start kdump service while dump target is encrypted. This restriction is too strict. Resolution: Just warn user that encrypted device is in dump path and second kernel will wait on console for password to be entered. Signed-off-by: arthur <zzou> Acked-by: Vivek Goyal <vgoyal> Please test again. I would like to close this bug.
will kexec-tools-2.0.4-21.fc19 be enough or do I need even newer ones?
I see that 2.0.4-25 is the nearest release after the fix. So 2.0.4-21 is not going to be good enough. Take an fc20 package same or higher than -25.
I can confirm that with kexec-tools-2.0.4-27.fc20.x86_64 I don't get the "Device /dev/sda2 is encrypted" message. With unconfigured kdump, I'm getting the standard "No space for kernel image" error, while when I configure kdump, the arming or recovery kernel is successful. As such, the issue is fixed in F20.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.