From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1PQ1EU-00072G-Vt for mharc-grub-devel@gnu.org; Tue, 07 Dec 2010 12:21:43 -0500 Received: from [140.186.70.92] (port=43203 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQ1ES-00070g-3u for grub-devel@gnu.org; Tue, 07 Dec 2010 12:21:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PQ1EN-0005W6-Ju for grub-devel@gnu.org; Tue, 07 Dec 2010 12:21:40 -0500 Received: from mail-bw0-f43.google.com ([209.85.214.43]:51795) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PQ1EN-0005UX-9F for grub-devel@gnu.org; Tue, 07 Dec 2010 12:21:35 -0500 Received: by bwz14 with SMTP id 14so262902bwz.30 for ; Tue, 07 Dec 2010 09:21:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type; bh=4cy7zLVUxvKhj8XQ+w23uWpPstLYcInuy7PF/QDcgG4=; b=pwycRsMtQLbTykIqiUOCMwQ1WM0xz/42xbXNBWY5XQbzS8+4o/ZkgTyWw1wGf9AOoG YlHZkyrLKsQCPtBFTfr1CDwG+zl8ubQMlsixfUoJF352vbDIN6J9S8Vs7Rj9KM6wR1uD JpGUums2G/nSClgvBIkbnM/RO8u6QYaSfnqYE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type; b=qZfzX4ZcWkOvo+5MoOnes3/LyJPH3xMxkVzsUiP82SW6k5zQ9mqzJCz+5osDXmI16s JHcnF3UIlrK1BxSOC38htNnfqcldwCIaqKRVFHDAEXg1CXakMtqtkyi1+aRU/PeL+Vza YNcaurwy95iEadPJhYchhhIjqO6podqvADApw= Received: by 10.204.118.4 with SMTP id t4mr718555bkq.38.1291742493103; Tue, 07 Dec 2010 09:21:33 -0800 (PST) Received: from debian.bg45.phnet (gprs59.swisscom-mobile.ch [193.247.250.59]) by mx.google.com with ESMTPS id a4sm2453652bka.19.2010.12.07.09.21.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 07 Dec 2010 09:21:31 -0800 (PST) Message-ID: <4CFE6D16.4060105@gmail.com> Date: Tue, 07 Dec 2010 18:21:26 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101030 Icedove/3.0.10 MIME-Version: 1.0 To: grub-devel@gnu.org References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigF2648673E5F19F63F5A79387" X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: Software RAID and Fakeraid X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2010 17:21:41 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF2648673E5F19F63F5A79387 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12/04/2010 05:34 AM, Leslie Rhorer wrote: > > =20 >> -----Original Message----- >> From: linux-raid-owner@vger.kernel.org [mailto:linux-raid- >> owner@vger.kernel.org] On Behalf Of Neil Brown >> Sent: Tuesday, November 30, 2010 4:25 PM >> To: Phillip Susi >> Cc: The development of GNU GRUB; John Sheu; linux-raid@vger.kernel.org= >> Subject: Re: Software RAID and Fakeraid >> >> On Tue, 30 Nov 2010 14:54:40 -0500 Phillip Susi wro= te: >> >> =20 >>> On 11/25/2010 5:26 AM, John Sheu wrote: >>> =20 >>>> What's the preferred way to differentiate BIOS fakeraid from regular= >>>> software mdraid? >>>> =20 >>> The only way I know of is detecting that it is a dmraid device as >>> opposed to md, which is why grub does it that way. This worked well = in >>> the past when each tool exclusively handled one type of raid. >>> >>> =20 >>>> I ask this as I'm booting with GRUB2 off a system that has one of >>>> =20 >> those >> =20 >>>> Intel fakeraid chipsets. As of a few months ago, the mdadm package >>>> =20 >> has >> =20 >>>> supported these fakeraid setups, so the RAID array comes up as a >>>> =20 >> /dev/md### >> =20 >>>> device. This is unfortunate, as GRUB2 assumes that any device of th= e >>>> =20 >> type >> =20 >>>> /dev/md### must be a pure software RAID device, and in >>>> util/grub-setup.c:939, tries to install itself to the RAID members >>>> individually: >>>> =20 >>> For grub to support fakeraids activated by the md driver, it needs so= me >>> way to find out that it is actually a fake raid, and not a software >>> raid. Adding linux-raid to Cc list to see if they can suggest a way = of >>> doing that. >>> =20 >> My feeling is that grub just needs to be a bit more careful. >> >> If the members of the md array are partitions, then installing itself = in >> the >> boot blocks of the devices holding those partitions always makes sense= =2E >> >> If the members of the md array are whole devices, then installing grub= in >> those devices might make sense depending on specific details of the >> metadata. The default should be that it doesn't make sense, but speci= fic >> cases do. >> e.g. if the metadata (/sys/block/mdX/md/metadata_version) is 0.90 or 1= =2E0, >> and >> the array is RAID1, then grub should install itself in the *array*, no= t in >> the devices. >> If the metadata is 1.1, then grub cannot install itself >> If the metadata is 1.2, then grub can install itself at the start >> If the metadata is external:imsm then (I think) grub should install it= self >> in >> the array ... though there are some complexities there. >> >> I often wonder why people who add knowledge of md to grub etc don't at= >> least >> let me know what they are doing in case I can see something obviously >> wrong >> with their approach.. >> =20 > I wonder why GRUB2 only supports 0.90 version superblocks on arrays > from which it can boot. I wonder even more why they seem to keep it a = deep, > dark secret. I tore my hair out for days trying to figure out why my > upgraded Linux box would not boot. Under legacy GRUB, it took some > fiddling, but 1.x RAID1 arrays were bootable. > > > =20 1.x metadata was added this summer. Please upgrade > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel > > =20 --=20 Regards Vladimir '=CF=86-coder/phcoder' Serbinenko --------------enigF2648673E5F19F63F5A79387 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREKAAYFAkz+bRYACgkQNak7dOguQgkG5QD+LXKIVIWHR2JpNNIi2USkmdb4 5YijT2ece5S4E4uuNLQA/RjV8m0FpJj7mDAxSsfyBEN5yIkvRigRVlVrzOODxNVh =OjoD -----END PGP SIGNATURE----- --------------enigF2648673E5F19F63F5A79387--