Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails
09.12.2017 01:33, Bjørn Forsman пишет: > Hi all, > > I assumed bootctl would be able to install onto a mdadm raid 1 array > (mirror). But this happens: > > $ bootctl --path=/mnt/boot install > Failed to probe partition scheme "/mnt/boot": Input/output error > > The raid array is created with --metadata=0.90 (superblock at the end > of device). systemd v234 was used for testing. > > I see people online that have worked around this by setting up the ESP > (/boot) manually, and finalizing the install with 2x calls to > efibootmgr. But I'm hoping for bootctl to handle this for me :-) > > Any ideas? > Firmware is unaware of MD RAID and each partition is individually and independently writable by firmware. Pretending that you can mirror them on OS level is simply wrong. Also each ESP requires own boot menu entry to be usable. Having common cross-bootloader standard of representing and dealing with redundant ESP would be good thing though. But mdadm is not one one of them :) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-networkd-wait-online
Thanks. I’m not surprised that work remains ... Related question: systemd-networkd-wait-online.target seems to assume that once the network is online, it stays that way. I’d like to also take action when it goes down, and again when it comes back up. Any pointers how to best go about this? Is there an inverse of the systemd-networkd-wait-online executable? Thanks, Johannes. > On Dec 6, 2017, at 3:30, Lennart Poetteringwrote: > > On Di, 05.12.17 12:21, Johannes Ernst (johannes.er...@gmail.com) wrote: > > See the discussion on > https://github.com/systemd/systemd/issues/7478#issuecomment-348508263 > regarding this kind of hardware. > > Lennart > > -- > Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] "bootctl install" on mdadm raid 1 fails
Hi all, I assumed bootctl would be able to install onto a mdadm raid 1 array (mirror). But this happens: $ bootctl --path=/mnt/boot install Failed to probe partition scheme "/mnt/boot": Input/output error The raid array is created with --metadata=0.90 (superblock at the end of device). systemd v234 was used for testing. I see people online that have worked around this by setting up the ESP (/boot) manually, and finalizing the install with 2x calls to efibootmgr. But I'm hoping for bootctl to handle this for me :-) Any ideas? Best regards, Bjørn Forsman ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel