The size of initrd for kdump sometimes becomes zero

Solution Verified - Updated -

Issue

  • The size of initrd for kdump sometimes becomes zero after the kernel crashed and then kdump ran. So the next kdump execution fails to boot because rootfs can not be mounted.
    1) Remove the initrd of kdump.
     # rm /boot/initrd-2.6.32-216.el6.i686kdump.img

    2) Restart kdump service.
     # service kdump restart

    3) Crash the kernel.
     # echo c > /proc/sysrq-trigger

    4) The size of initrd becomes 0KB.
    -rw-------. 1 root root        0 Nov 24 00:01 2011
    initrd-2.6.32-220.el6.i686kdump.img

Environment

  • Red Hat Entreprise Linux 6.2 (arch x86)
  • kexec-tools

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.