From owner-freebsd-current@FreeBSD.ORG Wed Feb 17 18:19:01 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 41E621065670 for ; Wed, 17 Feb 2010 18:19:01 +0000 (UTC) (envelope-from behrnetworks@gmail.com) Received: from mail-fx0-f226.google.com (mail-fx0-f226.google.com [209.85.220.226]) by mx1.freebsd.org (Postfix) with ESMTP id BF9E08FC1B for ; Wed, 17 Feb 2010 18:19:00 +0000 (UTC) Received: by fxm26 with SMTP id 26so7519160fxm.13 for ; Wed, 17 Feb 2010 10:18:59 -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=cncJMVfkavo62m6EVnePOKQCwqh56mMIr0qU3H0Q7Mg=; b=TAo9WxhsFhYayaihfNcTqdmTIwqWG7i5mHOU3Faw6aWIAekHRgf5AldwGVAuYZDPiD z0yXpl5FjSyw7E39yndQhZA40iW/WhOdghojcuo6toQ6kTjWyOLQESXSJ+VArsBmWVXt qzsjtLlH4Xan7uvi+bTc0v0oYJbR9pkkl0myM= 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=tu/Ywgehv6RiVQZUkMd7NjEdCSNYgeIBC10AG9D7rVBmBAEoJZZkdA0x0E587g0M1h UXKztbYOmoGBd5DbzOi08jvWZWvExujsfhutp7TAhK1os/KNqBeM+yB0bPeM7byMKvlM vuJhyN7/q4O3GpheKvLZ/GA35sUewxdbTZ/20= MIME-Version: 1.0 Received: by 10.204.0.84 with SMTP id 20mr5567244bka.5.1266430734611; Wed, 17 Feb 2010 10:18:54 -0800 (PST) In-Reply-To: References: <64aa03031002161803h667734cal4d668b9eb9c0a1a8@mail.gmail.com> <64aa03031002161821n266a0ef1jd8d8ec4cac1c9635@mail.gmail.com> <790a9fff1002161842m5d49515dh45bb942e30285b3b@mail.gmail.com> <790a9fff1002161842g17de8ecfvf2cfa8c77f03c32@mail.gmail.com> <64aa03031002161849s7b66b9e3l727aafd2afd3d596@mail.gmail.com> <64aa03031002161851o621f3bc8r31ba438e3fb906c0@mail.gmail.com> <4B7B644F.5050404@polands.org> <64aa03031002170528l7acf05bev4d75685187c1eb46@mail.gmail.com> <64aa03031002170746p49716f76gd87987422a190a02@mail.gmail.com> Date: Wed, 17 Feb 2010 13:18:54 -0500 Message-ID: <64aa03031002171018h2f7ecdc2l43dbb8c4cea8c6a8@mail.gmail.com> From: Chris To: Matt Reimer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Doug Poland , 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: Wed, 17 Feb 2010 18:19:01 -0000 Shouldn't those bug fixes have been included in CURRENT? If so, my original post shows the problems there. I've also tried using the 8.0-STABLE snapshot dvd1 and got the same errors I got when using CURRENT. Again, not sure why this worked on my desktop box and is failing on the laptop. I'll try copying over gptzfsboot and zfsloader from my 8.0-STABLE machine. On Wed, Feb 17, 2010 at 1:15 PM, Matt Reimer wrote: > On Wed, Feb 17, 2010 at 7:46 AM, Chris wrote: >> >> Ok, went back to my 8.0-RELEASE memstick image and after playing with >> the GPT settings a little and dd'ing all zeros to the disk first, I >> get a little farther this time. I'm seeing the following: >> >> ----------------------------- >> BTX loader 1.00 =A0 BTX version is 1.02 >> Consoles: internal video/keyboard >> BIOS drive C: is disk0 >> BIOS 631kB/1832448kB available memory >> >> FreeBSD/i386 bootstrap loader, Revision 1.0 >> (root@, Wed Feb 17 10:27:40 UTC 2010) >> Loading /boot/defaults/loader.conf >> /boot/kernel/kernel text=3D0x8924d8 >> ----------------------------- >> >> And that's as far as it gets. Per the handbook, that appears to be >> stuck somewhere between boot2 and /boot/loader. To me, it looks like >> it's having a problem loading the kernel. As far as my suspicion of >> the BIOS not correctly reporting the drives, it looks to me like the >> bootloader is seeing them so maybe that can be ruled out. I'm glad to >> see it get farther this time but this is still weird. >> >> Any ideas on this one? > > IIRC the 8.0-RELEASE gptzfsboot/loader lacked some bugfixes. Try using > gptzfsboot and zfsloader from -STABLE. > Matt