From owner-freebsd-current@FreeBSD.ORG Fri Feb 19 03:21:13 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 042D11065696 for ; Fri, 19 Feb 2010 03:21:13 +0000 (UTC) (envelope-from behrnetworks@gmail.com) Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mx1.freebsd.org (Postfix) with ESMTP id 826648FC14 for ; Fri, 19 Feb 2010 03:21:12 +0000 (UTC) Received: by bwz8 with SMTP id 8so929886bwz.3 for ; Thu, 18 Feb 2010 19:21:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FPRA1+jEv1eeOORQnF1GAkArM/b4brRgSQskyTTrewU=; b=VuBGpTGrNrG5GVR9Mx12Mfh+NEowrGcHRlVzbVde51BII3JNKUNS6u6NCAsMJIO2kA BSNUi6aByH/KoqPBvc9m+uG79dBpzb0XdxZP135YFIgEiwUfvgxxpLlnkaE+pZBrIGjL 0WRymyIXXXv3Fwp01IXhXW1h3Obh82O4vn+qs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=V5CrJZicEDFnhH7U+7Pn9TyTITJn7cEcDwaegOxxCS3LLLKgMA6BH+pURuD9yaCqMh XM7zdUvhtrq2QpnPXZ9zEUcjLsc5sh/PO5DHfWzOr83E0EGOOIj3gtQtijr1bYcOaxtb i0Axnf/mlu55K4DBucNRKzWdIZV8lefSvdHiY= MIME-Version: 1.0 Received: by 10.204.48.202 with SMTP id s10mr11707bkf.34.1266549671334; Thu, 18 Feb 2010 19:21:11 -0800 (PST) In-Reply-To: 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> <64aa03031002180531n5e07e3bcj455ba09bdf5e293e@mail.gmail.com> Date: Thu, 18 Feb 2010 22:21:11 -0500 Message-ID: <64aa03031002181921m2d00966cx6a3bb2c6e761970d@mail.gmail.com> From: Chris To: Matt Reimer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Scot Hetzel , Pegasus Mc Cleaft , freebsd-current@freebsd.org Subject: Re: Seeing the dreaded "ZFS: i/o error - all block copies unavailable" on 9.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2010 03:21:13 -0000 > 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?