Date: Sat, 4 Jun 2011 15:40:52 +0200 (CEST) From: Michael Reifenberger <mike@reifenberger.com> To: Gavin Atkinson <gavin@FreeBSD.org> Cc: Garrett Cooper <yanegomi@gmail.com>, pjd@FreeBSD.org, FreeBSD-Current <current@FreeBSD.org> Subject: Re: mount root from zfs fails under current with "error 6" Message-ID: <alpine.BSF.2.00.1106041533090.3119@gw.reifenberger.com> In-Reply-To: <1307116512.60345.8.camel@buffy.york.ac.uk> References: <alpine.BSF.2.00.1105301833270.3134@gw.reifenberger.com> <BANLkTinM5YvZ-91SJN6EFi5WwF5hQDtojg@mail.gmail.com> <alpine.BSF.2.00.1105310959440.3206@gw.reifenberger.com> <alpine.BSF.2.00.1105311925330.3376@gw.reifenberger.com> <1307116512.60345.8.camel@buffy.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Jun 2011, Gavin Atkinson wrote: ... >> maybe I found something: >> After setting vfs.zfs.debug=1 I got two new verbose bootlogs: >> http://people.freebsd.org/~mr/boot_fail2.txt >> http://people.freebsd.org/~mr/boot_success2.txt >> >> As you can see, in the failing case ZFS tries to attach to ada[0123] >> whereas in the succeeding case ZFS attaches to ada[0123]p3 (which are the >> correct devices) > > Can you try setting kern.geom.part.check_integrity=0 ? > Preparing a new r222654 kernel and booting with kern.geom.part.check_integrity=0 didn't cure anything. See http://people.freebsd.org/~mr/boot_3.txt for a "boot -v" using set kern.geom.label.debug=1 additionaly But reverting /sys/geom to r221381 allows to boot. See http://people.freebsd.org/~mr/boot_4.txt for a "boot -s" using set vfs.zfs.debug=1 set kern.geom.debugflags=4 set kern.geom.label.debug=1 additionaly. So the problem seems to be related to the recent geom changes... Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1106041533090.3119>