|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:20:03 pm|
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 see you must have run fdisk on it and created a slice. That's good.
Also, although you keep saying disklabel, I see you are using the bsdlabel command, so that is good.
Then, the only thing wrong is that your offsets should start at 0. They mean within the slice, not raw disk sector 0.
I don't know the actual size of the slice, but if it is 9 7676 8002 then starting at sector 63 and going for that size will make it go beyond the disk slice.
If you did a 'bsdlabel -e ad4s1' (no 'c' on it)
it should put you in an edit session and plug in the correct offset (0 in this case) and size for the slice in the c: line.
You appear to want to use all the slice for one partition, so just dup that c: line and make the copy be a: Then change the fstype from 'unused' to '4.2BSD' and the [fsize bsize bps/cpg] fields be 2048 16384 28552 or doubled or just let it pick those fields.
You can also put '*' in the offset and size fields for the a: line and it will create one partition that takes up the whole slice.
If you make more than one partition, still make the offset be '*', but you can name the sizes in blocks or by size such as 10g, 512m, etc and then put '*' in for the size of the last partition and it will make the sizes you specify and then make that last partition take all that remains.
Don't forget to newfs the partition[s].
- ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFGCs+Q4QvfyHIvDvMRAmTBAJwMJeMPTiJEDHWzA3ffe/YnVvRdgwCfVkBt YsPlRNHb6p3WJSIqMXA1K78= =n8pH -----END PGP SIGNATURE-----
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "free...@freebsd.org"