To follow up on my own post: I have seen the same problem now on a number of other machines of this type with such a raid configuration, so unfortunately, it is not just a single machine with a broken configuration. I filed a bug report, https://bugzilla.redhat.com/show_bug.cgi?id=474399 David Jansen On Thu, Nov 27, 2008 at 12:46:26PM +0100, David Jansen wrote: > After a few succesful Fedora 10 installs, I tried to install my main > machine which has 3 harddisks, 1 SATA disk (sda) for the system and a > data partition, and 2 sata disks in RAID1, set through the bios (Intel > chipset, raid bios reports as Intel Matrix Storage Manager option ROM > v7.6.0.1011 ICH9R wRAID5) which in Fedora 8 was handled by device mapper: > $ df /home > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/mapper/isw_edcfaihjg_Volume0p1 > 473078128 106809904 341849428 24% /home > > However, when starting a fresh install of Fedora 10 (I wanted to keep > /home and /data, but reformat the other partitions), no RAID was seen; > anaconda just reports 3 SATA disks, sa, sdb and sdc, and sdb and sdc > both contain 1 ext3 partion, both labeled /home , according to anaconda. > > Is there some additional magic or boot option needed to enable > devicemapper during a reinstall? I couldn't find anything in the release > notes that could indicate that this behaviour has changed. > > David Jansen > > PS: in case it helps, architecture is x86_64; system is a HP xw4600, cpu > reports as Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
