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. On Sun, Jun 30, 2019 at 2:06 PM Chris Ross <cross+open...@distal.com> wrote: > On Sun, Jun 30, 2019 at 01:17:11PM -0400, Gao-Mi Baohao wrote: > > P.S. looks like there is some kung-fu going on in > > src/usr.sbin/installboot/sparc64_softraid.c with the install location of > > the ofwboot image that only occurs if you do installboot on the softraid > > itself. > > Looking at src/sys/arch/sparc64/stand/ofwboot/diskprobe.c, I see a couple > of things that might help. Is there a way to turn on the output of > DPRINTF() at runtime, or is that compile-time? And, there is some > code inside of #ifdef BOOT_DEBUG. If someone could provide me with > an ofwboot that was compiled with this extra debugging, I could use > installboot to install it, and maybe get a little more idea what the > code is failing to find on my server. > > Thanks for the info and help. > > - Chris > >
