Bug 1729329 - can only install to spin disc
Summary: can only install to spin disc
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 30
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-11 23:45 UTC by Bob Siegfried
Modified: 2019-07-11 23:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
screenshot of early portion of install (Plymouth?) (5.60 MB, image/jpeg)
2019-07-11 23:45 UTC, Bob Siegfried
no flags Details

Description Bob Siegfried 2019-07-11 23:45:34 UTC
Created attachment 1589702 [details]
screenshot of early portion of install (Plymouth?)

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
[ OK ] Started Show Plymouth Boot Screen.

. . .

[ OK ] Started Monitoring of LVM2ë dmeventd or progress polling.

[Failed] Failed to start LVM2 PV scan on device 8:18.

See 'systemctl status lvm2-pvscan@8:18.service' for details.

[Failed] Failed to start LVM2 PV on device 259:3.

See 'systemctl status lvm2-pvscan@259:3.service' for details.

[Failed] Failed to start LVM2 PV on device 259:2.

See 'systemctl status lvm2-pvscan@259:2.service' for details.

[Failed] Failed to start LVM2 PV on device 8:3.

See 'systemctl status lvm2-pvscan@8:3.service' for details.

[ OK ] Started udev Wait for Complete Device Initialization.

[ OK ] from here on

This system previously ran Fedora 30. I swapped out 2 spin drives for a new spin drive and an SSD because one of the old drives developed a bad sector. A pair of M.2's are also in the system. All four old components were previously operating under Fedora 30. The only way I can get the system to install and boot now is to install only on the spin drive, leaving the M.2's and the SSD unutilized.

The only other info that seems relevant is that the new spin drive constantly get set up as sda, and the SSD as sdb each time I attempt an install trying to use both drives. I have tried installs with all possible combinations of storage components. 
2.
3.

Actual results: Can only install to new spin drive, and must select for each boot


Expected results: Successful installation


Additional info: Is this an Anaconda storage device detection issue?


Note You need to log in before you can comment on or make changes to this bug.