Date: Fri, 19 Sep 2014 00:03:09 +0200 (CEST) From: Wojciech Puchar <wojtek@puchar.net> To: Frank Mayhar <fmayhar@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: "Invalid partition table" on 10-stable. Message-ID: <alpine.BSF.2.00.1409190001590.873@laptop> In-Reply-To: <loom.20140918T225950-776@post.gmane.org> References: <1411013471.25791.52.camel@jill.exit.com> <541AB164.80707@beastielabs.net> <loom.20140918T225950-776@post.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> /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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1409190001590.873>