ata controller problem

Gerhard Schmidt schmidt at
Sat Oct 27 08:24:59 UTC 2012

Am 26.10.2012 18:33, schrieb Jeremy Chadwick:
> Regarding this:
> No no NO *NO*!
> I wish people would stop recommending this utter garbage.  There is
> absolutely no justification behind using the highly convoluted labelling
> mechanisms at multiple layers within FreeBSD.  There are 3 (possibly 4)
> different "label" mechanisms which do nothing but confuse the user, or
> cause other oddities/complexities.  Good grief, there is so much hard
> evidence on the mailing lists over the past 5 (maybe even 7?) years
> talking about the utter mess that is filesystem/device/geom/blahblah
> labels that to recommend this is borderline insane.
> The proper way to solve this problem is to user /boot/loader.conf
> tie-downs to assign each disk to each individual controllers' device
> number (e.g. ada0 --> scbus0 --> ahcich0, or whatever you want).  Please
> note I said ahcichX, not ahciX.  Different things.
> I have helped others in the past do this; Randy Bush is one such person.
> Taken directly from my /boot/loader.conf with a single SATA controller,
> but obviously this can be adjusted to whatever you want.
> # "Wire down" device names (ada[0-5]) to each individual port
> # on the SATA/AHCI controller.  This ensures that if we reboot
> # with a disk missing, the device names stay the same, and stay
> # attached to the same SATA/AHCI controller.
> #
> #
> See CAM(4) man page (read it, don't skim!) for full details.  Just
> please for the love of god do not use labels to solve this.
Sorry this doesn't work because the numbering of the ahci change with
the occupancy of the Hot-Swap Bays.

And that is my Problem. This i have tried first.

Any idea how i can fix which controller gets which number.


Gerhard Schmidt       | E-Mail und JabberID:
TU-München            | schmidt at
WWW & Online Services |
Tel: 089/289-25270    |
Fax: 089/289-25257    | PGP-Publickey auf Anfrage

More information about the freebsd-questions mailing list