On Mon, 2005-12-19 at 23:16 +0300, Paul P Komkoff Jr wrote: > Hello. > > Last N systems I've installed, I am usually assembling software raid1 > at install time. The disk layout I'm using is trivial: 100MB + > the rest, where on 1st 100MB is /dev/md0 (ext3, /boot) and the rest is > /dev/md1 (lvm, other). > > For whatever reason (haven't looked at the code yet :() anaconda > issuing mdadm commands in such order that primary replica of unsynched > md0 is second drive, and raid1 resync started first on md1. > > So, to boot without changing bios settings back and forth (or without > disabling 1st disk drive by any other means) it is nesessary to wait > while md1 raid1 resyncs, which can be as long as 2 hours (250GB HDD). I'm pretty sure that anaconda at some point deliberately did things to avoid that sync. So I suspect it got reenabled for a good reason... -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
