From: myglc2 <myglc2@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: Is there a way to write the bootloader to multiple drives?
Date: Tue, 16 May 2017 23:16:07 -0400 [thread overview]
Message-ID: <86efvoi360.fsf@gmail.com> (raw)
In-Reply-To: <877f1g7fcr.fsf@gnu.org>
On 05/16/2017 at 19:48 Ludovic Courtès writes:
> Hello,
>
> myglc2 <myglc2@gmail.com> skribis:
>
>> Is there a way to have 'guix system reconfigure' write the bootloader to
>> multiple drives?
>
> Why would you want to do that? (Honest question!)
>
> Ludo’.
When the drive with the bootloader fails (and you know it will, and at
the most embarrassing moment) the machine doesn't boot. My fantasy is
that if I could write the config as shown below, coaxing the machine
back into action will only involve reassembling the array with the good
drives. I know how to do this on Debian. I need to figure out how to do
it on GuixSD. ;-) Any advice?
You can achieve the save effect by manually replicating the bootloader
using dd. But you know that right before the drive fails you are going
to reconfig and 'guix gc' ;-) So having it in the config is better.
It would also be nice to enable optional automatic reassembly.
WDYT? - George
(bootloader (grub-configuration (device "/dev/nvme0n1"))
(bootloader (grub-configuration (device "/dev/sda")))
(bootloader (grub-configuration (device "/dev/sdb")))
(initrd (lambda (file-systems . rest) (apply base-initrd file-systems
#:extra-modules '("raid1")
rest)))
(mapped-devices (list (mapped-device
(source '("/dev/nvme0n1p1" "/dev/sda1" "/dev/sdb1"))
(target "/dev/md3")
(type raid-device-mapping))))
(file-systems (cons (file-system
(title 'device)
(device "/dev/md3")
(mount-point "/")
(type "ext4")
(dependencies mapped-devices))
%base-file-systems))
prev parent reply other threads:[~2017-05-17 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 14:23 Is there a way to write the bootloader to multiple drives? myglc2
2017-05-16 19:48 ` Ludovic Courtès
2017-05-17 3:16 ` myglc2 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86efvoi360.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).