> On Wed, Sep 27, 2017 at 08:06:15AM -0000, ti...@openmailbox.org wrote:
>> Hi!
>>
>> Crypto softraid is supported on GPT/UEFI boot and not just on BIOS/MBR boot,
>> right?
>>
>> It's supposed to work exactly the same way, just out of the box, the boot
>> code will ask for typed password or keydisk, right?
>>
>> Thanks,
>> Tinker
>
> http://www.openbsd.org/faq/faq14.html#softraid
Dear Stefan,
Thanks for responding - yes thanks for the obvious reference. For making GPT
booting work at all with OpenBSD, the "-b 960" argument to "fdisk -ig" that's
mentioned on the FAQ page, is instrumental, as "fdisk -ig" only creates a GPT
partitioning table whereas booting requires an EFI system boot partition too,
and fdisk creates that one only when "-b 960" is specified.
About automatic softraid unpacking on boot, the answer I found was that: Yes,
it is supported, but I think the boot order when booting softraid crypto on
GPT/UEFI is different from on MBR/boot.
I think on MBR/BIOS boot, the setup is that OpenBSD's MBR sector reads some
reserved subsequent sectors, which contain the unpacking code which ask you for
password/keydisk, and then unpacks the softraid, which will in turn contain the
boot code, which reads boot.conf .
In GPT/UEFI boot, OpenBSD's boot sequence is different: The host system's UEFI
firmware will load the /efi/boot/bootx64.efi file, which tries to load the
boot.conf file and then boot the system.
Unfortunately, bootx.64.efi does not get the idea of trying to boot sr0a:/bsd ,
but just tries hd0a:/bsd and then fails.
I tried to feed it with a boot.conf file by doing mount /dev/sd0i /mnt; mkdir
-p /mnt/etc; echo "boot sr0a:/bsd" >> /mnt/etc/boot.conf , however this has no
effect on the boot process, it still says the same as when the file was not
there:
probing: pc0 mem[572K 56K 495M 1455M 5M 6144M]
disk: hd0* hd1* hd2 sr0*
>> OpenBSD/amd64 BOOTX64 3.32
open(hd0a:/etc/boot.conf): Invalid Argument
boot>
This error may be because OpenBSD creating "boot.conf" within the FAT32 EFI
system boot volume actually crates "bo~1.con", which is not resolved as
"boot.conf" by OpenBSD's BOOTX64 EFI loader program? -
How do I instruct BOOTX64 to boot from sr0a:/boot ?
Also is this in the manual yet, where?
Thanks!
Tinker
