I'm having CentOS 7 64
installed on my desktop. After recent system update, I am getting below error while booting the CentOS 7
.
Some time system is able to boot and I can work on it. but it gives the same error at the time of next boot.
after entering this:
systemctl status kdump.service
I get this:
● kdump.service – Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)
Active: failed (Result: exit-code) since Thu 2015-01-22 02:55:49 MST; 39min ago
Main PID: 1139 (code=exited, status=1/FAILURE)Jan 22 02:55:49 localhost.localdomain kdumpctl[1139]: No memory reserved for crash kernel.
Jan 22 02:55:49 localhost.localdomain kdumpctl[1139]: Starting kdump: [FAILED]
Jan 22 02:55:49 localhost.localdomain systemd1: kdump.service: main process exited, code=exited, status=1/FAILURE
Jan 22 02:55:49 localhost.localdomain systemd1: Failed to start Crash recovery kernel arming.
Jan 22 02:55:49 localhost.localdomain systemd1: Unit kdump.service entered failed state.
Jan 22 02:55:49 localhost.localdomain systemd1: kdump.service failed.system-config-kdump:
command not found…
Adding image
Best Answer
Install the required packages
Modify grub
A kernel argument must be added to
/etc/grub.conf
to enable kdump. It’s called crashkernel and it can be either auto or set as a predefined value e.g. 128M, 256M, 512M etc.The line will look similar to the following:
Change the value of the
crashkernel=auto
tocrashkernel=128
orcrashkernel=256
...Regenerate grub configuration:
On a system with UEFI firmware, execute the following instead:
Open the
/etc/zipl.conf
configuration filelocate the parameters= section, and edit the crashkernel= parameter (or add it if not present). For example, to reserve 128 MB of memory, use the following:
crashkernel=128M
save and exitRegenerate the zipl configuration:
zipl
Enabling the Service
To start the
kdump
daemon at boot time, type the following command as root:This will enable the service for runlevels 2, 3, 4, and 5. Similarly, typing
chkconfig kdump off
will disable it for all runlevels.To start the service in the current session, use the following command as root: