Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 May 2009 10:36:32 -0700
From:      Freddie Cash <fjwcash@gmail.com>
To:        current@freebsd.org
Subject:   Re: fdisk incompatibility between major versions
Message-ID:  <b269bc570905251036l3b7534ccjf16dab34b0686e89@mail.gmail.com>
In-Reply-To: <4A1AD6D3.7030100@rcn.com>
References:  <4A1AD6D3.7030100@rcn.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mon, May 25, 2009 at 10:35 AM, Robert Huff <roberthuff@rcn.com> wrote:
>   Due to a combination of my spectacular stupidity and external events, a
> machine running -Current from late April will no longer boot.  Specifically,
> instead of the loader menu screen I get "Invalid partition".
>   Crud.
>   Broke out the most recent fixit disk, which is from 7.1 (Jan 2009).
>   Boots fine; fdisk finds the correct slice information; bsdlabel finds the
> right partition data; mount / and /usr under LiveFS
>   Whew!!!!
>   So ... I'm guessing the problem in the boot code is corrupted, and if I do
>
>    fdisk -B -b <path to -CURRENT boot blocks> da0
>
>    it should put things back to normal.
>    However: when I do the second commit I get
>
>    fdisk: Geom not found "da0"
>    fdsk: failed to write sector 0

In order to alter a drive with a mounted filesystem (ie an active
drive), you need to first set the drive to writable:

sysctl -w kern.geom.debugflags=16

This has been the case for several years now (since 5.x I believe).

-- 
Freddie Cash
fjwcash@gmail.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b269bc570905251036l3b7534ccjf16dab34b0686e89>