Red Hat Bugzilla – Bug 621647
Exception occurs on install when multipath is enabled
Last modified: 2010-08-18 09:20:20 EDT
Description of problem: When installing RHEL6 beta 2, when choosing a disk to install the OS on, if there is more than one path to any disks, an exception will occur. This seems to be a multipath / anaconda error. Version-Release number of selected component (if applicable): inbox for RHEL6 beta 2 How reproducible: constant Steps to Reproduce: 1. configuration should include more than one path to a SAN array 2. Install OS, using any disk (multipath or not) 3. Use all defaults Actual results: See screenshots. "Could not commit to to disk /dev/mapper/mpathn" Expected results: Should have begun installation Additional info: This is an HP BL490c G6, connected to an EVA6400 multipathed through a Cisco and Brocade fabric. This was done using the Emulex NC553i, LPe1105, and LPe1205.
Created attachment 436922 [details] screenshot 2
Created attachment 436923 [details] screenshot 3
Created attachment 436924 [details] screenshot 1
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. **
The only information that looks helpful to be in in screenshot 2. It appears that device-mapper in unable to creat a linear device. This could be a kpartx partition on the multipath device. If this is the case, this bug might be another instance of 612173. However, without more of anaconda's logs, it's pretty hard to tell.
(In reply to comment #6) > The only information that looks helpful to be in in screenshot 2. It appears > that device-mapper in unable to creat a linear device. This could be a kpartx > partition on the multipath device. If this is the case, this bug might be > another instance of 612173. However, without more of anaconda's logs, it's > pretty hard to tell. I'll see about collecting as many logs as possible. Thanks!
Created attachment 439037 [details] Anaconda Log
I have all of the logs in /tmp, so let me know what else you need... I've recently tried snapshot 10 with the same config, and I'm getting a different error, sooner than this one. So I cannot verify if it works in snapshot 10 or not.
The first issue you were seeing about could not commit to disk has been fixed in more recent snapshots. The issue you are seeing in comment #10 has been fixed in anaconda-13.21.69-1. Duping this bug against the latter issue since that's the most recent snapshot you are trying. *** This bug has been marked as a duplicate of bug 575749 ***