From owner-freebsd-questions@FreeBSD.ORG Wed Feb 3 18:21:56 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C796B1065679 for ; Wed, 3 Feb 2010 18:21:56 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from mail-pz0-f184.google.com (mail-pz0-f184.google.com [209.85.222.184]) by mx1.freebsd.org (Postfix) with ESMTP id 9C1388FC1D for ; Wed, 3 Feb 2010 18:21:56 +0000 (UTC) Received: by pzk14 with SMTP id 14so322395pzk.3 for ; Wed, 03 Feb 2010 10:21:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=QUtLUWKFaDF3m2g9y4ybasgnDwC4x5ZpeWHRCTBM2P4=; b=eGmNi4yTwIIVC5RfmCO29qCLr59PVKubTYh0UPK1xvLQi8sXAbGUaTuLRZEdn50Le8 Q6cXWB5p+KSZvUOxEzZ9eo4IrMHx8dku4lxOjpZM11QdqLH3h3E1tOUo8u9U3VjoYHsm zmHFXK+1cwaHcs73C7jAjgaUZifEplJvFHtmM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Jv8+rC/t9eEvuZCpm6+ulmmSRfOVyJuTwCPHzBxLdUv0wIbsM6cu/ddNwl1iHnjnrs PL6/pb78sC/iam52/sLSI6Btoz3FQb0+IUikyl3HMPHS3x33zFnadXC/Ui4A9gcyUa7p lrw03eBWlxtwTSq212VFC6l0t5Ilx7Z3g/1Ok= MIME-Version: 1.0 Received: by 10.142.6.13 with SMTP id 13mr1654864wff.39.1265221316074; Wed, 03 Feb 2010 10:21:56 -0800 (PST) In-Reply-To: <20100203185415.74e05d77.freebsd@edvax.de> References: <539c60b91002030935m31f66c6ft247f1231ad61656@mail.gmail.com> <20100203185415.74e05d77.freebsd@edvax.de> Date: Wed, 3 Feb 2010 11:21:56 -0700 Message-ID: <539c60b91002031021p4c08f382he33ace83cfa3466@mail.gmail.com> From: Steve Franks To: Polytropon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Mailing List Subject: Re: adding disk moves ad0 to ad4 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, 03 Feb 2010 18:21:56 -0000 On Wed, Feb 3, 2010 at 10:54 AM, Polytropon wrote: > On Wed, 3 Feb 2010 10:35:48 -0700, Steve Franks = wrote: >> Just curious, having read the handbook section talking about freebsd >> going straight to the hardware and skipping the bios for disk >> numbering, why then, if I stick a sata disk in 'sata0' on the >> motherboard, does it come up as ad0, but if I add a second disk in >> 'sata1' or 'pata0', on the next boot, I have no ad0, but ad4 and ad6? >> This seems to be the case with every mobo I've owned in the last 2 >> years from a variety of mfr's. =A0Is there a way around this? > > Maybe this is specific to your motherboard. As far as I > experienced, using (P)ATA and SATA - or not using it - > keeps the numbering intact, e. g. ad0 - ad3 is ATA, > ad4 - ad7 is SATA, no matter where a disk is actually > connected. > > It's possible that your BIOS does something strange in > representing one SATA, but no ATA disk as ad0, "the first > disk existing", as well as if an ATA disk would be present, > but no SATA disk. > > I can understand that this is annoying. > > > >> I don't >> care what it comes out as, as long as it stays put... > > There are labels or UFSIDs you can use to identify partitions > on a disk regardless of the device name they would come > out as. See "man glabel" and "man tunefs" for details. > > > >> Since I have >> the only fbsd system at work, I tend to format alot of funky drives >> for people, and it gets anoying having to swap fstab's every time... > > Labels can really help here: /etc/fstab will then contain > labels or UFSIDs instead of device names - and they don't > change when a disk is added or removed. > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > I knew there had to be a solution! Thanks! Steve