From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1W2alQ-0001zj-Sy for mharc-grub-devel@gnu.org; Mon, 13 Jan 2014 01:12:44 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38221) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W2alP-0001zX-2d for grub-devel@gnu.org; Mon, 13 Jan 2014 01:12:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W2alN-0005VO-Ix for grub-devel@gnu.org; Mon, 13 Jan 2014 01:12:42 -0500 Received: from mail-wi0-x22b.google.com ([2a00:1450:400c:c05::22b]:45910) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W2alN-0005VI-Cl for grub-devel@gnu.org; Mon, 13 Jan 2014 01:12:41 -0500 Received: by mail-wi0-f171.google.com with SMTP id cc10so592153wib.16 for ; Sun, 12 Jan 2014 22:12:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=FCO2CcY2y1t3iz7XpMgGZmvgjE8+aBwLwU7OG1e00nI=; b=yiX5v65Q+F2Sl+By5/PxoDW7ADczfKewfhNjRXPIzDl/nkMqURHI6G5p1U1/LWxKxV /KyU5WtyFV3K6qvtsSFNMAsvd7cW/dYhu9+vFQIEDg2F7YZfz/KuRYlUHVoHA3Ec2Gz5 tDmPBCoix/29+pmp+9FG4q/XDPTC3QZnUz2bw6sH9rQ/0BQG1Ll1Qgo4nxGn37qtl5Gk BNjcQa7czf2F0YZd+4NqxOZtbsp2g7rWF97gTr/OMndUQ0Ns2h41lhdOOQgl9X2J3wA2 VfLI9o23XvP16PDWEFgp11Hg0nHeuxu0gWx0q6QV1Zqs1wf1RwkeR3mZHXJukw0D6cRt YLQQ== MIME-Version: 1.0 X-Received: by 10.194.80.137 with SMTP id r9mr349476wjx.88.1389593560434; Sun, 12 Jan 2014 22:12:40 -0800 (PST) Received: by 10.216.237.133 with HTTP; Sun, 12 Jan 2014 22:12:40 -0800 (PST) Date: Mon, 13 Jan 2014 10:12:40 +0400 Message-ID: Subject: Booting from RAID (was: Re: booting btrfs) From: Andrey Borzenkov To: The development of GNU GRUB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::22b 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: Mon, 13 Jan 2014 06:12:44 -0000 On Mon, Jan 13, 2014 at 9:53 AM, Chris Murphy wro= te: > There are other problems with Fedora that prevent this from being usable = now, including grubby which can't update grub.cfg during kernel updates, wh= en /boot is on a Btrfs subvolume. So I have no present implementation, it's= a question how to boot from Btrfs raid1 in the future, and have as little = duplicative efforts as possible. Also, my argument is that if a GUI install= er permits the user to create bootable raid1, that it should also properly = configure all drives, and the static ESP grub.cfg, to make the system boota= ble. Otherwise the user has to do this manually which requires esoteric kno= wledge beyond most users. If the system really isn't bootable in the face o= f a disk failure, then I think a GUI installer shouldn't even offer bootabl= e raid1 (Btrfs or otherwise) as an option. 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. 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, but modifying grub-setup part is more challenging.