Date: Thu, 15 Jan 2009 16:09:49 +0100 From: Dimitry Andric <dimitry@andric.com> To: Marcel Moolenaar <xcllnt@mac.com> Cc: Randy Bush <randy@psg.com>, Luiz Otavio O Souza <lists.br@gmail.com>, George Neville-Neil <gnn@neville-neil.com>, Ben Kaduk <minimarmot@gmail.com>, current@freebsd.org Subject: Re: GEOM and moving to CURRENT from 7.1 Message-ID: <496F51BD.6010508@andric.com> In-Reply-To: <496F44FA.1070004@andric.com> References: <FC3D3CF7-091B-4ECF-BE38-6C7751C20994@neville-neil.com> <alpine.BSF.2.00.0901112002080.3696@ibyngvyr.purzvxnyf.bet> <496D0364.2060505@psg.com> <47d0403c0901131335h46e7b151p3768de9a3e2c2027@mail.gmail.com> <EC370904A7B74B93887C79E120CA2835@adnote989> <085BEE07-BAE5-4A45-A14D-9587987FAA5C@mac.com> <496F44FA.1070004@andric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-01-15 15:15, Dimitry Andric wrote: > On 2009-01-14 17:34, Marcel Moolenaar wrote: >>> The only way i've found to boot my system again is to compile a new >>> kernel with GEOM_BSD and GEOM_MBR, instead of GEOM_PART_*. >> Wipe out your second sector on the disk. You have a >> stale BSD disklabel that prevents the MBR from being >> used. > > Hmm, in my case I can't do so, since I have a "Dangerously Dedicated" > FreeBSD MBR partition. This apparently lets the MBR partition overlap > with the MBR itself, putting the disklabel on the sector following the > MBR. Just as a data point, I can confirm that adding GEOM_MBR fixes this issue. At least temporarily, until I find out the proper way. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?496F51BD.6010508>