Date: Wed, 12 May 2010 03:00:10 +0400 From: Yuri Pankov <yuri.pankov@gmail.com> To: Pawel Jakub Dawidek <pjd@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS doesn't mountroot: Unable to open /dev/ad4p3 for writing (error=1). Message-ID: <20100511230010.GA1608@darklight.org.ru> In-Reply-To: <20100511223009.GA3044@garage.freebsd.pl> References: <4BE616D6.7000901@jrv.org> <loom.20100511T213336-358@post.gmane.org> <20100511223009.GA3044@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 12, 2010 at 12:30:09AM +0200, Pawel Jakub Dawidek wrote: > On Tue, May 11, 2010 at 07:44:46PM +0000, Yuri Pankov wrote: > > James R. Van Artsdalen <james-freebsd-fs2 <at> jrv.org> writes: > > > > > > > > FreeBSD 9.0-svn207742 #0: Sat May 8 17:13:06 UTC 2010 > > > root <at> 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. > > <snip> > > > > 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). > > It should be worked around in r207936. Could you guys try it? > > -- > Pawel Jakub Dawidek http://www.wheelsystems.com > pjd@FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! Worked like a charm, successfully booted from ad4p3 (no ahci and ATA_CAM). Thanks, Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100511230010.GA1608>