Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Oct 2013 07:23:28 +0200
From:      Polytropon <>
To:        Casey Scott <>
Subject:   Re: ATA drive ID differences between kernels
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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. :-)

> 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

I could imagine you're experiencing something similar...

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>