Bug 751481

Summary: Software RAID won't boot
Product: [Fedora] Fedora Reporter: Andrew Gillis <andrew>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
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: 2011-11-07 22:28:59 UTC Type: ---
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
ifcfg.log
none
storage.log
none
program.log
none
X.log
none
yum.log
none
anaconda.log
none
ifcfg.log
none
program.log
none
storage.log
none
syslog
none
X.log
none
yum.log none

Description Andrew Gillis 2011-11-04 20:47:40 UTC 
Fedora installed on Software RAID dosn't boot

Install Fedora 16 using the graphical install. I used the GUI tools to create a RAID 1 partition on two drives as stated in the documentation. Fedora installed with no errors but when I rebooted the system I only get a grub error "error: no such device: <GUID>"

I booted into rescue mode and ran grub2-install /dev/sda. This completed successfully but the system still won't boot.

I created a kickstart file the installs to software RAID. Same error.



How reproducible:

Install Fedora 16 to Software RAID.
Comment 1 Brian Lane 2011-11-05 00:20:16 UTC 
Please switch to tty2 (ctrl-alt-f2) and attach the logs from /tmp/*log to this bug as individual plain/text files.
Comment 2 Andrew Gillis 2011-11-07 14:56:07 UTC 
Created attachment 532061 [details]
anaconda.log
Comment 3 Andrew Gillis 2011-11-07 14:56:27 UTC 
Created attachment 532062 [details]
ifcfg.log
Comment 4 Andrew Gillis 2011-11-07 14:57:15 UTC 
Created attachment 532063 [details]
storage.log
Comment 5 Andrew Gillis 2011-11-07 14:57:38 UTC 
Created attachment 532064 [details]
program.log
Comment 6 Andrew Gillis 2011-11-07 14:57:52 UTC 
Created attachment 532065 [details]
X.log
Comment 7 Andrew Gillis 2011-11-07 14:58:06 UTC 
Created attachment 532066 [details]
yum.log
Comment 8 Brian Lane 2011-11-07 17:48:55 UTC 
It looks like the install never finished. the last anaconda.log entry is tasksel and program log doesn't show it running grub.
Comment 9 Andrew Gillis 2011-11-07 18:07:22 UTC 
Created attachment 532105 [details]
anaconda.log
Comment 10 Andrew Gillis 2011-11-07 18:07:48 UTC 
Created attachment 532106 [details]
ifcfg.log
Comment 11 Andrew Gillis 2011-11-07 18:08:10 UTC 
Created attachment 532108 [details]
program.log
Comment 12 Andrew Gillis 2011-11-07 18:08:30 UTC 
Created attachment 532109 [details]
storage.log
Comment 13 Andrew Gillis 2011-11-07 18:08:53 UTC 
Created attachment 532110 [details]
syslog
Comment 14 Andrew Gillis 2011-11-07 18:09:15 UTC 
Created attachment 532111 [details]
X.log
Comment 15 Andrew Gillis 2011-11-07 18:09:40 UTC 
Created attachment 532112 [details]
yum.log
Comment 16 Andrew Gillis 2011-11-07 18:10:24 UTC 
Sorry, I didn't know I need to let it finish. I let it finish this time and attached all new logs.
Comment 17 Brian Lane 2011-11-07 22:28:59 UTC 

*** This bug has been marked as a duplicate of bug 750794 ***
Comment 18 Brian Lane 2011-11-07 22:29:26 UTC 
Give the workaround in bug 750794 a try.
Comment 19 Andrew Gillis 2011-11-07 23:35:20 UTC 
The workaround in bug 750794 does not resolve the problem. I still get  "error:
no such device: <GUID>" when I boot the system.