Your disk layout is strange, an EFI partition is typically initialised by a GPT disk, not MBR.
GPT has a number of advantages including no differentiation between primary and extended partitions, and beating the 2TB limit of MBR. When created, GPT also creates a 'protective MBR' covering the whole disk, so that older tools that only understand MBR don't break things. You can, if you know what you're doing, manipulate this protective MBR but you shouldn't - it will have odd effects and different operating systems will interpret it in different ways (Linux will be a bit upset). In short : either use all GPT partitioning tools to edit your disk, or wipe it clean and restart with MBR. Matthew is absolutely right about MBR otherwise. Generally MBR partitions and a disklabel have a direct mapping, but you can for instance, ignore the partition scheme. Imagine you have an old system that only boots partitions below 128GB or less but you want to use over that amount for OpenBSD? A solution is to create two partitions, one up to 128GB and the second over. Then adjust the disklabel to cover the two partitions, but make sure that the root section of the disklabel is entirely contained in the first MBR partition. MBR is also a pain, because not everything understands extended partitions/logical drives, notably FreeBSD. If you are doing multiboot (I set up an epic two Windows, three BSD, and Linux multiboot config last night for bare metal testing on a virtualised system) I'd recommend the following : Generally partition using Windows. It works well, most of the tools are graphical, and it can install in GPT, and both primary and extended MBR partitions. Modify partition IDs using OpenBSD, it's really good for that. FreeBSD does not like extended partitions. What I need to look up is why disklabels stop at 'p', as it's an issue on disks with lots of non OpenBSD partitions. PK
