実行しているファームウェアのバージョンが v5.06 以下の cciss ターゲットに kdump がコアファイルをダンプできない

Issue

• kdump が cciss ターゲットでダンプファイルを保存できず、以下のエラーが発生します。

• コンソールでエラーが継続します。

    Making device-mapper control node
    Scanning logical volumes
      Reading all physical volumes.This may take a while...
      No volume groups found
      No volume groups found
    Activating logical volumes
      No volume groups found
      No volume groups found
    Saving to the local filesystem /dev/mapper/vg0-dump
    e2fsck 1.38 (30-Jun-2005)
    fsck.ext3: while trying to open /dev/mapper/vg0-dump


    The superblock could not be read or does not describe a correct ext2
    filesystem.If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>

    fsck.ext3: 
    mount:Mounting /dev/mapper/vg0-dump on /mnt failed:No such file or directory
    Attempting to enter user-space to capture vmcore
    Creating root device.
    Checking root filesystem.
    fsck 1.38 (30-Jun-2005)
    fsck:WARNING: couldn't open /etc/fstab:No such file or directory
    e2fsck 1.38 (30-Jun-2005)
    fsck.ext2: while trying to open /dev/vg0/lv_root

    The superblock could not be read or does not describe a correct ext2
    filesystem.If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>

    fsck.ext3: 
    mount:Mounting /dev/mapper/vg0-dump on /mnt failed:No such file or directory
    Attempting to enter user-space to capture vmcore
    Creating root device.
    Checking root filesystem.
    fsck 1.38 (30-Jun-2005)
    fsck:WARNING: couldn't open /etc/fstab:No such file or directory
    e2fsck 1.38 (30-Jun-2005)
    fsck.ext2: while trying to open /dev/vg0/lv_root

    The superblock could not be read or does not describe a correct ext2
    filesystem.If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>

    fsck.ext2: 
    Mounting root filesystem.
    Trying mount -t ext4 /dev/vg0/lv_root /sysroot
    Trying mount -t ext3 /dev/vg0/lv_root /sysroot
    Trying mount -t ext2 /dev/vg0/lv_root /sysroot
    Trying mount -t minix /dev/vg0/lv_root /sysroot
    unable to mount rootfs.Dropping to shell

• コンソールログのエラー:

        Loading cciss.ko module
        cciss 0000:05:00.0:Controller claims that 'Bit 2 doorbell reset' is supported, but not 'bit 5 doorbell reset'.Firmware update is recommended.
        cciss 0000:05:00.0: cciss:Trying to put board into performant mode
        cciss 0000:05:00.0:Placing controller into performant mode
        cciss 0000:05:00.0:Waiting for board to soft reset.
        cciss 0000:05:00.0: board not ready, timed out.
        cciss 0000:05:00.0:Soft reset had no effect.
        cciss 0000:05:00.0:Soft reset failed.
        cciss: probe of 0000:05:00.0 failed with error -1
        Loading cciss.ko module
        cciss 0000:05:00.0: cciss:Trying to put board into performant mode
        cciss 0000:05:00.0:Placing controller into performant mode
         cciss/c0d0: p1 p2