Date:        Tue, 8 Jul 2025 07:11:05 +0000 (UTC)
    From:        RVP <r...@sdf.org>
    Message-ID:  <e3a190e2-d660-5955-d18b-9639590c3...@sdf.org>

  | So, you want BIOS + GPT? Hmm, this'll be a bit tricky, I think.

No, it shouldn't be.   If it were just that it would be trivial.

That it is BIOS + GPT + GRUB makes it more interesting (to some anyway).

  | > dk2: NetBSD, 125829120 blocks at 269486080, type: msdos  # <<<
  | This should be type `ffs', but, no matter because, ...

It might actually matter.

  | I don't think bootxx_ffsv2 understands GPT.

It actually does, to a degree, but for this, that should be
almost irrelevant I think.

  | Here, I think it finds only the
  | Protective MBR (and no NetBSD-type primary partition) and throws this error.

The reported error came from grub, nothing in NetBSD is going to be
complaining about a "slice", that's not a concept that exists here,
or more accurately, that's not a name we use for anything that exists.

  | Try creating an Hybrid MBR with an NetBSD-type MBR entry with start and size
  | corresponding to that of `dk2' (gdisk(8) on Linux).

No, don't do that.   That will just make a mess, and is not needed.

And to answer a question from the message that prompted that reply,
there is no problem at all leaving bootxx_ffsv2 installed - all FFS
filesystems (whether you intend to boot from them or not) have a (small)
space reserved for that, if it isn't used (most FFS filesystems) it
usually just contains zeroes, but unless you're booting from it, nothing
cares what is there.

You should not however have any kind of disklabel in a GPT partition (though
if you just ask to see one, the kernel will invent something and pass it
back without it ever existing on the drive).

I can't help with configuring or using grub correctly, but from the reported
error, that looks to be where the problem is (provided of course that the
filesystem in /dev/dk2 is in fact an FFSv2 filesystem - use
        dumpfs /dev/rdk2
to check it.)   You really need someone who really understands grub to
diagnose possible causes for a "NO SLICE" error message.

If there is a need to send another message about this, include the
output from

        gpt show -a wd0

kre

Reply via email to