> On Wed, Sep 27, 2017 at 10:31:22AM -0000, ti...@openmailbox.org wrote:
>> 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? -
>
> boot.conf has nothing to do with it.
> softraid boot is handled independently from boot.conf.
>
>> How do I instruct BOOTX64 to boot from sr0a:/boot ?
>
> What's odd is that you have a bootable sr0 but the boot loader still
> tries hd0 instead. That looks like a bug. Usually sr0 should be tried
> in this situation.
>
> I don't know the solution. Perhaps try re-running installboot?
>
> FWIW, this all works fine for me on a thinkpad helix2.
Hi Stefan,
I first tried booting the machine (by typing "boot sr0a:/bsd" in the boot
console of course), and doing "installboot -v sd0". It says:
Using / as root
installing bootstrap on /dev/rsd0c
using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot
copying /usr/mdec/BOOTIA32.EFI to
/tmp/installboot.MjdT8BAY8o/efi/BOOT/BOOTIA32.EFI
copying /usr/mdec/BOOTIX64.EFI to
/tmp/installboot.MjdT8BAY8o/efi/BOOT/BOOTIX64.EFI
..and after rebooting the machine, booting was still not automatic.
I then booted the machine (by typing "boot sr0a:/bsd" in the boot console again
of course) and did "installboot -v sd1", and it gave:
Using / as root
installing bootstrap on /dev/rsd0c
using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot
sd1: softraid volume with 1 disk(s)
sd1: installing boot loader on softraid volume
/usr/mdec/boot is 6 blocks x 16384 bytes
copying /usr/mdec/BOOTIA32.EFI to
/tmp/installboot.1lt1hgtQYa/efi/BOOT/BOOTIA32.EFI
copying /usr/mdec/BOOTIX64.EFI to
/tmp/installboot.1lt1hgtQYa/efi/BOOT/BOOTIX64.EFI
Rebooting, that also did not help.
I tried with "fdisk -e sd1" and disabling the 1 (EFI) partition by setting its
type to 0 (so that installboot would not try to install any EFI files to sd1i)
and then doing "installboot sd1", and that did not help too.
What am I doing wrong, are there actually any installboot arguments that could
help me make it work?
Would I need to add some debug output lines to installboot? Actually, it would
be nice if installboot's verbose mode would clarify which configuration the
boot code is actually set up with, so the user is a bit more saved from the
wild-guessing-by-a-large-number-of-reboots-hoping-for-the-best kind of method
I'm refered to right now. Please let me know what I should do now to fix it -
Thanks,
Tinker
