Description of problem: Currently several customers fail on kdump local test due to `vmcore not found` issue, however the vmcores did saved. After investigation, we have the following: there are several disks attched, but the disk driver load sequence is different in first kernel and kdump kernel. So /dev/sda1 in first kernel might be /dev/sdb1 in second kernel. Then in kdump kernel, system tries to mount a incorrect partition, which is likely to cause error. Thus, we need to use UUID or LABEL to avoid such loading sequence mismatch issue. Version-Release number of selected component (if applicable): 1.5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0222.html