atom feed14 messages in org.freebsd.freebsd-questionsWhy is 'disklabel'ng a new drive so d...
FromSent OnAttachments
Marc G. FournierMar 28, 2007 8:26 pm 
Kris KennawayMar 28, 2007 8:41 pm 
Marc G. FournierMar 28, 2007 8:48 pm 
ill...@gmail.comMar 28, 2007 9:04 pm 
Jerry McAllisterMar 28, 2007 9:20 pm 
Jerry McAllisterMar 28, 2007 9:24 pm 
Jerry McAllisterMar 28, 2007 9:29 pm 
RWMar 28, 2007 9:48 pm 
Jerry McAllisterMar 28, 2007 10:13 pm 
Antony MawerMar 29, 2007 10:07 pm 
Jerry McAllisterMar 29, 2007 11:22 pm 
Antony MawerMar 29, 2007 11:55 pm 
Jerry McAllisterMar 30, 2007 3:09 pm 
Daniel ErikssonMar 31, 2007 9:35 am 
Subject:Why is 'disklabel'ng a new drive so difficult?
From:Kris Kennaway (kr@obsecurity.org)
Date:Mar 28, 2007 8:41:10 pm
List:org.freebsd.freebsd-questions

On Wed, Mar 28, 2007 at 05:26:49PM -0300, Marc G. Fournier wrote:

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 edit 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

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 learned a useful trick the other day: you can use abbreviations like "1g", also '*' to mean "automatically calculate". See the manpage.

Kris