From owner-freebsd-current@FreeBSD.ORG Fri Mar 19 02:18:11 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 CB1D0106566B for ; Fri, 19 Mar 2010 02:18:11 +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 586BB8FC0A for ; Fri, 19 Mar 2010 02:18:10 +0000 (UTC) Received: by bwz8 with SMTP id 8so2701452bwz.3 for ; Thu, 18 Mar 2010 19:18:10 -0700 (PDT) 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:content-type :content-transfer-encoding; bh=qnfltsou+UprBeF63uPStSj6GEsWyPqZC/XbhfV8jJg=; b=MGm7zIYW4KUtK3Tt1PfaVd1RJBn5lXpQyo5KboclbWXlHibvcgVeiQJJ62+K+xIStq xT9To/zJ6ukKQttLFb0ta552z7fPPuy3uF1odaFI79qGkPegAzBGITzmCgPx1/9m3J1Z SMbI/646u6lV1iSrjbgGEYAkZC1po+ip5GFOY= 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 :content-type:content-transfer-encoding; b=eegmHIzhuTn7OXO6Hu3sNl0MSJ6mzzgfU6fa9+2AklZS05kS/twFNcs6Dpdc0LsAjR 2Xi5XKvEVrmZn5q1Zru6XGXZ9KR1R8MC+exNhMtY9eOhxeor1vsqLLmbbguTsXwWMtcm x+NNjyQgRL62w1BoBoh77+LmNjpQMQBnIf36I= MIME-Version: 1.0 Received: by 10.204.156.204 with SMTP id y12mr465677bkw.82.1268965089647; Thu, 18 Mar 2010 19:18:09 -0700 (PDT) In-Reply-To: <64aa03031002252143k529096b1rf397254d5401d948@mail.gmail.com> References: <64aa03031002161803h667734cal4d668b9eb9c0a1a8@mail.gmail.com> <201002250806.01217.jhb@freebsd.org> <64aa03031002250958m470982c5g59735f9cef88af78@mail.gmail.com> <201002251308.36002.jhb@freebsd.org> <64aa03031002252143k529096b1rf397254d5401d948@mail.gmail.com> Date: Thu, 18 Mar 2010 22:18:08 -0400 Message-ID: <64aa03031003181918p634ea1dcp93599cd2cbd71a39@mail.gmail.com> From: Chris To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 Mar 2010 02:18:12 -0000 I guess we can officially declare this thread dead? On Fri, Feb 26, 2010 at 1:43 AM, Chris wrote: > On Thu, Feb 25, 2010 at 1:08 PM, John Baldwin wrote: >> On Thursday 25 February 2010 12:58:13 pm Chris wrote: >>> On Thu, Feb 25, 2010 at 8:06 AM, John Baldwin wrote: >>> > On Wednesday 24 February 2010 10:12:25 pm Chris wrote: >>> >> So it sounds like somehow my system is trying to use the old boot2 >>> >> method when I don't hit F12. I'm guessing the difference is due to h= ow >>> >> the hard drive is getting presented to the boot loader by the BIOS. >>> >> How can I get rid of the legacy boot system and use only the ZFS >>> >> bootloader? >>> > >>> > Does F12 enable PXE booting or some such? >>> >>> The only options I have when I press F12 are to either boot from my >>> hard drive or to boot from my optical drive. Is there >>> any way to more verbosely see what is happening at the bootloader level= ? >> >> No. =A0So it sounds like F12 pops up some sort of boot menu, and that in= the >> broken case you just let the machine boot off of the disk normally? > > Right. Upon powering on, to get the system to boot normally, I hit the > F12 key which brings up a box that lets me choose either my hard disk > or my optical drive to boot. When I do not hit F12, I get the LBA > errors and the "ZFS: i/o error - all block copies unavailable" error > shown in previous posts to this thread. If I boot into the non-F12 > broken state and leave the system alone, it appears to try and boot > twice and gets the same LBA errors and the same ZFS error. > > Again, if I install FreeBSD off an installation CD and use sysinstall > to install a typical UFS-based system it boots without any trouble at > all, F12 or not, leading me to believe that there's some sort of > difference between the plain bootloader and the ZFS-enabled bootloader > with respect to the way they interact with the BIOS. > > Another oddity I noticed is that if I change the SATA mode in the BIOS > to "IDE Native" mode, the hard drive activity light stays on, even > when the system is booted and is sitting idle. If I change it to > "AHCI", I do not see this. I doubt this has any relation to ZFS, but > it was just an interesting observation. >