Am Mittwoch 13 Januar 2010 schrieb Alexander Duscheleit: > On Wed, 13 Jan 2010 10:05:04 -0500 > > Carlos Williams <carloswill@xxxxxxxxx> wrote: > > On Tue, Jan 12, 2010 at 7:56 PM, Alexander Duscheleit > > > > <jinks@xxxxxxxxxxxx> wrote: > > > I didn't know, where to put a proper reply in this thread, because > > > basically you are all doing the same mistake. I will just outline > > > the procedure here briefly and then explain where it all went > > > wrong :) > > > > > > 1 - cfdisk # the settings in Carlos' 1st mail look sane > > > 2 - modprobe raid1 > > > 3 - mdadm --create /dev/md0 --level=1 > > > --raid-devices=2 /dev/sda2 /dev/sdb2 4 - /arch/setup # we save the > > > mdadm -D --scan for later !!!! 5 - before getting to the "Configure > > > System" part, open up another console (Alt-F2) and do > > > mdadm -D --scan >> /mnt/etc/mdadm.conf > > > (you have to do this before mkinitcpio runs > > > in the "Configure" stage, but after the target > > > system is mounted, so between "Install Packages" > > > and "Configure System" should be fine) > > > 6 - continue the setup as described in OP (skip the cp -a part) > > > > Alexander, > > > > All I can say is THANK YOU! Seriously solved one of the most > > frustrating things for me. > > [...] > > Glad, I could help :) > > I still think /arch/setup *should* generate this file itself if it > detects software raids in use for the target. The wiki even seems to > suggest, that it does. > > Could some releng shine light on this, please? > > Greetings, > jinks > As alternative you could use archboot iso. It will create such file and autoconfiguration of initcpio. Iso files are located here: ftp.archlinux.org/iso/archboot/ greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@xxxxxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
