Unable to boot the system after configuring HA-LVM setup

Solution Verified - Updated -

Issue

  • After configuring HA-LVM setup on cluster nodes using tagging variant as per the steps described in solution 3067 cluster node is unable to boot successfully and shows following kernel panic error messages on console:

    on RHEL 6 cluster nodes:

    Kernel panic - not syncing: Attempting to kill init!
    Pid; 1, comm: init Not tainted 2.6.32.279.14.1.el6.x86_64 #1
    Call Trace:
     [<ffffffff814fd98a>] ? panic+0xa0/0x168
     [<ffffffff81070c42>] ? do_exit+0x862/0x870
     [<ffffffff8117d0a5>] ? fput+0x25/0x30
     [<ffffffff81070ca8>] ? do_group_exit+0x58/0xd0
     [<ffffffff81070d37>] ? sys_exit_group+0x17/0x20
     [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b
    

    on RHEL 5 cluster nodes:

    Unable to access resume device (/dev/VolGroup00/swap)
    mount: could not find filesystem '/dev/root'
    setuproot: moving /dev failed: no such file or directory
    setuproot: error mounting /proc: no such file or directory
    setuproot: error mounting /sys: no such file or directory
    switchroot: mount failed: no such file or directory
    kernel panic - no syncing: attempted to kill init!
    

Environment

  • Red Hat Enterprise Linux 5, 6 (with High Availability Add-On)
  • HA-LVM (using tagging variant)

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
Close

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