From owner-freebsd-fs@FreeBSD.ORG Tue May 11 19:55:06 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71A05106566B for ; Tue, 11 May 2010 19:55:06 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 2A09C8FC17 for ; Tue, 11 May 2010 19:55:05 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OBvXk-0002ps-6z for freebsd-fs@freebsd.org; Tue, 11 May 2010 21:55:04 +0200 Received: from 142-076-ppp.kubtelecom.ru ([142-076-ppp.kubtelecom.ru]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 May 2010 21:55:04 +0200 Received: from yuri.pankov by 142-076-ppp.kubtelecom.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 May 2010 21:55:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org connect(): No such file or directory From: Yuri Pankov Date: Tue, 11 May 2010 19:44:46 +0000 (UTC) Lines: 20 Message-ID: References: <4BE616D6.7000901@jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 213.132.76.142 (Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.3) Gecko/20100511 Firefox/3.6.3) Subject: Re: ZFS doesn't mountroot: Unable to open /dev/ad4p3 for writing (error=1). X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2010 19:55:06 -0000 James R. Van Artsdalen jrv.org> writes: > > FreeBSD 9.0-svn207742 #0: Sat May 8 17:13:06 UTC 2010 > root clunk.housenet.jrv:/usr/obj/usr/src/sys/GENERIC amd64 > > I am no longer able to boot my newly-created ZFS pools in a VirtualBox > VM: the "Unable to open /dev/ad4p3 for writing" error shown below > prevents the pool from being imported even though it is found. > > When the pool was created it was on disk ad6, but it is now booting on > ad4: zpool.cache contains wrong disk names so the kernel finds the pool > member(s) by guid, not name. Same here on recent -CURRENT. I recently needed to disable ahci(4) driver (pool was created on ada0p3), and got the same error about ad4p3 (device name without ahci driver). Yuri