kdump fails due to late recognition of disks

Issue

• Kdump fails when the 2nd kernel could not recognize the disk which vmcore should be saved in before fsck runs on the 2nd kernel.

• In my case, the disk is connected through Emulex lpfc but I don't know whether the same problem occurs or not when using other HBAs.

  <snip>
  Creating block device ram4
  Creating block device ram5
  Creating block device ram6
  Creating block device ram7
  Creating block device ram8
  Creating block device ram9
  Creating block device sda
  Creating block device srlpfc 0000:07:00.1: 1:1303 Link Up Event x1 received Data: x1 x1 x8 x2 x0 x0 0
  0
  lpfc 0000:07:00.1: 1:(0):0100 FLOGI failure Status:x3/x18 TMO:x0
  mdadm: No arrays found in config file or automatically
  Free memory/Total memory (free %): 75356 / 114520 ( 65.8016 )
  Saving to the local filesystem LABEL=/dump
  Usage: fsck.ext3 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
   [-I inode_buffer_blocks] [-P process_inode_size]
   [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
   [-E extended-options] device
  
  Emergency help:
   -p                   Automatic repair (no questions)
   -n                   Make no changes to the filesystem
   -y                   Assume "yes" to all questions
   -c                   Check for bad blocks and add them to the badblock list
   -f                   Force checking even if filesystem is marked clean
   -v                   Be verbose
   -b superblock        Use alternative superblock
   -B blocksize         Force blocksize when looking for superblock
   -j external_journal  Set location of the external journal
   -l bad_blocks_file   Add to badblocks list
   -L bad_blocks_file   Set badblocks list
  mount: can't find /mnt in /etc/fstab
  dropping to initramfs shell
  exiting this shell will reboot your system
  / #