Bug 1317786 - unable to start the newly installed f24 system on vm after add a storage device
Summary: unable to start the newly installed f24 system on vm after add a storage device
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 08:35 UTC by lnie
Modified: 2016-03-18 12:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-18 12:31:25 UTC
Type: Bug

Attachments (Terms of Use)
dracut (57.06 KB, image/png)
2016-03-15 08:35 UTC, lnie 		no flags Details
screenshot (72.24 KB, image/png)
2016-03-15 08:36 UTC, lnie 		no flags Details
journalctl (65.92 KB, text/x-vhdl)
2016-03-16 04:34 UTC, lnie 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description lnie 2016-03-15 08:35:30 UTC 
Created attachment 1136421 [details]
dracut

Description of problem:
 

Version-Release number of selected component (if applicable):
 f24-Alpha1.1-workstation-x86_64

How reproducible:
always

Steps to Reproduce:
1.Do a default install with f24 
2.add an existing storage as is shown in the screenshot
3.reboot the system

Actual results:


Expected results:
the system starts successfully as it dose in f23

Additional info:
Comment 1 lnie 2016-03-15 08:36:01 UTC 
Created attachment 1136422 [details]
screenshot
Comment 2 Zbigniew Jędrzejewski-Szmek 2016-03-15 11:24:01 UTC 
Please provide the boot logs or some details of what goes wrong.
Comment 3 lnie 2016-03-16 04:34:49 UTC 
Created attachment 1136841 [details]
journalctl
Comment 4 lnie 2016-03-16 04:53:06 UTC 
The log from journalctl -b has been uploaded.Please let me know if there is any other information needed. 
FYI:The log complaints "Multiple VGs found with the same name",and it is not seen in the log from f23.The dirty existing storage has a f24 system installed before it is added to the unlucky VM.
Comment 5 Harald Hoyer 2016-03-18 12:30:30 UTC 
Mar 16 04:18:14 localhost dracut-initqueue[404]: Multiple VGs found with the same name: skipping fedora

seems like you have multiple volume groups with the same name on your disks. therefore lvm vgscan -ay does not activate those.
Comment 6 Harald Hoyer 2016-03-18 12:31:25 UTC 
there is nothing dracut can do. make your volume group names unique
Note You need to log in before you can comment on or make changes to this bug.