Bug 1317786

Summary: unable to start the newly installed f24 system on vm after add a storage device
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: dracutAssignee: dracut-maint-list
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: dracut-maint-list, harald, jonathan, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-18 12:31:25 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:
Attachments:
Description Flags
dracut
none
screenshot
none
journalctl none

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