> So marking a partition as 'Active/Bootable', (the 00 -> 80 change) > causes your system to hang. Apparently Linux does this when you > 'Label' it. The OpenBSD installer does it for you when you > select 'Whole disk'. Nothing obviously to do with the disklabel. You > could test this by manually > setting the 'Active' flag on the working Linux MBR. Or, conversely > unsetting the flag with fdisk > after the OpenBSD install but before rebooting. In either case does it > get further before noticing that it can't boot?
I did some testing with the following results: 1. Partition disk with Linux gparted and use cfdisk to set partition type to A6 and OpenBSD disklabel to set disklabel. (partition: 0; start: 2048; size: 1953519616) - Bootflag off, no disklabel -> boot - Bootflag on, no disklabel -> boot - Bootflag off, with disklabel -> freeze - Bootflag on, with disklabel -> freeze 2. Partition disk with OpenBSD fdisk + disklabel (installer start + size). (partition: 3, start: 64; size: 1953520001) - Bootflag off, no disklabel -> freeze - Bootflag on, no disklabel -> freeze - Bootflag off, with disklabel -> freeze - Bootflag on, with diskalbel -> freeze 3. Partition disk with OpenBSD fdisk + disklabel (linux start + size). (partition: 3: start: 2048; size: 1953519616) - Bootflag off, no disklabel -> boot - Bootflag on, no disklabel -> boot - Bootflag off, with disklabel -> freeze - Bootflag on, with disklabel -> freeze 4. Partition disk with OpenBSD fdisk with type 83 (installer start + size). (partition: 3, start: 64; size: 1953520001) - Bootflag off -> freeze - Bootflag on -> freeze It looks like the motherboard doesn't like the partition to start at 64 and it also doesn't like disklabels. Any suggestions on what to try next or should I just buy a different motherboard? Kind regards, Martijn Rijkeboer
