Bug 108987
Summary: | "Exception Occured" in Disk Druid stage of Anaconda | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Torrey Hoffman <thoffman> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-04-16 21:55:46 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: |
Description
Torrey Hoffman
2003-11-04 01:37:31 UTC
What were the software raid devices preconfigured on the system? Hello. Here's a more detailed explanation: From the first installation of Fedora Core on this machine (before I added the second two disks), I had a RAID 0 configured as /dev/md0. This was on two 36 GB SATA disks. Each of the two SATA disks had a swap partition and a regular partition in addition to the raid partition. Then I added the two more disks. These were PATA disks, transferred from my old computer. They each had a single partition, and on the old computer they were also configured as /dev/md0. So, when I started to reinstall Fedora Core on the resulting system, it autodetected the two previous RAID0 collections. However, it seemed to get confused, since obviously there were four partitions involved, and they couldn't all be from the same RAID0... I worked around the problem by doing a Ctrl-Alt-F1 from the installer to get to a command prompt, and then wiped the partition tables on the SATA disks using: "dd if=/dev/zero of=/dev/sda bs=512 count=1" "dd if=/dev/zero of=/dev/sdb bs=512 count=1" Then I rebooted and restarted the install... it worked fine that time around since there was only the one pre-existing RAID setup to find. My suggestion would be: - Have anaconda detect invalid RAID (or LVM?) configurations before entering the disk druid installer - If something strange shows up in the existing partition tables, give the user an option to ignore or wipe out existing partitions, on a drive-by-drive basis... Hope that helps? Okay, matches what I was guessing. Fixed in CVS |