partition C doesn't start at 0!

[Jason C. Wells]

On Tue, 9 Sep 2003, Ulrich Spoerlein wrote:

> On Mon, 08.09.2003 at 22:06:58 -0700, Jason C. Wells wrote:
> > I can boot from ad0s1.  I am still monkeying around with the ad0s2 slice.
> > In the process of trying to get ad0s2 to boot with a PicoBSD-esque system,
> > I looked at my disklabel and I saw all kinds of scary messages.
> >
> > # bsdlabel ad0s1
> > partition a: partition extends past end of unit
> > partition c: partition extends past end of unit
> > bsdlabel: partition c doesn't start at 0!
> > bsdlabel: An incorrect partition C may cause problems for standard system
> > utilities.
>
> What does
> # fdisk -s ad0
> and
> # bsdlabel ad0s1
> # bsdlabel ad0s2
> say?

/dev/ad0: 1654 cyl 16 hd 63 sec
Part        Start        Size Type Flags
   1:          63      262017 0xa5 0x80
   2:      262080      131040 0xa5 0x00
   3:      393120     1274112 0xa5 0x00
# /dev/ad0s1:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:   262017        0    4.2BSD     2048 16384 16384
  c:   262017        0    unused        0     0         # "raw" part,
don't edit
# /dev/ad0s2:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:   131040        0    4.2BSD     2048 16384  8192
  c:   131040        0    unused        0     0         # "raw" part,
don't edit

BTW, my apologies to anyone who got a bounce message from an old anti-spam
measure that I forgot was in place.  I have removed the "world" from my
blacklist. :o

Thanks,
Jason C. Wells