Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2018-01-23 Thread Lennart Poettering
On Di, 23.01.18 21:19, Bjørn Forsman (bjorn.fors...@gmail.com) wrote: > Hi Lennart, > > On 23 January 2018 at 20:22, Lennart Poettering > wrote: > > On Sa, 23.12.17 17:46, Bjørn Forsman (bjorn.fors...@gmail.com) wrote: > >> Would bootctl patches be considered for

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2018-01-23 Thread Bjørn Forsman
Hi Lennart, On 23 January 2018 at 20:22, Lennart Poettering wrote: > On Sa, 23.12.17 17:46, Bjørn Forsman (bjorn.fors...@gmail.com) wrote: >> Would bootctl patches be considered for inclusion? > Doing what precisely? Whatever is needed to support "bootctl install" on

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2018-01-23 Thread Lennart Poettering
On Sa, 23.12.17 17:46, Bjørn Forsman (bjorn.fors...@gmail.com) wrote: > On 14 December 2017 at 12:22, Lennart Poettering > wrote: > > On Do, 14.12.17 22:17, Michael Chapman (m...@very.puzzling.org) wrote: > >> It's perhaps unlikely for firmware itself to write to the

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-23 Thread Bjørn Forsman
On 14 December 2017 at 12:22, Lennart Poettering wrote: > On Do, 14.12.17 22:17, Michael Chapman (m...@very.puzzling.org) wrote: >> It's perhaps unlikely for firmware itself to write to the ESP, but certainly >> anything launched from the firmware can. One of my boot

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-15 Thread Andrei Borzenkov
On Thu, Dec 14, 2017 at 2:11 PM, Lennart Poettering wrote: > On Do, 14.12.17 11:55, D.S. Ljungmark (spi...@aanstoot.se) wrote: > >> Right, and _that_ causes a far less interesting output from blkid. >> >> /dev/md0: UUID="1492-1FE7" VERSION="FAT32" TYPE="vfat" >>

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread Lennart Poettering
On Do, 14.12.17 22:17, Michael Chapman (m...@very.puzzling.org) wrote: > On Sun, 10 Dec 2017, Bjørn Forsman wrote: > > On 9 December 2017 at 06:56, Andrei Borzenkov wrote: > > > [...] > > > Firmware is unaware of MD RAID and each partition is individually and > > >

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread Lennart Poettering
On Do, 14.12.17 11:55, D.S. Ljungmark (spi...@aanstoot.se) wrote: > Right, and _that_ causes a far less interesting output from blkid. > > /dev/md0: UUID="1492-1FE7" VERSION="FAT32" TYPE="vfat" > USAGE="filesystem" uh, why does it output "/dev/md0" as device for this? did you invoke it for

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread Michael Chapman
On Sun, 10 Dec 2017, Bjørn Forsman wrote: On 9 December 2017 at 06:56, Andrei Borzenkov wrote: [...] Firmware is unaware of MD RAID and each partition is individually and independently writable by firmware. 1. "Firmware is unaware of MD RAID". I agree. 2. "...

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread Lennart Poettering
On Do, 14.12.17 11:44, D.S. Ljungmark (spi...@aanstoot.se) wrote: > I seem to have the same problem, and here's the output: > > [root@spring ~]# blkid -p /dev/sda1 Well, I presume you are mounting /mnt/boot through the MD layer, right? Hence you need to check /dev/md0p1 or something instead.

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread D.S. Ljungmark
Right, and _that_ causes a far less interesting output from blkid. /dev/md0: UUID="1492-1FE7" VERSION="FAT32" TYPE="vfat" USAGE="filesystem" On Thu, Dec 14, 2017 at 11:53 AM, Lennart Poettering wrote: > On Do, 14.12.17 11:44, D.S. Ljungmark (spi...@aanstoot.se) wrote: >

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread D.S. Ljungmark
I seem to have the same problem, and here's the output: [root@spring ~]# blkid -p /dev/sda1 /dev/sda1: UUID="01c0c70f-9204-8e4e-f2a7-aa8ec14c4a41" UUID_SUB="2a820238-597c-bfd4-aa2e-19425f7e8fa4" LABEL="spring.skuggor.se:0" VERSION="1.0" TYPE="linux_raid_member" USAGE="raid"

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-11 Thread Lennart Poettering
On Fr, 08.12.17 23:33, Bjørn Forsman (bjorn.fors...@gmail.com) wrote: > 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 >

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-10 Thread Bjørn Forsman
On 9 December 2017 at 06:56, Andrei Borzenkov wrote: > [...] > Firmware is unaware of MD RAID and each partition is individually and > independently writable by firmware. 1. "Firmware is unaware of MD RAID". I agree. 2. "... independently writable by firmware". I don't

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-08 Thread Andrei Borzenkov
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

[systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-08 Thread 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).