From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NyCuU-0001PW-AH for garchives@archives.gentoo.org; Sat, 03 Apr 2010 23:37:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E7BE2E09B3; Sat, 3 Apr 2010 23:37:23 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id ADE71E09B3 for ; Sat, 3 Apr 2010 23:37:23 +0000 (UTC) Received: from digimed.co.uk (grunthos.digimed.co.uk [192.168.1.4]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id B399860DEBC for ; Sun, 4 Apr 2010 00:37:22 +0100 (BST) Date: Sun, 4 Apr 2010 00:37:10 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How does grub assemble a RAID1 for / ?? Message-ID: <20100404003710.3e1ae97c@digimed.co.uk> In-Reply-To: References: Organization: Digital Media Production X-Mailer: Claws Mail 3.7.5cvs43 (GTK+ 2.18.9; i686-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/hxPvsF57afD/Bdc/Dez7RYC"; protocol="application/pgp-signature" X-Archives-Salt: 5275d062-7190-4de0-b5b1-1f0b1cf2fa80 X-Archives-Hash: 5fed7b292a095f0936029e7dc850d984 --Sig_/hxPvsF57afD/Bdc/Dez7RYC Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 3 Apr 2010 16:07:06 -0700, Mark Knecht wrote: > The install is complete but it won't boot. grub finds the kernel > and starts booting but then I get the typical VFS file sync error as > the kernel starts looking for the install on /dev/md3. What I'm not > understanding is how does the boot process get the information > required to assemble the RAID device. By hand in the non-RAID install > I do this: >=20 > keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3 > mdadm: /dev/md3 has been started with 2 drives. > keeper ~ # cat /proc/mdstat > Personalities : [raid1] > md3 : active raid1 sdb3[0] sdc3[1] > 52436092 blocks super 1.1 [2/2] [UU] >=20 > unused devices: > keeper ~ # >=20 > but when I try to boot the RAID install it says it cannot find /dev/md3. You need to set the partition type for the RAIDed partitions to "Linux raid autodetect". You'll probably then find that the kernel sets the RAID as /dev/md0, not md3. --=20 Neil Bothwick "You want us to do WHAT?" - Ancient Chinese wall engineer. --Sig_/hxPvsF57afD/Bdc/Dez7RYC Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAku30TEACgkQum4al0N1GQN3wACggFKpaAIWrPezeNPgdR2wIJaw z3cAn0+VI607vxJdhV5gSWUqIv74YNi6 =8Uot -----END PGP SIGNATURE----- --Sig_/hxPvsF57afD/Bdc/Dez7RYC--