From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1W7I9F-0005kZ-I8 for mharc-grub-devel@gnu.org; Sun, 26 Jan 2014 00:20:45 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58851) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7I98-0005jx-By for grub-devel@gnu.org; Sun, 26 Jan 2014 00:20:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W7I91-0001jM-W8 for grub-devel@gnu.org; Sun, 26 Jan 2014 00:20:38 -0500 Received: from mail-lb0-x236.google.com ([2a00:1450:4010:c04::236]:51860) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7I91-0001jI-N9 for grub-devel@gnu.org; Sun, 26 Jan 2014 00:20:31 -0500 Received: by mail-lb0-f182.google.com with SMTP id w7so3555390lbi.41 for ; Sat, 25 Jan 2014 21:20:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type; bh=uTwLUq5nMa/SbBw9qmf42u7eyplA0YZIqz+XSkde2es=; b=A3xBnGR5BiZX9Wv5oriM5wKWsUJdPWjIBFOm0c7pvuR7fvCdKbrOAPPyzmhEreR3jl UA3Fa/Dm2hwgIJwtWJ++RCMbjJhCUsURAVzEM1qBeNgk0ldk2t5CxiMf02raPhol77Y5 y/Qbq28hSuKFskuSDtkjsgkPCN9Q5zf5rMqHIum9fvG9nGbilbO82C2GQPFqR3eGc54N OGLBvTXJk0NBnr9z6KfVSsK/POF5eO4IORxv9+EKFLQcah+AcR9PDKG7zwsJdDvSZpwM we9fYOYCI7R64QFDB1eln7AQYD2is3q/peSRiwQJX6TxEq1zS6co4l7UORbEoMcmMQ0w BDFQ== X-Received: by 10.112.43.70 with SMTP id u6mr12955232lbl.30.1390713630672; Sat, 25 Jan 2014 21:20:30 -0800 (PST) Received: from opensuse.site (ppp91-76-154-95.pppoe.mtu-net.ru. [91.76.154.95]) by mx.google.com with ESMTPSA id k1sm1404026lbc.5.2014.01.25.21.20.29 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Sat, 25 Jan 2014 21:20:29 -0800 (PST) Date: Sun, 26 Jan 2014 09:20:27 +0400 From: Andrey Borzenkov To: grub-devel@gnu.org Subject: Re: Booting from RAID (was: Re: booting btrfs) Message-ID: <20140126092027.25cc8883@opensuse.site> In-Reply-To: <52DE29E8.5000202@gmail.com> References: <52DE29E8.5000202@gmail.com> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.22; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/AE0SdNoZfpioK02fT=Qsltw"; protocol="application/pgp-signature" X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::236 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 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: Sun, 26 Jan 2014 05:20:44 -0000 --Sig_/AE0SdNoZfpioK02fT=Qsltw Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =D0=92 Tue, 21 Jan 2014 09:03:52 +0100 Vladimir '=CF=86-coder/phcoder' Serbinenko =D0=BF=D0=B8= =D1=88=D0=B5=D1=82: > On 13.01.2014 07:12, Andrey Borzenkov wrote: > > On Mon, Jan 13, 2014 at 9:53 AM, Chris Murphy = wrote: > >=20 > >> There are other problems with Fedora that prevent this from being usab= le now, including grubby which can't update grub.cfg during kernel updates,= when /boot is on a Btrfs subvolume. So I have no present implementation, i= t's a question how to boot from Btrfs raid1 in the future, and have as litt= le duplicative efforts as possible. Also, my argument is that if a GUI inst= aller permits the user to create bootable raid1, that it should also proper= ly configure all drives, and the static ESP grub.cfg, to make the system bo= otable. Otherwise the user has to do this manually which requires esoteric = knowledge beyond most users. If the system really isn't bootable in the fac= e of a disk failure, then I think a GUI installer shouldn't even offer boot= able raid1 (Btrfs or otherwise) as an option. > >=20 > > openSUSE supports /boot on RAID1 and will simply run grub-install for > > each device (it limits bootloader location to MBR in this case). This > > can be optimized of course noticing that you need to create image just > > once, but it works. Same can be used in case of btrfs. > >=20 >=20 > > I'd like to have some more generic case of having several boot block > > locations independently on RAID (effectively grub-install /dev/sda > > /dev/sda3 /dev/sdb ...); grub-install part looks more or less > > straightforward, > You need to be careful with root_dirve =3D=3D boot_drive check in this ca= se. > You may have to create 2 images if this supposition is true for some > locations but not all. > > but modifying grub-setup part is more challenging. > >=20 > It should invoke stup part several times. Sure, but I would rather avoid aborting on the first error and continue to install to further locations if possible. That was easy with shell utilities but became less though today. --Sig_/AE0SdNoZfpioK02fT=Qsltw Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlLkmxsACgkQR6LMutpd94wMPQCgkttWcNX/gFHtX4F6r5xhv3kd LgYAniLsfOO8kKNEfmfvF0+HztoHW3BU =1enY -----END PGP SIGNATURE----- --Sig_/AE0SdNoZfpioK02fT=Qsltw--