I'm going go try to simplify this a little more.. if that's even possible.
OpenBSD always addresses physical disks using disklabel partitions.. on a blank disk, the only partition would be 'c'.
For every disk in the system, a "fake" or "fictitious" label is created within the kernel when no actual label exists on the drive.
If you first booted OpenBSD's RAMDISK kernel, it created a fictitious label with foreign partitions mapped between i and p, after you added your OpenBSD partition and created your OpenBSD specific partitions, you kept the partitions mapped by the kernel in the disklabel you wrote to disk.
Quote:
|
Originally Posted by disklabel(8)
Note that when a disk has no real BSD disklabel, the kernel creates a default label so that the disk can be used. This default label will include other partitions found on the disk if they are supported on your architecture. For example, on systems that support fdisk(8) partitions the default label will also include DOS and Linux partitions. However, these entries are not dynamic, they are fixed at the time disklabel is run. That means that subsequent changes that affect non-OpenBSD partitions will not be present in the default label, though they may be updated by hand. To see the default label, run disklabel with the -d flag. disklabel can then be run with the -e flag and any entries pasted as desired from the default label into the real one.
|
So to repeat what jggimi said.. if you add partitions to fdisk AFTER you install OpenBSD, they will not be in your on-disk label, you need to add them manually.. or not at all, if you don't plan on accessing them.