From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 18 22:03:14 2014 Return-Path: Delivered-To: freebsd-hackers@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 ESMTPS id 62CA9AA0 for ; Thu, 18 Sep 2014 22:03:14 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E2025BDF for ; Thu, 18 Sep 2014 22:03:13 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id s8IM399O011400; Fri, 19 Sep 2014 00:03:09 +0200 (CEST) (envelope-from wojtek@puchar.net) Date: Fri, 19 Sep 2014 00:03:09 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Frank Mayhar Subject: Re: "Invalid partition table" on 10-stable. In-Reply-To: Message-ID: References: <1411013471.25791.52.camel@jill.exit.com> <541AB164.80707@beastielabs.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Fri, 19 Sep 2014 00:03:09 +0200 (CEST) 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:03:14 -0000 >> >> /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.