On Wed, 5 Oct 2022 at 18:42, Martin Husemann <[email protected]> wrote: > > On Wed, Oct 05, 2022 at 04:13:31PM +0100, Ottavio Caruso wrote: > > 5) Selected NetBSD (dk6@wd0) > > > > 6) The menu goes back to point 3 without any apparent errors. > > > > I would have expected the menu would offer to create a disklabel from > > there, but it didn't. > > > > No apparent warnings in dmesg. > > As Chavdar said: there will be no disklabel, the GPT partitions (and dk* > wedges) will be enough. > > But what you observed clearly is a bug somewhere in sysinst, I'll try to > reproduce it locally.
Update: good news and bad news. Good news: I was able to install NetBSD by nuking the ffsv2 partition and recreating it from scratch, as suggested here: https://mail-index.netbsd.org/netbsd-users/2020/10/01/msg025800.html Bad news. The installer didn't ask me if and where I wanted to install the bootloader and now I can't boot into NetBSD. "update-grub2" from Linux doesn't pick the NetBSD partition. All I need to know now is: 1) How do I know if the bootloader has been installed 2) How do I chainload it from Grub. Now, reading this: https://wiki.netbsd.org/Installation_on_UEFI_systems/ I don't if it is really still relevant as it was meant for NetBSD 8.*, it looks like I have to manually copy the bootloader files onto the EFI partition. I have mounted the FFSv2 partition onto Linux and this is the fstab: # NetBSD /etc/fstab # See /usr/share/examples/fstab/ for more examples. NAME=NetBSD / ffs rw 1 1 NAME=EFI\ system\ partition /boot msdos rw 0 0 kernfs /kern kernfs rw ptyfs /dev/pts ptyfs rw procfs /proc procfs rw tmpfs /var/shm tmpfs rw,-m1777,-sram%25 Is /boot the correct mount point and are there any files to be copied over? Shouldn't sysinst have dealt with this already? -- Ottavio Caruso A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
