Re: GPT boot, again

[Dima Veselov <kab00m%lich.phys.spbu.ru@localhost>]

> > > I installed /boot, ran installboot and gpt biosboot. Here is fdisk
> > > output for the disk:
> >
> > What flags installboot was used with?
>
> installboot -o console=com0,speed=115200 /dev/rdk2
> /usr/mdec/bootxx_ffsv2

Did you installed MBR ever? I always do that separately.

> Here is the result:
>
> # dkctl wd2 listwedges
> /dev/rwd2d: 3 wedges:
> dk3: efi@wd2, 524288 blocks at 34, type: msdos
> dk4: raid1@wd2, 11686966381 blocks at 524322, type: raidframe
> dk5: swap@wd2, 33554432 blocks at 11687490703, type: swap

Not sure you can do partitioning that way. You have to line up
fake MBR partition and real GPT booting partition, so they match.
In your case MBR partition is started at 1 sector, this is (usually)
64 block. Here we see that you have real booting partition at
524322. Nobody can point BIOS bootcode (MBR actually) to
that address. This how it will work:

[root@gloria kab00m]$ fdisk wd0
.....
cylinders: 5814021, heads: 16, sectors/track: 63 (1008 sectors/cylinder)
.....
0: GPT Protective MBR (sysid 238)
    start 1, size 4294967295 (2097152 MB, Cyls 0-267349/89/4)
        PBR is not bootable: Bad magic number (0x0000)

[root@gloria kab00m]$ dkctl wd0 listwedges
/dev/rwd0d: 5 wedges:
dk0: 5b9ff8df-0892-11e4-b3c8-001731c9c57a, 524288 blocks at 64, type: 
raidframe

They both point to 1 sector or 64 block. Also, you must have booting 
partition end
lined up too, so it never can be bigger than 2Gb.

> # installboot -ev NAME=raid1@wd2
> File system:         /dev/rdk4
> Boot options:        timeout 5, flags 0, speed 115200, ioaddr 0, console
> com0
>
> But I think it does not even reach that stage, since the BIOS just skips
> the disk.

Disk may be skipped because MBR corrupted, so you can reinstall
it after lining partitions up.