Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Sep 2013 06:43:33 -0700 (PDT)
From:      Andrew Moran <amoran@yahoo.com>
To:        Volodymyr Kostyrko <c.kworr@gmail.com>
Cc:        "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject:   Re: Rescuing a GPT ZFS boot setup
Message-ID:  <1379598213.765.YahooMailNeo@web121304.mail.ne1.yahoo.com>
In-Reply-To: <523AACF8.8080404@gmail.com>
References:  <1379572619.72405.YahooMailNeo@web121302.mail.ne1.yahoo.com> <523AACF8.8080404@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0AAlas, that did not work. =A0 =A0 But it does look to be BIOS related.=
 =A0 =A0=0A=0AI think this new system has a UEFI bios. =A0=A0=0A=0AI just r=
ead from=A0https://wiki.freebsd.org/UEFI:=0A=09* Partitions not seen. When =
using GPT, FreeBSD will create a protective MBR. This MBR has one partition=
 entry covering the whole disk. FreeBSD marks this partition active. This c=
auses at least some UEFI implementations to ignore the GPT. To fix this the=
 partition needs to be marked inactive.=0A=09* Filesystem not seen. FreeBSD=
's FAT32 code appears to sometimes create filesystems that the UEFI code ca=
n't properly read. If the filesystem is small enough, use FAT16 or FAT12 in=
stead.=0A=0AI think this may be my issue. =A0But=A09.1 LiveCD does boot and=
 I can see the data once booted, so there must be a way to fix the boot loa=
der on the drive to work.=0A=0A=A0=A0Is there a way for me to reinstall the=
 MBR or boot partition on the drives to make it boot up with this BIOS? =A0=
:(=0A=0AThanks.=0A=0A--Andy=0A=0A=0A=0A________________________________=0A =
From: Volodymyr Kostyrko <c.kworr@gmail.com>=0ATo: Andrew Moran <amoran@yah=
oo.com> =0ACc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> =
=0ASent: Thursday, September 19, 2013 12:51 AM=0ASubject: Re: Rescuing a GP=
T ZFS boot setup=0A =0A=0A19.09.2013 09:36, Andrew Moran wrote:=0A> 3 years=
 ago I followed https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror  for a=
 FreeBSD 8.1 system (which has since been upgraded to 9.1).=A0 =A0 A couple=
 days ago I had massive hardware failure, and wound up having to put the tw=
o drives into an entirely new PC system.=0A>=0A> Unfortunately I'm not able=
 to get it to boot off the hard drives.=A0 It doesn't even show the FreeBSD=
 bootloader menu it normally would.=A0 The BIOS sees both drives and it can=
 boot off the 9.1 install/Live CD without any problems.=A0  In the LiveCD, =
I can see both drives partition tables ("gpart show ..") and I can import=
=A0 the zpool ("zpool import zroot"), and see all my data.=A0  I just can't=
 seem to boot from it.=A0  I tried rerunning the "gpart bootcode" commands =
on both drives (no errors), but no effect.=0A>=0A> It's also not beyond the=
 realm of possibility I have some BIOS setting wrong, but the drives do sho=
w up in the POST and BIOS setting.=0A>=0A> Does anyone know how I can make =
my drives bootable again?=0A=0AMaybe the machine is just too picky about pa=
rtitioning scheme? Try this =0Ablack magic:=0A=0Aprintf '\ny\n\n\n\ny\n\ny\=
n\n\n\n\ny\n' | fdisk -u ${YourDiskName}=0A=0A-- =0ASphinx of black quartz,=
 judge my vow.
From owner-freebsd-stable@FreeBSD.ORG  Thu Sep 19 13:58:39 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@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 89ABCD2B
 for <freebsd-stable@freebsd.org>; Thu, 19 Sep 2013 13:58:39 +0000 (UTC)
 (envelope-from c.kworr@gmail.com)
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com
 [209.85.217.182])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 149D82F84
 for <freebsd-stable@freebsd.org>; Thu, 19 Sep 2013 13:58:38 +0000 (UTC)
Received: by mail-lb0-f182.google.com with SMTP id c11so7915026lbj.13
 for <freebsd-stable@freebsd.org>; Thu, 19 Sep 2013 06:58:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:cc:subject
 :references:in-reply-to:content-type:content-transfer-encoding;
 bh=y0kMEJ87NMe15mX79QTqQiq9kLxRFBZ0aex/NfZIji8=;
 b=yx7bsMeAbYuVGBj8uy5nhbcw0RlYytGeDUxrdIiojT67RVOSlEEt//ZT9E76grnF9N
 vivcq7vDkNANmzXWxZiGs/Y+VvDaL7qZSKkBxy1flIC7VtjXv1c3pyzJrJLx/9M6yOxC
 /wFGhb/xD9MSG4h9WAd+hs1ggwwFXOXV4hS2SA5ebwyhaXbgmdEOaqXf5udWLYBzVhdw
 v4ub4cOkSeLQNcOl69AZ5slR6Xw6tW0+VN5Z0o85te4BKJKdaODAnaIBGJfOvTiX5VXf
 PsCE1bNxjcqtRQNZD+OZ0RCiFtKmJkPSp8RtLw4PIYjaKbfR1b955UVkRtPx81VrZ6zc
 znqg==
X-Received: by 10.112.156.103 with SMTP id wd7mr1277454lbb.48.1379599095935;
 Thu, 19 Sep 2013 06:58:15 -0700 (PDT)
Received: from [192.168.1.130] (mau.donbass.com. [92.242.127.250])
 by mx.google.com with ESMTPSA id mr1sm2296245lbc.16.1969.12.31.16.00.00
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Thu, 19 Sep 2013 06:58:15 -0700 (PDT)
Message-ID: <523B02F6.4070708@gmail.com>
Date: Thu, 19 Sep 2013 16:58:14 +0300
From: Volodymyr Kostyrko <c.kworr@gmail.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Andrew Moran <amoran@yahoo.com>
Subject: Re: Rescuing a GPT ZFS boot setup
References: <1379572619.72405.YahooMailNeo@web121302.mail.ne1.yahoo.com>
 <523AACF8.8080404@gmail.com>
 <1379598213.765.YahooMailNeo@web121304.mail.ne1.yahoo.com>
In-Reply-To: <1379598213.765.YahooMailNeo@web121304.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>;
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 13:58:39 -0000

19.09.2013 16:43, Andrew Moran wrote:
> Alas, that did not work.     But it does look to be BIOS related.
>
> I think this new system has a UEFI bios.
>
> I just read from https://wiki.freebsd.org/UEFI:
> 	* Partitions not seen. When using GPT, FreeBSD will create a protective MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks this partition active. This causes at least some UEFI implementations to ignore the GPT. To fix this the partition needs to be marked inactive.
> 	* Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create filesystems that the UEFI code can't properly read. If the filesystem is small enough, use FAT16 or FAT12 instead.
>
> I think this may be my issue.  But 9.1 LiveCD does boot and I can see the data once booted, so there must be a way to fix the boot loader on the drive to work.

Good catch. The fix landed in stable not so long ago 
(http://svnweb.freebsd.org/base?view=revision&revision=255017) so you 
wouldn't find it in 9.2 either. Can you try this:

	gpart unset -a active ada0

-- 
Sphinx of black quartz, judge my vow.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1379598213.765.YahooMailNeo>