On Sun, Jun 30, 2019 at 02:14:41PM -0400, Gao-Mi Baohao wrote:
> Don't forget about e.g. "boot disk2 -V" at your OpenBoot prompt. Have a
> look at
> https://github.com/openbsd/src/blob/master/sys/arch/sparc64/stand/bootblk/bootblk.fth
> .
>
> Match the verbose boot output with the debug messages in that bootblk.fth
> (look for statements in the source like "boot-debug? if") and see where it
> chokes. That will at least tell you if bootblk is getting the softraid
> okay, or if it's choking before you ever get to ofwboot. And that Forth
> bootblk doesn't need to be recompiled for debugging.
Thanks. That looks like it's getting the softraid data, and I presume loading
ofwboot from there:
Boot device: /pci@0/pci@0/pci@2/scsi@0/disk@2 File and args: sr0 -V
OpenBSD IEEE 1275 Bootblock 1.4
Booting from device /pci@0/pci@0/pci@2/scsi@0/disk@2,0:a
found softraid metadata
softraid-boot 28000 50
>> OpenBSD BOOT 1.12
ERROR: /iscsi-hba: No iscsi-network-bootpath property
Unknown device: sr0
Cannot boot from softraid: Unknown error: code 19
I don't know if I should see anything after the message from softraid-boot,
but assume "OpenBSD BOOT 1.12" is coming from the ofwboot that's loaded
from the softraid.
If you think more debugging in bootblk.fth would be valuable, I'm happy to
put more in. Just let me know how to reload that, because I am not
aware right now of how that gets stuck into place. installboot loads
/usr/mdev/bootblk, should I use fgen to build a new one? I can do that
when booted up from the ISO and running in chroot on the disks I think.
But, if we're already beyond that, I'll want to look into ofwboot...
- Chris
