Red Hat Bugzilla – Bug 816823
traceback when /boot is on md on EFI
Last modified: 2012-05-16 07:51:49 EDT
libreport version: 2.0.10
cmdline: /usr/bin/python /usr/sbin/anaconda
other involved packages:
release: Cannot get release name.
time: Fri 27 Apr 2012 01:03:43 AM CDT
anaconda-tb-p_F0Nd: Binary file, 1578890 bytes
:The following was filed automatically by anaconda:
:anaconda 17.20 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1132, in grub_device_name
: name = "(hd%d" % self.drives.index(drive)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1491, in grub_conf_device_line
: return "device %s %s\n" % (self.grub_device_name(self.stage2_device),
: File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1258, in write_config_header
: File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1037, in write_config
: File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1374, in write_config
: super(GRUB, self).write_config()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1558, in write
: File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2346, in writeBootloader
: File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 383, in dispatch
: self.dir = self.steps[self.step].target(self.anaconda)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 247, in go_forward
: File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked
: File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
: File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1221, in handleRenderCallback
:ValueError: MDRaidArrayDevice instance (0x7f2d2cba9ed0) --
: name = md0 status = True kids = 0 id = 126
: parents = ['existing 368MB partition sda2 (115) with non-existent mdmember',
: 'existing 368MB partition sdb2 (111) with non-existent mdmember']
: uuid = eb1d1595:a14545aa:42f30dc8:1a7f8301 size = 367.98828125
: format = existing ext4 filesystem mounted at /boot
: major = 0 minor = 0 exists = True protected = False
: sysfs path = /devices/virtual/block/md0 partedDevice = parted.Device instance --
: model: Linux Software RAID Array path: /dev/md0 type: 17
: sectorSize: 512 physicalSectorSize: 512
: length: 753640 openCount: 0 readOnly: False
: externalMode: False dirty: False bootDirty: False
: host: 13107 did: 13107 busy: True
: hardwareGeometry: (94205, 2, 4) biosGeometry: (46, 255, 63)
: PedDevice: <_ped.Device object at 0x7f2d2c31d560>
: target size = 0 path = /dev/md0
: format args = None originalFormat = ext4 level = 1 spares = 0
: members = 2
: total devices = 2 metadata version = 1.0 is not in list
Created attachment 580640 [details]
Straightforward installation of F17 on a new Thinkpad T420, using LVM on crypto on MD.
Digging a little further, it looks like this exception occurs whenever /boot is on an MD device in EFI mode. In this case I was trying to install with /boot on /dev/md0. Is there some reason this shouldn't work?
I think it would occur regardless of whether LVM/crypto were in use for the rest of the system.
This is totally untested, so we're probably going to just disable /boot on md on EFI for F17 since it's too late to be trying to test/fix it.
anaconda-17.27-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-17.27-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-17.27-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.