From owner-freebsd-questions@FreeBSD.ORG Fri Oct 18 05:23:36 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 CE90F928 for ; Fri, 18 Oct 2013 05:23:36 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 92FEF2D0E for ; Fri, 18 Oct 2013 05:23:36 +0000 (UTC) Received: from r56.edvax.de (port-92-195-74-65.dynamic.qsc.de [92.195.74.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 1DE033C6B5; Fri, 18 Oct 2013 07:23:35 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id r9I5NS8k002014; Fri, 18 Oct 2013 07:23:28 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 18 Oct 2013 07:23:28 +0200 From: Polytropon To: Casey Scott Subject: Re: ATA drive ID differences between kernels Message-Id: <20131018072328.6267d3a8.freebsd@edvax.de> In-Reply-To: <251840039.356.1382053725512.JavaMail.root@phantombsd.org> References: <1712475983.350.1382053431300.JavaMail.root@phantombsd.org> <251840039.356.1382053725512.JavaMail.root@phantombsd.org> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Oct 2013 05:23:36 -0000 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, ...