14 messages in org.freebsd.freebsd-questionsWhy is 'disklabel'ng a new drive so d...| From | Sent On | Attachments |
|---|---|---|
| Marc G. Fournier | Mar 28, 2007 8:26 pm | |
| Kris Kennaway | Mar 28, 2007 8:41 pm | |
| Marc G. Fournier | Mar 28, 2007 8:48 pm | |
| ill...@gmail.com | Mar 28, 2007 9:04 pm | |
| Jerry McAllister | Mar 28, 2007 9:20 pm | |
| Jerry McAllister | Mar 28, 2007 9:24 pm | |
| Jerry McAllister | Mar 28, 2007 9:29 pm | |
| RW | Mar 28, 2007 9:48 pm | |
| Jerry McAllister | Mar 28, 2007 10:13 pm | |
| Antony Mawer | Mar 29, 2007 10:07 pm | |
| Jerry McAllister | Mar 29, 2007 11:22 pm | |
| Antony Mawer | Mar 29, 2007 11:55 pm | |
| Jerry McAllister | Mar 30, 2007 3:09 pm | |
| Daniel Eriksson | Mar 31, 2007 9:35 am |
| Subject: | Why is 'disklabel'ng a new drive so difficult? | |
|---|---|---|
| From: | Jerry McAllister (jerr...@msu.edu) | |
| Date: | Mar 28, 2007 9:24:08 pm | |
| List: | org.freebsd.freebsd-questions | |
On Wed, Mar 28, 2007 at 04:04:49PM -0500, ill...@gmail.com wrote:
On 28/03/07, Marc G. Fournier <free...@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 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 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_ drives. 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.
////jerry
--
--
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "free...@freebsd.org"