On Mon, 19 Jul 2021 at 17:58, Jeff Rizzo <riz%tastylime.net@localhost> wrote:
In case it clarifies anything, here's what the GPT looks like on all the
disks (more or less):
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 230686720 1 GPT part - NetBSD RAIDFrame component
230686754 7583350381 2 GPT part - ZFS
7814037135 32 Sec GPT table
7814037167 1 Sec GPT header
For the EFI boot to work, you need a FAT16/FAT32 partition, I don't
see one. The default GPT sysinst partitioning will create one and copy
the netbsd.efi file, which then should be selectable for boot - if EFI
is enabled of course. Not much else - no boot blocks or anything of
the type, just a partition with some .efi files available. On my HP
(laptops only) I have several of these, booting different systems, one
of them being NetBSD-current:
┌───────────────────◀▶
│C:/Temp
└─▶ dir e:\EFI\BOOT\
Directory: e:\EFI\BOOT
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 30/06/2018 01:16 icons
-ar-- 29/05/2018 17:02 215855 bootia32.efi
-a--- 30/06/2018 01:17 205874 bootx64-netbsd.efi
-ar-- 29/05/2018 17:02 205874 bootx64.efi
....
In my case I have to interrupt the default boot process and select an
.efi file to boot (in one of the last BIOS/UEFI updates HP removed the
option of setting an .efi file as the default boot option - prior to
that I had refind setup as the default, which then let me boot
graphically another 7-8 different systems).
Of course I don't know if this somewhat old server has UEFI at all.
For this to work with NetBSD, it should support UEFI in CSM mode
without trusted boot being enabled.
Anyone care to help? :) Thanks in advance!
+j
Chavdar