Description of problem: The installer reports the SATA SSD device I'm going to install do is at /dev/mapper/mpathc rather than /dev/sda. This could be a device-mapper or kernel bug, not sure, but it manifests so far only in the Live environment when doing an OS install, not in the installed environment. Version-Release number of selected component (if applicable): python-blivet-0.59-1.fc21.noarch device-mapper-1.02.86-1.fc21.x86_64 anaconda-21.45-1.fc21.x86_64 How reproducible: Non-deterministic, but happens often. Steps to Reproduce: 1. Launch anaconda and go through an installation. 2. 3. Actual results: In various parts of the UI, the installer refers to the target device as mpathc. Expected results: Target device should be sda. Additional info:
Created attachment 913585 [details] dmesg OK at 17 seconds monotonic time a preexisting sda6 swap partition is referred to by systemd as /dev/mapper/mapthc6. So this bug is set to the wrong component. No idea if it's a systemd, systemd-udev, or device-mapper bug.
Created attachment 913586 [details] journalctl -l -b -o short-monotonic
Created attachment 913587 [details] anaconda storage.log
[ 13.000642] rawhide.localdomain multipathd[789]: sda: add path (uevent) [ 13.001228] rawhide.localdomain multipathd[789]: sda: spurious uevent, path already in pathvec [ 13.048938] rawhide.localdomain kernel: device-mapper: multipath service-time: version 0.2.0 loaded [ 13.013270] rawhide.localdomain multipathd[789]: mpathc: load table [0 500118192 multipath 0 0 1 1 service-time 0 1 1 8:0 1] [ 13.013779] rawhide.localdomain multipathd[789]: mpathc: event checker started [ 13.014108] rawhide.localdomain multipathd[789]: sda [8:0]: path added to devmap mpathc would seem to indicate multipathd.
Yeah if I find the wwid with multipath -v2 and blacklist it in multipath.conf I don't run into this, the SSD appears in anaconda normally as expected. Also sometimes causes anaconda to bogusly claim no disks are found: see dup bug 1114783 for that manifestation.
*** Bug 1114783 has been marked as a duplicate of this bug. ***
I haven't experienced this in over a month, but don't know if that means something was found and fixed, or if the problem's just become much more rare.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.