From owner-freebsd-questions@FreeBSD.ORG Wed Mar 28 21:04:51 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A0FF16A400 for ; Wed, 28 Mar 2007 21:04:51 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id B057E13C457 for ; Wed, 28 Mar 2007 21:04:50 +0000 (UTC) (envelope-from illoai@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so3450678nfc for ; Wed, 28 Mar 2007 14:04:49 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Atno5nU2nBSlAjlyuTAp5J7VGeXUcrIMKuBGazCpSZG0RDewTbDPxQx4xnraf4BWjLwjQVZ+pWnzaZ0juppnLCgYkjkI/5GYLuz0obkKyB+Yjt61U0eI5V9GvCc9y6XotTJrylqnWkrs1I48pSigED6qpM8zNc3766N7mVmLEpY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XhEPGc7Ru8OGe8i49xug3GocXFEUmSut8aZDjDIfePpgPKzsJ9vEuotUt3hRgfMpXsr+kSQ/+l72nqHSy+spk5YrBa4ruIQBx29hSFYipeEGGkX5IDqFjWUSShES/bt1MGwIr+PqzPuZaf8eCBWKfZqdA4RqwS7oyoGJPWCq+/I= Received: by 10.82.107.15 with SMTP id f15mr19747088buc.1175115889262; Wed, 28 Mar 2007 14:04:49 -0700 (PDT) Received: by 10.82.175.6 with HTTP; Wed, 28 Mar 2007 14:04:49 -0700 (PDT) Message-ID: Date: Wed, 28 Mar 2007 16:04:49 -0500 From: "illoai@gmail.com" To: "Marc G. Fournier" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-questions@freebsd.org Subject: Re: Why is 'disklabel'ng a new drive so difficult? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2007 21:04:51 -0000 On 28/03/07, Marc G. Fournier 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. The drives which DO return the errors have partitions newfs-ed with a non-default blocksize (-b 8192). What effect (or "impact" if you learnt English in a Zeppelin over Italy in 1916) that may have is beyond me. -- --