Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Feb 2010 22:26:57 -0800
From:      Matt Reimer <mattjreimer@gmail.com>
To:        Chris <behrnetworks@gmail.com>
Cc:        Scot Hetzel <swhetzel@gmail.com>, Pegasus Mc Cleaft <ken@mthelicon.com>, freebsd-current@freebsd.org
Subject:   Re: Seeing the dreaded "ZFS: i/o error - all block copies  unavailable" on 9.0-CURRENT
Message-ID:  <f383264b1002172226s9a76ae6sac55dca22dface77@mail.gmail.com>
In-Reply-To: <64aa03031002171949gdfbd99ci8eab7f29399cc011@mail.gmail.com>
References:  <64aa03031002161803h667734cal4d668b9eb9c0a1a8@mail.gmail.com> <790a9fff1002161842g17de8ecfvf2cfa8c77f03c32@mail.gmail.com> <64aa03031002161849s7b66b9e3l727aafd2afd3d596@mail.gmail.com> <201002171840.41088.ken@mthelicon.com> <790a9fff1002171303u4b40a90cr626ef856efee473b@mail.gmail.com> <64aa03031002171416s128ff196y92a5be5a6abadeb@mail.gmail.com> <64aa03031002171949gdfbd99ci8eab7f29399cc011@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 17, 2010 at 7:49 PM, Chris <behrnetworks@gmail.com> wrote:

> As a follow-up to this, I rebuilt world and kernel and updated my
> system to the latest 8.0-STABLE. I'm still seeing the problem and I
> can still get around it by choosing my hard drive from the F12 boot
> menu. I did notice that the bootloader now says it's ZFS enabled
> whereas it didn't while on 8.0-RELEASE. I also updated the bootcode
> with: "gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 adX"
> after installing world. No help there.
>
> It seems to me that there's a difference in the way the ZFS-enabled
> bootloader sees the drives that the BIOS reports as opposed to the
> non-ZFS-enabled bootloader.  Anyone have any ideas on that? I checked
> for any BIOS updates but it looks like I'm current. It sure would be
> nice to not have to select my hard drive each time.
>

Can you paste the exact error? Are you getting something like:

    error 1: lba 32
    error 1: lba 1

When I've seen the above sequence, it was due to a stack overflow (IIRC),
with the result that the loader would start a second time and barf out these
errors.

The "large number" in the error might give us a clue as to what's going on.
If the number is really large, it might be an indication that your BIOS
doesn't reliably read past a certain threshold. ZFS writes a sort of label
at the beginning and end of its drives; perhaps the loader is trying to read
the label at the end of the disk and is failing (I don't recall whether it
tries to read both labels).

Matt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f383264b1002172226s9a76ae6sac55dca22dface77>