From owner-freebsd-questions@FreeBSD.ORG Thu Sep 26 07:05:34 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 977C4EFE for ; Thu, 26 Sep 2013 07:05:34 +0000 (UTC) (envelope-from tyler@tsweet.net) Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2BDA021B7 for ; Thu, 26 Sep 2013 07:05:33 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id hj3so6299558wib.2 for ; Thu, 26 Sep 2013 00:05:31 -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:content-type:content-transfer-encoding; bh=cK8GuNzfmhQ1KXOQQk+Tn5GPflbTA4y+xGjOEHQ1/9k=; b=dAM1lXFig8UEVQ9IY4QzkckxjIKQa0NirfFOTsT7J68AXqLzb3Y4v0x4HsmgxwZijH 4rSRM8WvNegmFgqQQhAB8CpSCP4G8Ighe7Q6j/IwmWOF6LBR4DNwQCS9VOPPnNYWvP+z 7e0PaFWz1hJiuDk6tZUvIirwJLH8+DtWV/yNL4AihjxoRUmOm650SnypFLE7bDLv+o6Z NdLN8FUDly3y/V1Sw4mpt4bhz2/TholdFiFRanLFipwYaszlAbCc6sCMY2HMokPNveJ7 NPQIoAZtIyOLN7pW3ZonzIOsSrjZQBtHZKDkr83LmDNorQnd6nkM/xB7HiFOhtJe5zIz KEXQ== X-Gm-Message-State: ALoCoQlPvn7ScaAX8nSm2kwQS1aS1Py21cx7M4QZEUqFAuO5zjf+4OmsUedz3/B409CPRzLGm9zW X-Received: by 10.194.21.131 with SMTP id v3mr904901wje.44.1380178768960; Wed, 25 Sep 2013 23:59:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.12.194 with HTTP; Wed, 25 Sep 2013 23:58:48 -0700 (PDT) X-Originating-IP: [67.212.118.60] In-Reply-To: References: From: Tyler Sweet Date: Thu, 26 Sep 2013 01:58:48 -0500 Message-ID: Subject: Re: FreeBSD 8.4 Boot failure To: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Thu, 26 Sep 2013 07:05:34 -0000 Well, I wasn't able to continue troubleshooting. I took the opportunity that the server was already down to upgrade the BIOS. HP kindly does not provide any checks or warnings letting you know that you need to do a stepped upgrade, so the server is bricked. *sigh*. So this likely won't get investigated more. I'll be setting up a new server and attempting to import the zpools there. Thank for your advice anyhow! If this happens again on another server, I'll see about trying more things. On Wed, Sep 25, 2013 at 3:46 AM, Tyler Sweet wrote: > 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 w= hat 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 = without zfs support. Then tried to upgrade the bootcode, but you're still l= eft 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 "l= oader" with zfs support (built without by default). >> >> If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.con= f and rebuild/reinstall it, or install /boot/loader from the fixit (if it h= as zfs support in 8.4). >> >> That's my first thought at least... If that doesn't fix it (remember ba= ckups of any files you replace or upgrade), it'd be interesting to see the = output 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 /bo= ot/loader there, which might be the easiest way to get the system up, befor= e rebuilding with ZFS-capable loader... if I'm right, which isn't a given (= ref disclaimers). >> >> Terje >>