Date: Thu, 1 Sep 2011 13:54:58 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Garrett Cooper <yanegomi@gmail.com> Cc: Jason Campbell <jason.lee.campbell@gmail.com>, Matt Thyer <matt.thyer@gmail.com>, freebsd-current@freebsd.org Subject: Re: Problems booting 9.0-BETA1 memstick Message-ID: <alpine.BSF.2.00.1109011345510.80217@wonkity.com> In-Reply-To: <24B9852A-8DE4-4BC6-9B55-2D74E414E31D@gmail.com> References: <CAMG0UAh1=Jy_eD5t%2BV_MkhVJrMFoe-OQQFgut1USr6v9CWMj4A@mail.gmail.com> <alpine.BSF.2.00.1108302109370.49311@wonkity.com> <CACM2%2B-4aU8VqaaKQnAXszFsU-097NLqHGdJP_u5LnbBWVoVtng@mail.gmail.com> <24B9852A-8DE4-4BC6-9B55-2D74E414E31D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 1 Sep 2011, Garrett Cooper wrote:
> On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
>
>> Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
>>
>> We won't need larger than 2TiB installation media for many decades!
>
> Or just don't use a backup partition? Maybe dd conv=sync would help?
It seems like the same problem as gmirror inside a GPT partition.
gptboot doesn't realize it's looking for backup GPT data in the wrong
spot. That might be a problem local to gptboot, or something deeper.
It seems wrong to have gptboot just ignore backup GPT data, but it could
be an option. Can it actually do something if the backup GPT differs,
or is it testing for an error that can't be handled?
MBR didn't have backup data ("Luxury! Pure luxury!"), and it did okay.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1109011345510.80217>