From owner-freebsd-questions@FreeBSD.ORG Wed Sep 25 06:45:31 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3BD8A25B for ; Wed, 25 Sep 2013 06:45:31 +0000 (UTC) (envelope-from terje@elde.net) Received: from keepquiet.net (keepquiet.net [IPv6:2a01:4f8:130:84c1::deaf:babe]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F05A72B95 for ; Wed, 25 Sep 2013 06:45:30 +0000 (UTC) Received: from [10.130.11.108] (cm-84.210.76.250.getinternet.no [84.210.76.250]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: terje@elde.net) by keepquiet.net (Postfix) with ESMTPSA id ADC042E408; Wed, 25 Sep 2013 08:45:20 +0200 (CEST) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: X-Mailer: iPhone Mail (10B329) From: Terje Elde Subject: Re: FreeBSD 8.4 Boot failure Date: Wed, 25 Sep 2013 08:45:17 +0200 To: Tyler Sweet Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2013 06:45:31 -0000 On 25. sep. 2013, at 06:59, Tyler Sweet wrote: > I tried reinstalling the boot blocks from both > the fixit live filesystem and also mounting zroot and using the files > there in case they were different. Disclaimer: I haven't gotten (enough) morning-coffee yet, but... Disclaimer 2: at times tracking how zfs-booting is done in the different ver= sions can be a bit tricky. This is a moving target, and I've lost track of t= he 8-branch.=20 That said, assuming you have the correct bootcode (gptzfsboot), here's what m= ight have happened: You installed 8.2, with a loader supporting zfs. Then you upgraded your /boo= t-stuffs, and bootcode on disk (correctly), but got left with a loader witho= ut zfs support. Then tried to upgrade the bootcode, but you're still left wi= th a loader not supporting zfs.=20 If I recall correctly, then the zfs-bootcode for 9+ will use "zfsloader" (su= pporting zfs and built by default), while earlier versions depend on "loader= " with zfs support (built without by default).=20 If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.conf an= d rebuild/reinstall it, or install /boot/loader from the fixit (if it has zf= s support in 8.4).=20 That's my first thought at least... If that doesn't fix it (remember backup= s of any files you replace or upgrade), it'd be interesting to see the outpu= t of: ls -l /boot/*loader /boot/*boot On the /boot you're using. Anything that didn't get built or installed? Also, did you snapshot your zfs before upgrading? Could be a working /boot/l= oader there, which might be the easiest way to get the system up, before reb= uilding with ZFS-capable loader... if I'm right, which isn't a given (ref di= sclaimers).=20 Terje