From owner-freebsd-questions@FreeBSD.ORG Sat Oct 19 03:36:25 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 14A73B34 for ; Sat, 19 Oct 2013 03:36:25 +0000 (UTC) (envelope-from casey@phantombsd.org) Received: from scottmail.org (scottmail.org [209.206.250.76]) by mx1.freebsd.org (Postfix) with ESMTP id DCB8F20B6 for ; Sat, 19 Oct 2013 03:36:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by scottmail.org (Postfix) with ESMTP id 527D024A427; Fri, 18 Oct 2013 20:36:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at scottmail.org Received: from scottmail.org ([127.0.0.1]) by localhost (scottmail.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nvdoRaQXX4v; Fri, 18 Oct 2013 20:36:17 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by scottmail.org (Postfix) with ESMTP id 8114924A452; Fri, 18 Oct 2013 20:36:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at scottmail.org Received: from scottmail.org ([127.0.0.1]) by localhost (scottmail.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Pbjc4G0BPFcf; Fri, 18 Oct 2013 20:36:16 -0700 (PDT) Received: from scottmail.org (bearcat.phantombsd.org [192.168.1.20]) by scottmail.org (Postfix) with ESMTP id 998DC24A427; Fri, 18 Oct 2013 20:36:16 -0700 (PDT) Date: Fri, 18 Oct 2013 20:36:16 -0700 (PDT) From: Casey Scott To: Polytropon Message-ID: <640848482.387.1382153776544.JavaMail.root@phantombsd.org> In-Reply-To: <20131018072328.6267d3a8.freebsd@edvax.de> References: <1712475983.350.1382053431300.JavaMail.root@phantombsd.org> <251840039.356.1382053725512.JavaMail.root@phantombsd.org> <20131018072328.6267d3a8.freebsd@edvax.de> Subject: Re: ATA drive ID differences between kernels MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.1.6] X-Mailer: Zimbra 8.0.2_GA_5569 (ZimbraWebClient - GC30 (Win)/8.0.2_GA_5569) Thread-Topic: ATA drive ID differences between kernels Thread-Index: U4L7pD6nOnJtySs2KyP4PoZ/PKMDqQ== Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Casey Scott List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Oct 2013 03:36:25 -0000 Labels solved my problem. Thanks! I also tried removing ata & atadisk, but the drives weren't detected. For posterity's sake, following these 2 links provided the info I needed for labeling: http://www5.us.freebsd.org/doc/handbook/geom-glabel.html http://www.wonkity.com/~wblock/docs/html/disksetup.html Thanks again. -Casey ----- Original Message ----- > On Thu, 17 Oct 2013 16:48:45 -0700 (PDT), Casey Scott wrote: > > I recently installed 9.2 on a server that was running 8.3. > > The problem I'm facing is that the GENERIC and my custom > > kernel ID drives differently: > > > > e.g. GENERIC CUSTOM > > drive 1 ada1 ada6 > > drive 2 ada2 ada7 > > drive 3 ada3 ada8 > > > > > > The result of which is a error code 19 at mountroot. > > This is a _perfect_ situation to start using labels. :-) > > http://www.wonkity.com/~wblock/docs/html/disksetup.html > > > > > I've been through UPDATING, NOTES, Google, forums, etc. and > > can't determine what's missing from my custom kernel. Custom > > kernel config below: > > Just a guess: The kernel enumerates the devices as they come > up (presented by "the hardware"). There are "reserved number > ranges" according to what the storage controller _can_ offer, > even if it's not the case. > > Example from my home system: > > ad0 = ATA, primary master > ad1 = ATA, primary slave > ad2 = ATA, secondary master > ad3 = ATA, secondary slave > ad4 = SATA 1st port > ad6 = SATA 2nd port > > If I'd remove the support for the (ordinary) ata devices, > it would maybe be possible that the numbering scheme changes. > I'm not sure in how far AHCI (because of SATA) fits in here. > The SATA drives could then be ada0 and ada1, or ada4 and ada6 > respectively. > > I could imagine you're experiencing something similar... > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... >