Bug 1225618

Summary: Cannot install Fedora 22 (&23-Beta) - does not find /dev/mapper disk partition.
Product: [Fedora] Fedora Reporter: rh001 <rh001>
Component: libblockdevAssignee: Vratislav Podzimek <vpodzime>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: anaconda-maint-list, blivet-maint-list, g.kaviyarasu, jonathan, pomec, rh001, sbueno, sgallagh, stickster, vanmeeuwen+fedora, vpodzime
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:17:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
storage log file
none
program log file none

Description rh001 2015-05-27 19:31:31 UTC
Description of problem:
Cannot install Fedora 22

Version-Release number of selected component (if applicable):
Fedora 22

How reproducible:
All the time

Steps to Reproduce:
1. Boot from Fedora 22 install CD
2. Run Install to hard-drive
3. When install gets to select disk - nothing shows up.

Actual results:
no disks

Expected results:
to be able to find /dev/mapper/pdc_cafbcjfbc


Additional info:
I can open a shell and mount all of the partitions and see all the files.
The commands:
  mount /dev/mapper/pdc_bcjfbc5 /mnt/sysimage
  mount /dev/mapper/pdc_bcjfbc1 /mnt/sysimage/boot
work fine.
When I run installer after mounting, Fedora still cannot find any disks.

Comment 1 Greg Ennis 2015-06-13 04:16:23 UTC
Same thing has happened to me.  I am trying to put together a dual boot Windows and Fedora 22 system.  When I get to the selecting the disk there is no disk to select.  I am using a Dell Optiplex 780 with Windows 7.1

Comment 2 Greg Ennis 2015-06-13 13:14:42 UTC
I used the netinstall 64 disc for fedora 22 and was able to proceed with my installation.  The netinstall disc recognized the hard drives without a problem.

Comment 3 David Shea 2015-06-17 21:44:09 UTC
Please attach the log files from /tmp as individual, text/plain attachments.

Comment 4 rh001 2015-06-18 19:45:21 UTC
Created attachment 1040634 [details]
anaconda.log

Comment 5 rh001 2015-06-18 20:30:14 UTC
I assume you wanted the anaconda log file.

Comment 6 David Shea 2015-06-18 20:32:47 UTC
And storage.log, and program.log.

Comment 7 rh001 2015-06-21 12:57:24 UTC
Created attachment 1041411 [details]
storage log file

Comment 8 rh001 2015-06-21 12:58:50 UTC
Created attachment 1041412 [details]
program log file

Additional log files attached.

Comment 9 rh001 2015-09-10 19:56:14 UTC
Any update?  Fixed in Fedora 23?

Comment 10 rh001 2015-10-29 20:27:27 UTC
Downloaded and tried to install XFCE Fedora release 23-Beta and still does not find disks, and install throws a lot of "unknown errors".
Can someone bump this priority to urgent?
No issues installing latest (or even previous) release of ubuntu.

Comment 11 David Lehman 2015-11-04 19:19:52 UTC
sda and sdb are members of the (active) promise fasttrack array pdc_cafbcjfbc, but libblockdev is unable to identify the array based on its members:

18:17:57,499 INFO blivet: got format: existing dmraidmember
18:17:57,500 DEBUG blivet:       DeviceTree.handleUdevDMRaidMemberFormat: type: dmraidmember ; name: sdb ;
18:17:57,677 WARN blivet: dmraid member sdb does not appear to belong to any array

Comment 12 Fedora End Of Life 2016-07-19 14:17:49 UTC
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.