Date: Fri, 24 Sep 2004 16:05:48 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Chris Elsworth <chris@shagged.org> Cc: freebsd-geom@freebsd.org Subject: Re: WARNING: Expected rawoffset 0, found 63 ? Message-ID: <1096056348.9306.87.camel@zappa.Chelsea-Ct.Org> In-Reply-To: <20040924191938.GA84500@shagged.org> References: <20040924160620.GA77997@shagged.org> <1096044939.9306.54.camel@zappa.Chelsea-Ct.Org> <20040924171810.GA80912@shagged.org> <1096050986.9306.72.camel@zappa.Chelsea-Ct.Org> <20040924191938.GA84500@shagged.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2004-09-24 at 15:19, Chris Elsworth wrote:
> app1# bsdlabel -r /dev/mirror/gm
> # /dev/mirror/gm:
> 8 partitions:
> # size offset fstype [fsize bsize bps/cpg]
> a: 71119675 16 unused 0 0
> c: 71119691 0 unused 0 0 # "raw" part, don't edit
>
>
> So now another two things crop up - where has that a partition come from
> (perhaps that's just what bsdlabel -w does by default, no big deal)
> but more importantly, why do they both have an offset of 16 bytes..
> It didn't seem to mind me changing it to zero, though. So now I'll see
> if I can get it booting :)
I believe the above is bsdlabel's idea of an "auto" label. I don't know
why the 16 sector offset for the "a" partition, because you don't get
that when you label a slice via sysinstall and choose the "auto
defaults." (Maybe there's a case for making bsdlabel's "auto" label
behave the same as sysinstall.)
I edited mine from 16 to 0, too, when using (roughly) the same label as
my sysinstalled minimal system on the mirror device. I haven't noticed
any ill effects (touch wood:).
Cheers,
Paul.
--
e-mail: paul@gromit.dlib.vt.edu
"Without music to decorate it, time is just a bunch of boring production
deadlines or dates by which bills must be paid."
--- Frank Vincent Zappa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1096056348.9306.87.camel>