Hide Forgot
The following was filed automatically by anaconda: anaconda 14.22 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/mdraid.py", line 202, in mddeactivate raise MDRaidError("mddeactivate failed for %s: %s" % (device, msg)) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2876, in teardown mdraid.mddeactivate(self.path) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1301, in findExistingRootDevices device.teardown() File "/usr/lib64/python2.7/site-packages/pyanaconda/upgrade.py", line 110, in findExistingRoots return findExistingRootDevices(anaconda, upgradeany=upgradeany) File "/usr/lib64/python2.7/site-packages/pyanaconda/upgrade.py", line 81, in findRootParts flags.cmdline.has_key("upgradeany")) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 212, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 131, in gotoNext self.moveStep() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1278, in setScreen self.anaconda.dispatch.gotoNext() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1191, in nextClicked self.setScreen () MDRaidError: mddeactivate failed for /dev/md3: mdadm: failed to stop array /dev/md3: Device or resource busy Perhaps a running process, mounted filesystem or active volume group?
Created attachment 494456 [details] Attached traceback automatically from anaconda.
Can you provide some more detail about the system? It looks like you were trying to upgrade. There are also a number of ldconfig errors in the logs, but I am not sure if they are related.
OK. The system is based upon a Dual-Core 64-bit Intel Atom chipset and has five 250GB SATA notebook hard drives with a Promise TX SATA PCI controller in the one PCI slot in the motherboard. Each drive was identically partitioned with a small slice at the beginning and "the rest". On drives sda1 and sdb1 the root/boot partition was mirrored as /dev/md3. On drives sdd1 and sde1 there is a RAID0 making a larger /tmp as /dev/md1. Swap is directly on sdc1. The remaining large partition on each drive was combined into a RAID5 array as /dev/md2 which was a single large LVM2 volume. I tried to upgrade from Fedora 12 to Fedora 14. Anaconda really didn't understand the disc layout at all and bombed out in many different ways. The various bug reports I filed were the various failures as I used the ALT-F2 console to re-mount the various partitions/slices in the hope that it would aid anaconda in performing the upgrade. Ultimately all my efforts were failures and I installed a fresh Fedora 14 onto a new manually created /dev/md0 (on /dev/sda1 and /dev/sdb1) and then progressively relocated the other partitions onto the LVM area and other md devices. Probably the best fix for anaconda might be some way in which you could let it proceed with the package update efforts without messing with the disc layout. It works, it's valid, but it is pretty complex. Regards, Bevis.
I think the ldconfig errors are all related to some zero-size files in the Oracle 11g installation on this system. They've been there for a while and persist after the fresh install of Fedora 14. Regards, Bevis.
So you went to the shell and manually activated your md and lvm and then returned to the installer? This is not supported. If you want to attach logs from a run in which you let the installer discover the devices without your intervention I can take a look at them to see what may be going on. Are you aware that Fedora 15 will be out soon? A beta is already available.
I'm pretty sure one of the earliest bugs submitted is exactly that scenario. Basically I tried the simple method first and anaconda blew up big time.
Ok, we're going to close the others and work on the one that's a supported attempt.