From owner-freebsd-stable@FreeBSD.ORG Fri Jan 15 23:29:25 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99E03106566B for ; Fri, 15 Jan 2010 23:29:25 +0000 (UTC) (envelope-from prvs=0631c28db0=ob@gruft.de) Received: from main.mx.e-gitt.net (service.rules.org [IPv6:2001:1560:2342::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2703B8FC13 for ; Fri, 15 Jan 2010 23:29:24 +0000 (UTC) Received: from ob by main.mx.e-gitt.net with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1NVvbX-000DHe-9A for freebsd-stable@freebsd.org; Sat, 16 Jan 2010 00:29:23 +0100 Date: Sat, 16 Jan 2010 00:29:23 +0100 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Message-ID: <20100115232922.GM45688@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org References: <7ab0356e1001151213y5536d4cdi1d1759ce28ad546a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7ab0356e1001151213y5536d4cdi1d1759ce28ad546a@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: Oliver Brandmueller Subject: Re: AHCI and ZFS: root mount error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2010 23:29:25 -0000 Hi, On Fri, Jan 15, 2010 at 09:13:39PM +0100, Romain Garbage wrote: > After setting ahci_load="YES" in /boot/loader.conf, I get a root mount error. > ahci seems to attach to disk correctly (I get ada0 messages with no error) > > Without ahci_load="YES", system boots fine, with ata module attaching to disk. > > I have a full zfs system, set up following wiki instructions: > http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition > (MBR scheme, ZFS in a FreeBSD slice, together with a swap partition) > > I'm using a GENERIC kernel, RELENG_8 branch. > > My /boot/loader.conf: > zfs_load="YES" > vfs.root.mountfrom="zfs:zroot" > nvidia_load="YES" > snd_hda_load="YES" > tmpfs_load="YES" > coretemp_load="YES" 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. - Olli -- | Oliver Brandmueller http://sysadm.in/ ob@sysadm.in | | Ich bin das Internet. Sowahr ich Gott helfe. |