From owner-freebsd-questions@FreeBSD.ORG Wed Sep 25 08:54:50 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 D97B31CC for ; Wed, 25 Sep 2013 08:54:50 +0000 (UTC) (envelope-from tyler@tsweet.net) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 75D5C236A for ; Wed, 25 Sep 2013 08:54:48 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id x12so5931968wgg.32 for ; Wed, 25 Sep 2013 01:54:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=gLt97982Kgq4LoeK2wuvX5TwtQsghHjj+XSDVNSfY0E=; b=C8ciXtND9hpsgHcMzWtZKfgD89TkPvIFpLe7mS1Nv3MkvxP5meX0+mHvFkIgMONEJb 4/bfSZwotMkSM8qBMVuoLtoUOcK56O4SQBPJQ0jo9SzrW8Ys0wPG9gODksO3Zx1scQfg oPZw0K0LDFLmdd8N0ecNb8C5Txpgo+gdTl2khvwRfXIQgSgjiTf5ny5oxSzLaKnLIIbd k/XUFikaX0m1ddBkBxbGscZdsbw974jm3AajtAigGGOxPR/TKBkqbEMxKWzFI8Y1927h jB35v88bFniCmMC57KCzB7k0x2zMmBylGTWVdqimzSqys+yjUt9P2Vcp+XZKC9ckAy2n Hovg== X-Gm-Message-State: ALoCoQlaK6i4OkwJaRNYzz251QYQDdhB759c9lpNaWyyc6fvOEtvg0Py52emc8UWuOzFXBckE0oX X-Received: by 10.194.11.67 with SMTP id o3mr26771712wjb.0.1380098851681; Wed, 25 Sep 2013 01:47:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.12.194 with HTTP; Wed, 25 Sep 2013 01:46:51 -0700 (PDT) X-Originating-IP: [67.212.118.60] In-Reply-To: References: From: Tyler Sweet Date: Wed, 25 Sep 2013 03:46:51 -0500 Message-ID: Subject: Re: FreeBSD 8.4 Boot failure To: Terje Elde Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 08:54:51 -0000 Luckily, in this case, I had set a cron job long, long ago to do daily snapshots. So I have a snapshot from before the upgrade - There are indeed two different loaders. The newer one matches "zfs" when grepped, the older one does not... But, since it was working before, I restored the older loader and tried to boot again. No dice - it still sticks at that screen where all I see is "/" in the upper left. I also tried putting the older zfsboot and zfsloader back in place (with the old loader) to try and get a different error - still no dice. I'm still stuck wondering if that screen is from FreeBSD attempting to boot, or from the BIOS - but nothing changed for booting, as far as I know. I'll poke through the BIOS more tomorrow as well to see if some option got reset during a power-off. I'll get a more thorough look at what all changed in /boot tomorrow too, and get a list of all the files. It's almost 4am here and I have to work tomorrow :) (well, today I suppose). I'll also check to see if I can find anything about if zfs boot works differently in 8.4 vs 8.3 and older, as I may not have rebooted after the final "freebsd-update install" command (I *think* I did, but my memory gets fuzzy). Thanks for the input! I hope you have a good morning, and I'll let you know tomorrow/later today with anything new and interesting I find :) On Wed, Sep 25, 2013 at 1:45 AM, Terje Elde wrote: > 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 = versions can be a bit tricky. This is a moving target, and I've lost track = of the 8-branch. > > That said, assuming you have the correct bootcode (gptzfsboot), here's wh= at might have happened: > > You installed 8.2, with a loader supporting zfs. Then you upgraded your /= boot-stuffs, and bootcode on disk (correctly), but got left with a loader w= ithout zfs support. Then tried to upgrade the bootcode, but you're still le= ft with a loader not supporting zfs. > > If I recall correctly, then the zfs-bootcode for 9+ will use "zfsloader" = (supporting zfs and built by default), while earlier versions depend on "lo= ader" with zfs support (built without by default). > > If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.conf= and rebuild/reinstall it, or install /boot/loader from the fixit (if it ha= s zfs support in 8.4). > > That's my first thought at least... If that doesn't fix it (remember bac= kups of any files you replace or upgrade), it'd be interesting to see the o= utput 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 /boo= t/loader there, which might be the easiest way to get the system up, before= rebuilding with ZFS-capable loader... if I'm right, which isn't a given (r= ef disclaimers). > > Terje >