Bug 781876

Summary:	Install to Hard drive from LiveCD fails
Product:	[Fedora] Fedora	Reporter:	Dave Knight <dmk>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-19 00:53:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Knight 2012-01-15 21:39:37 UTC

Description of problem:

Apparently install process has difficulty with hardware RAID1 mirror boot set consisting of uninitialized (no partitions, etc) disks that have been configured as a RAID1 mirror by the raid card BIOS.  The same raid card worked fine with FC10... 


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

anaconda as distributed with FC16 liveCD


How reproducible:
After FC16 LiveCD boots up (GNOME3 loads OK), choose "Install to Hard Drive".  Runs for qa bit then displays error - described in saved abrt.log file below


Steps to Reproduce:
1. boot LiveCD from USB stick (4GB)
2. click on Install to Hard drive icon
3. wait 
  
Actual results:
install fails

Expected results:
install succeeds (as on another machine with a different (cheaper/newer) raid card.


Additional info:  here is the saved "abrt.log" content:

[liveuser@localhost tmp]$ cat abrt.log
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-7.fc16.i686
product:        Fedora
reason:         DeviceTreeError: MD RAID device md127 not in devicetree after scanning all slaves
time:           Sun Jan 15 16:11:49 2012
version:        16

description:
:The following was filed automatically by anaconda:
:anaconda 16.25 exception report
:Traceback (most recent call first):
:  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 753, in addUdevMDDevice
:    "scanning all slaves" % name)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 999, in addUdevDevice
:    device = self.addUdevMDDevice(info)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1866, in _populate
:    self.addUdevDevice(dev)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1823, in populate
:    self._populate(progressWindow)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 476, in reset
:    cleanupOnly=cleanupOnly)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 104, in storageInitialize
:    storage.reset()
:  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward
:    self.dispatch()
:  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked
:    self.anaconda.dispatch.go_forward()
:DeviceTreeError: MD RAID device md127 not in devicetree after scanning all slaves

END:

[liveuser@localhost tmp]$

Comment 1 Brian Lane 2012-01-16 15:12:36 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 Dave Knight 2012-01-16 16:34:38 UTC

This problem seems to have been caused by the incomplete creation of the RAID1 mirror array.  Specifically, new disks were installed and a RAID1 mirror established, but the "build" process (which takes a very long time with the RAID controller I am using) had not been completed at the time of this install.

Subsequently, I re-did the RAID1 configuration and build, and the FC16 install was successful.

Perhaps the "bug" is that anaconda was not able to recognize the invalid RAID1  set, or was not able to emit an error indicative of the problem - or I wsa unable to interpret the errors emitted to infer the nature of the problem.

Bottom line, I'd say this was mostly "pilot error".

Comment 3 Chris Lumens 2012-01-17 15:11:04 UTC

Well, we still shouldn't traceback.  Can you provide the info from comment #1, or is it gone for good?

Comment 4 Dave Knight 2012-01-17 18:01:13 UTC

Agreed.  Unfortunately, the /tmp/*.log files are long gone, unless /tmp lives, or is preserved, somewhere on the LiveCD install USB stick (suggestion?).

Comment 5 Brian Lane 2012-01-19 00:53:29 UTC

No, /tmp isn't preserved. If you ever hit this again please reopen.