From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 18 22:21:58 2014 Return-Path: Delivered-To: freebsd-hackers@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 ESMTPS id 18E77484 for ; Thu, 18 Sep 2014 22:21:58 +0000 (UTC) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF9AED9A for ; Thu, 18 Sep 2014 22:21:57 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id y10so80359pdj.37 for ; Thu, 18 Sep 2014 15:21:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type :date:message-id:mime-version:content-transfer-encoding; bh=UYyKwxb9gBt2TLnsj2Ru0OxCY1tWlzyDJh8L3u9J6RE=; b=oA04+XVM17sweSBO8k2t48PyJEonWKaWlEHN4iXaitfsakjZ+sK2G+5D40PyPh2Mw0 P6OCYjy5tbuWQKl23rA8Q/XDpHvYjkOQEex72xi2I1WC5K90wGPn7CDTM/+yEGjRes3n 3ikw1h/h/MdZ4m/bAScoZckQ/f7xiYdHx9KbPCJQribk6COWN53gs/H0EZ41OBqRW3qz m5/XYAYcivBGmMEqU/v1xq3PyZS4gYVFoNzUw83+K3eceTQyKSQKhN1Jds0+Hl1Ed6wW QMRMfwod5m+hM65rfbft2hFQLvxWD5wfLvmFpo9JZnLvAsIEQQi/w7182gqDJvxmD57m Fp6Q== X-Received: by 10.70.88.237 with SMTP id bj13mr11336984pdb.57.1411078917080; Thu, 18 Sep 2014 15:21:57 -0700 (PDT) Received: from ?IPv6:2001:470:f0fd:0:2e0:81ff:febc:fdcc? ([2001:470:f0fd:0:2e0:81ff:febc:fdcc]) by mx.google.com with ESMTPSA id qy1sm52526pbc.27.2014.09.18.15.21.55 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Thu, 18 Sep 2014 15:21:56 -0700 (PDT) Subject: Re: "Invalid partition table" on 10-stable. From: Frank Mayhar Reply-To: fmayhar@gmail.com To: Wojciech Puchar In-Reply-To: References: <1411013471.25791.52.camel@jill.exit.com> <541AB164.80707@beastielabs.net> Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 18 Sep 2014 15:22:58 -0700 Message-ID: <1411078978.90616.21.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 22:21:58 -0000 On Fri, 2014-09-19 at 00:03 +0200, Wojciech Puchar wrote: > >> > >> /sbin/gpart bootcode -b /boot/pmbr ada0 > >> > >> Probably gpart changed the way it installs the MBR, but I think it is > >> very board (or maybe BIOS) specific: other systems do not have the issue. > >> > >> Please let me know if this "trick" helps for you. > > > > I did install the pmbr during the initial setup, as well as the bootstrap > > itself. I do plan to try the "set active partition" trick suggested > > elsewhere. > while it may not solve your problems i prefer to NEVER make MBR partitions > at all, only bsdlabel. > > example: > > [root@laptop ~]# bsdlabel ada0 > # /dev/ada0: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 249984 16 4.2BSD 0 0 0 > b: 4750000 250000 swap > c: 117210240 0 unused 0 0 # "raw" part, don't edit > d: 63332672 5000000 4.2BSD 0 0 0 > h: 48877568 68332672 4.2BSD 0 0 0 > > simply do > > bsdlabel -B disk > > to make it bootable. Well, my pmbr isn't really an MBR, it's just the fake one to make things "work right" as I understand it. In fact, I don't really understand it, or why it's necessary, but it's pretty clear that something's funky here. I'm planning to avoid disk/bsdlabel entirely in favor of gpart, GPT and zfs. (I'm dead set on using ZFS; I don't trust UFS nearly as much as I used to.) -- Frank Mayhar frank@exit.com