Tonton, Tonton wrote:
Hi, no, I use mdadm. Can GRUB see/use/boot this?
Yes! Then I think Guix has everything you need.
Maybe this is way easier than I thought. Could you share how you configure this on your end?
Nothing fancy: --8<---------------cut here---------------start------------->8--- (mapped-devices (list (mapped-device (type raid-device-mapping)(source (list "/dev/sda2" "/dev/sdb2" "/dev/sdc2" "/dev/sde2"))
(target "/dev/md0")))) (file-systems (cons* (file-system (dependencies mapped-devices) ; XXX is this needed? (device "/dev/md0") (mount-point "/") (type "btrfs") (options "compress=zlib,relatime")) (file-system (device (file-system-label "EFI")) (mount-point "/boot/efi") (create-mount-point? #t) (type "vfat")) %base-file-systems)) … (bootloader (bootloader-configuration (bootloader grub-efi-bootloader) (target "/boot/efi") (timeout (seconds 1)))) --8<---------------cut here---------------end--------------->8---(That comment's been there for years; in true admin fashion I haven't touched a working set-up.)
Guix doesn't use mdadm.conf or whatever it's called. Depending on your system, using labels or UUIDs instead of device names could make it more robust, or merely complicate drive replacement in future.
Adding LUKS to this mix should be possible too, but I haven't tried it myself.
Kind regards, T G-R
signature.asc
Description: PGP signature
