[00:59] <KeeperoftheKeys> hey
[00:59] <KeeperoftheKeys> I suspect this question has come up in the past but I haven't found a sufficient answer for it so far
[01:00] <KeeperoftheKeys> Is there any reason the server installer doesn't allow me to use a mdadm raid1 with 0.90 metadata as ESP device?
[01:01] <KeeperoftheKeys> I have a Debian machine that boots that way (granted I had to fix booting because the Debian installer also couldn't figure out where to put boot stuff, but in the end of the day this is a bootable config)
[01:02] <KeeperoftheKeys> config - 2 disks, each disk formatted GPT, part 1 256M mdraid1 vfat ESP, part 2 rest mdraid1 btrfs (yes I know that I could have done raid1 at the btrfs level)
[01:03] <sarnold> KeeperoftheKeys: if I've understood correctly, it's because the filesystem in question can be modified from other operating systems or from the uefi boot environment itself, and would therefore bust your raid; dpkg-reconfigure grub-pc or grub-efi-amd64 or something like that should make it possible to install into two filesystems and keep some semblance of redundancy there
[01:05] <KeeperoftheKeys> you mean that the UEFI env might write to only one of the 2 drives?
[01:06] <KeeperoftheKeys> (thanks for the quick response :))
[01:07] <patdk-lap> well, the esp is shared between operating systems and even the bios
[01:07] <patdk-lap> I install a uefi shell and firmware updates using it
[01:07] <patdk-lap> but anything done outside of linux won't be able to mount the mdadm raid and keep it in sync
[01:07] <patdk-lap> if you never plan to, ya, mdadm would be accaptable
[01:08] <patdk-lap> or just let grub do it's thing, and your always be bootable to ubuntu, just not maybe anything else that is custom added to the esp partition
[01:08] <KeeperoftheKeys> for me it would be in linux or EFI so the moment the OS was booted change would sync over
[01:09] <KeeperoftheKeys> if I add both disks as boot disks like most tutorials suggest what is making sure that both /boot/efi and /boot partitions remain in sync?
[01:09] <KeeperoftheKeys> (instead of mdraid)
[01:11] <patdk-lap> mdadm should make sure boot partition is
[01:11] <patdk-lap> but grub would do it's normal thing for efi
[01:12] <patdk-lap> it won't make sure both are in sync
[01:12] <patdk-lap> it would make sure the ubuntu entry in both boots grub
[01:13] <KeeperoftheKeys> ok will try that, don't feel like fighting more with the installer now like I did with my Debian install the other day
[11:28] <flaf> dbungert: I have filed the "bug" as you wanted (maybe it's not a bug). Here is the link: https://bugs.launchpad.net/subiquity/+bug/1956452. Bye. :)