Date: Tue, 10 Oct 2006 11:10:52 +1000 From: Antony Mawer <fbsd-questions@mawer.org> To: Juha Saarinen <juhasaarinen@gmail.com> Cc: FreeBSD questions <freebsd-questions@freebsd.org> Subject: Re: AHCI support in 6.1-RELEASE? Message-ID: <452AF31C.4080302@mawer.org> In-Reply-To: <b34be8420610091802y32acf30ds66fde8c95f4201ee@mail.gmail.com> References: <b34be8420610091706t3f5bf82cn13075f3f69c734f9@mail.gmail.com> <b34be8420610091718q5541a124v1195f243ec12c06a@mail.gmail.com> <452AEA98.2030409@mawer.org> <b34be8420610091802y32acf30ds66fde8c95f4201ee@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/10/2006 11:02 AM, Juha Saarinen wrote:
> On 10/10/06, Antony Mawer <fbsd-questions@mawer.org> wrote:
>> Most likely this renumbers the drivers, so you go from your hard drive
>> showing as eg. ad0 to ad4. You will need to edit /etc/fstab as
>> appropriate to match what the drive is showing up as after changing to
>> AHCI mode.
>
> Yep... exactly like that - from ad0 to ad4. Worked perfectly. Thank
> you very much, it didn't occur to me that there would be driver
> renumbering when switching to AHCI.
>
> Oddly enough, even though the drive is connected to SATA port 0 on the
> motherboard, it shows up as being on ATA channel 2, Master. According
> to atacontrol, I have six ATA channels on the box, 0-5. Doesn't seem
> quite logical that the driver should be renumbered as ad4, but... if
> it works, I don't care.
Usually I find that ad0/ad1 = primary IDE (master/slave), ad2/3 =
secondary IDE (master/slave), and then the SATA connectors pick up from
ad4 onwards...
The SATA ports seem to be numbered in increments of 2, presumably
because every SATA port is a "master", so the usual "slave" position is
unused... ie:
SATA 0 -> ad4
SATA 1 -> ad6
SATA 2 -> ad8
SATA 3 -> ad10
Presumably turning off ATA_STATIC_ID would just number them in the
sequential order (ad0, ad1, ad2, ...) based on the devices that are
actually connected... but this can mess things up when you connect
additional drives at a later date somewhere in the middle of the chain!
I have a patch I wrote for sysinstall somewhere that allows you to do
disk=auto in an install.cfg, and it picks the first device it comes
across (eg. if ad4 is the first IDE disk, it picks it over ad10)...
we've found this very handy for installation/deployment scenarios that
are automated via install.cfg but may have different disk configurations...
If there's enough interest I might look at submitting it for inclusion...
Cheers
Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?452AF31C.4080302>