Date: Wed, 11 Nov 2009 17:58:20 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: current@freebsd.org Subject: Re: How to confuse geom_part_mbr Message-ID: <7D0E66F2-A3E1-40F9-949B-7C4347E61E21@mac.com> In-Reply-To: <86d43omsb0.fsf@ds4.des.no> References: <86tyx0mxjw.fsf@ds4.des.no> <94D5F246-3413-4256-A0FB-6DF2D3BFE9D0@mac.com> <86d43omsb0.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 11, 2009, at 5:43 PM, Dag-Erling Sm=F8rgrav wrote: > Marcel Moolenaar <xcllnt@mac.com> writes: >> Dag-Erling Sm=F8rgrav <des@des.no> writes: >>> The machine won't boot, even though you have a valid partition table >>> on ad0 that points to a valid bsdlabel in ad0s1. >> No, you don't have a valid partition table on ad0, because >> you didn't remove the BSD disklabel in sector 2 on ad0. >=20 > Yes, I do have a valid partition table. It is exactly byte-by-byte > identical to the one I get after I zero sector two and re-run fdisk. > The fact that there is unwanted data in sector 2 does *not* make it = any > less valid. Of course it does. It's the same as GPT. There's a MBR in front of it and if you don't know about GPT tables, you'll see the MBR, otherwise you'll use the GPT. The difference is that the MBR in front of a BSD disklabel is not supposed to have partitions. But you may not be able to distinguish boot code from a valid partition entry. >=20 > What's more, this could have easily been avoided if geom_whatever gave > the partition table precedence over the label it found in sector 2. That break standard BSD disklabels, because they would be probed as MBRs. --=20 Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7D0E66F2-A3E1-40F9-949B-7C4347E61E21>