AHCI and ZFS: root mount error

[Volodymyr Kostyrko]

On Sat, 16 Jan 2010 00:29:23 +0100
Oliver Brandmueller <ob at e-Gitt.NET> wrote:

> Check with "zpool status" if your zpool refers to diskslices like 
> "ad0s1". I use gpt have setup the ZFS mirror to refer to gptids:
> 
>   pool: silver
>  state: ONLINE
>  scrub: none requested
> config:
> 
>         NAME                                            STATE     READ WRITE CKSUM
>         silver                                          ONLINE       0     0     0
>           mirror                                        ONLINE       0     0     0
>             gptid/9e68d234-f306-11de-a0c4-0002b3b6e838  ONLINE       0     0     0
>             gptid/a025b88c-f306-11de-a0c4-0002b3b6e838  ONLINE       0     0     0
> 
> With that kind of configuration I can switch back and forth between 
> using ATA_CAM or using traditional ATA drivers. Since you're not using 
> GPT I gues you can use geom labels to do more or less the same thing.
> 
> In short: use labels, nut device names. Saves headaches in many cases.

ZFS actually can find disks without any glabel help. I have one server which I have moved recently to ahci and nothing changes for me. ZFS silently accepted new provider names and continue working as usual.

-- 
Sphinx of black quartz judge my vow.