amd64/186515: Doesn't boot with GPT when # of entries over than 128.

[James R. Van Artsdalen]

On 2/7/2014 6:42 AM, Andrey V. Elsukov wrote:
> On 06.02.2014 23:30, John Baldwin wrote:
>>  Using more entries to pad out the table isn't the normal way to handle 4k 
>>  alignment.  You can just leave a gap before the start of freebsd-boot.  Having 
>>  the sectors "free" vs having them contain zero'd GPT entries doesn't really 
>>  make a difference.  One question is when does the boot break?  Does it make it 
>>  into the loader and break trying to boot the kernel?  Does it make it into 
>>  gptboot and break trying to load the loader?
> Hi John,
>
> this is gptboot's restriction. Look at the sys/boot/common/gpt.c.
>

For the last couple of years every FreeBSD system I've installed has
been partitioned by this command:

bigtex:/root# grep -- -s.gpt mkdisk.sh
gpart create -s gpt -n 152 "$DISK" || exit

yielding something like

bigback:/root# gpart show
=>        40  3907029089  ada0  GPT  (1.8T)
          40         128     1  freebsd-boot  (64K)
         168    29828864     2  freebsd-swap  (14G)
    29829032  3877200097     3  freebsd-zfs  (1.8T)

I guess the bug is unique to GPT UFS booting?