Date: Thu, 18 Feb 2010 22:21:11 -0500 From: Chris <behrnetworks@gmail.com> To: Matt Reimer <mattjreimer@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: <64aa03031002181921m2d00966cx6a3bb2c6e761970d@mail.gmail.com> In-Reply-To: <f383264b1002180950t51ddb421i51b36886e7da6295@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> <f383264b1002172226s9a76ae6sac55dca22dface77@mail.gmail.com> <64aa03031002180531n5e07e3bcj455ba09bdf5e293e@mail.gmail.com> <f383264b1002180950t51ddb421i51b36886e7da6295@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I think you're probably right about this being a BIOS problem.
> Does the gptzfsboot 'status' command show the same output when you run it
> with and without the F12 workaround? Here's what I see from FreeBSD and f=
rom
> gptzfsboot:
> [root ~]# zpool status
> =A0=A0pool: glamdring
> =A0state: ONLINE
> =A0scrub: none requested
> config:
>
> =A0=A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 STATE =A0 =A0 =
READ WRITE CKSUM
> =A0=A0 =A0 =A0 =A0glamdring =A0 =A0 =A0 =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0=
0 =A0 =A0 0 =A0 =A0 0
> =A0=A0 =A0 =A0 =A0 =A0raidz2 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ONLINE =A0 =A0 =
=A0 0 =A0 =A0 0 =A0 =A0 0
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0 =A0ONLINE =A0 =A0 =A0 0 =A0 =
=A0 0 =A0 =A0 0
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-1 =A0ONLINE =A0 =A0 =A0 0 =A0 =
=A0 0 =A0 =A0 0
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-2 =A0ONLINE =A0 =A0 =A0 0 =A0 =
=A0 0 =A0 =A0 0
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-3 =A0ONLINE =A0 =A0 =A0 0 =A0 =
=A0 0 =A0 =A0 0
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-4 =A0ONLINE =A0 =A0 =A0 0 =A0 =
=A0 0 =A0 =A0 0
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-5 =A0ONLINE =A0 =A0 =A0 0 =A0 =
=A0 0 =A0 =A0 0
>
> errors: No known data errors
> ...
>
> /boot.config: -Dh
> Default: glamdring:/boot/zfsloader
> boot: status =A0pool: glamdring
> config:
>
> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0STATE
> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 glamdring =A0 =A0 ONLINE
> =A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0raidz2 =A0 =A0 ONLINE
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-0 =A0 =A0 ONLINE
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-1 =A0 =A0 ONLINE
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-2 =A0 =A0 ONLINE
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-3 =A0 =A0 ONLINE
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-4 =A0 =A0 ONLINE
> =A0=A0 =A0 =A0 =A0 =A0 =A0label/glamdring-5 =A0 =A0 ONLINE
> Matt
I'm seeing some difference in the bootloader output between using the
F12 workaround or not:
F12 workaround mode:
FreeBSD/i386 boot
Default: zroot:/boot/zfsloader
boot: status
config:
NAME STATE
zroot ONLINE
gpt/disk0 ONLINE
No F12 key pressed:
FreeBSD/i386 boot
Default: zroot:/boot/kernel/kernel
config:
NAME STATE
zroot ONLINE
gpt/disk0 ONLINE
What's up with the differences between the Default boot setting?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64aa03031002181921m2d00966cx6a3bb2c6e761970d>