From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1PWaDc-0005yE-IQ for mharc-grub-devel@gnu.org; Sat, 25 Dec 2010 14:55:56 -0500 Received: from [140.186.70.92] (port=38932 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PWaDY-0005xN-Qs for grub-devel@gnu.org; Sat, 25 Dec 2010 14:55:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PWaDX-0000Gc-Pn for grub-devel@gnu.org; Sat, 25 Dec 2010 14:55:52 -0500 Received: from mail-wy0-f169.google.com ([74.125.82.169]:44428) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PWaDX-0000GN-LF for grub-devel@gnu.org; Sat, 25 Dec 2010 14:55:51 -0500 Received: by wyj26 with SMTP id 26so7923262wyj.0 for ; Sat, 25 Dec 2010 11:55:50 -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=YjQ0ftVDCaY25cVJWChVDkYmzWGd7wmYRGKgOowMLVI=; b=E6TL38EDCnPXxO5C5NVej1GDr7jgFbw97Hhj8rniUIsSdaEXc7oChTGdMvsyzLVTPA ftfzzJllMmxYrAyv4AM7pBcdZy8tVGL2m8RZzpmn0q1/v6Y1GNFjG3fjecGFuBdj/Pf2 pkQiFkM9jTjuJP3qXwPsXX+zoWTGVKNUwFqJ8= 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=Z1fQJQu2kgtz+dm3kdxGG+rNc4/XhM/72IEslMqCy0wZZR8vbE6I5nONaRqD1RYmM/ xjSC3KFpRrWGNHfgHr0MDN4KvcMBXWw2fujQ/Lr9nDEHmPvmeNTT6gJPQzWElkt67uxN OIFtId/R2t+CGNtfgleRGL3+wogUzCxd8tHEU= Received: by 10.216.44.208 with SMTP id n58mr15849051web.39.1293306949390; Sat, 25 Dec 2010 11:55:49 -0800 (PST) Received: from debian.bg45.phnet (12-131.62-81.cust.bluewin.ch [81.62.131.12]) by mx.google.com with ESMTPS id o19sm5012858wee.2.2010.12.25.11.55.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 25 Dec 2010 11:55:47 -0800 (PST) Message-ID: <4D164C3E.9020509@gmail.com> Date: Sat, 25 Dec 2010 20:55:42 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101211 Icedove/3.0.11 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="------------enigDC76EA97AAF7B52171D06026" 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: Sat, 25 Dec 2010 19:55:53 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDC76EA97AAF7B52171D06026 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 11/25/2010 11:26 AM, John Sheu wrote: > What's the preferred way to differentiate BIOS fakeraid from regular > software mdraid? > > I ask this as I'm booting with GRUB2 off a system that has one of > those Intel fakeraid chipsets. As of a few months ago, the mdadm > package has supported these fakeraid setups, so the RAID array comes > up as a /dev/md### device. This is unfortunate, as GRUB2 assumes that > any device of the type /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: > Right now GRUB2 is unable to distinguish between 2 cases. However you can inform it that you have scamraid by adding following line to device.m= ap: (hd0) /dev/md0 > if (0 && dest_dev[0] =3D=3D 'm' && dest_dev[1] =3D=3D 'd' > && ((dest_dev[2] >=3D '0' && dest_dev[2] <=3D '9') || dest_dev[2] =3D= =3D '/')) > { > char **devicelist; > int i; > > devicelist =3D grub_util_raid_getmembers (dest_dev); > > for (i =3D 0; devicelist[i]; i++) > { > setup (arguments.dir ? : DEFAULT_DIRECTORY, > arguments.boot_file ? : DEFAULT_BOOT_FILE, > arguments.core_file ? : DEFAULT_CORE_FILE, > root_dev, grub_util_get_grub_dev (devicelist[i]), 1, > arguments.force, arguments.fs_probe); > } > } > > For a fakeraid setup, however, the BIOS presents the entire device as > "regular" int13 device, so GRUB2 really should be installing it to the > entire /dev/md### device, not the individual members. > > So what's the preferred way to differentiate BIOS fakeraid? Is there > some ioctl that would make this easier than having to parse /proc/mdsta= t? > > Thanks, > -John Sheu > > > _______________________________________________ > 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 --------------enigDC76EA97AAF7B52171D06026 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/ iF4EAREKAAYFAk0WTD4ACgkQNak7dOguQgkdYgD/Y/dX5O+qzKN7mCqSPBNuH6T4 5k+7wqZji8nBcrRUmMAA/3OEd0zlXCCerHBzNbbz8QI/KuUay1rdVPx+HYdBoqJt =JWSu -----END PGP SIGNATURE----- --------------enigDC76EA97AAF7B52171D06026--