Why is 'disklabel'ng a new drive so difficult?
jerrymc at msu.edu
Wed Mar 28 21:24:29 UTC 2007
On Wed, Mar 28, 2007 at 04:04:49PM -0500, illoai at gmail.com wrote:
> On 28/03/07, Marc G. Fournier <freebsd at hub.org> wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09
> >Tried to disklabel it, and it gives me all kinds of warnings when I look
> >at it
> >after running the disklabel:
> >ganymede# bsdlabel -w ad4s1 auto
> >ganymede# bsdlabel ad4s1c
> ># /dev/ad4s1c:
> >8 partitions:
> ># size offset fstype [fsize bsize bps/cpg]
> > a: 976767986 79 unused 0 0
> > c: 976768002 63 unused 0 0 # "raw" part,
> > don't
> >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
> >Even if I try to use /stand/sysinstall to do the fdisk, the end result has
> >'issues' ...
> >So, what is the generally accepted method of label'ng a new drive? :(
> I think you have it correct (or "right" as they say).
> When I:
> % bsdlabel [da|ad]NsNc
> those very error messages are horked up on _some_
> To me
> % bsdlabel [da|ad]NsN
> has always been the correct method.
Yes, do not use the 'c' on the bsdlabel command.
Just make is da0s1 or ad0s1 (or whichever drive and slice it really is).
If you do a 'baslabel -e [da|ad]NsN' it will give you a nice
edit session with an appropriate value for the 'c:' line and
you can easily go from there.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions