From owner-freebsd-current@FreeBSD.ORG Wed Jan 2 18:57:17 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E8620C1F for ; Wed, 2 Jan 2013 18:57:17 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by mx1.freebsd.org (Postfix) with ESMTP id 7F0731DA2 for ; Wed, 2 Jan 2013 18:57:17 +0000 (UTC) X-AuditID: 12074423-b7ef96d000000725-de-50e4830656c0 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 41.8F.01829.60384E05; Wed, 2 Jan 2013 13:57:10 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id r02IvAg4012314; Wed, 2 Jan 2013 13:57:10 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id r02Iv8YE026547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Jan 2013 13:57:10 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r02Iv8Nv002991; Wed, 2 Jan 2013 13:57:08 -0500 (EST) Date: Wed, 2 Jan 2013 13:57:08 -0500 (EST) From: Benjamin Kaduk To: Robert Huff Subject: Re: problem after installkernel going from 9.0 to CURRENT In-Reply-To: <50E476D3.2030609@rcn.com> Message-ID: References: <50E0BFA0.6070702@rcn.com> <50E476D3.2030609@rcn.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOIsWRmVeSWpSXmKPExsUixCmqrMvW/CTAYN9DPYsJV34wWXRfvM7q wOQx49N8Fo+nKyaxBDBFcdmkpOZklqUW6dslcGU8+/uLteAGb8WuZ8/YGxivcHUxcnBICJhI 3Nnp0sXICWSKSVy4t54NxBYS2McosW6mZxcjF5C9nlHiWPNOdgjnOJPEvFtToKrqJVYcmcoK MohFQEviyGlRkDCbgIrEzDcb2UDCIkB2z2UPEJNZQFziZb8SSIWwgJPEgjUP2UFsTgF1ia1n /zODlPAKOEo8eFoGMdtRovXCKhYQW1RAR2L1/ilgNq+AoMTJmU/AbGYBS4lzf66zTWAUnIUk NQtJagEj0ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdM73czBK91JTSTYyg8GR3Ud7B+Oeg0iFG AQ5GJR7eFTVPAoRYE8uKK3MPMUpyMCmJ8vI3AYX4kvJTKjMSizPii0pzUosPMUpwMCuJ8F7P AcrxpiRWVqUW5cOkpDlYlMR5r6Xc9BcSSE8sSc1OTS1ILYLJynBwKEnwyoIMFSxKTU+tSMvM KUFIM3FwggznARp+uxFkeHFBYm5xZjpE/hSjopQ4rxlIswBIIqM0D64Xlj5eMYoDvSLMqwJS xQNMPXDdr4AGMwENfvXmMcjgkkSElFQDY270If+Vzi9uMWWY3z/25uyCJWF/+wU0c00fznRb 9DFlmSTHzMMy6q4CF55MjHBzXvFr0z3j2aH7Ftz+qHdP72Okw74EndcLN9+wmMIiwDXzVZdU 7yYzuTXHu/k4C7vOHTvKNbH1qFbh83+r485fMvdqcZhcO0dlwdL2dv+t/42adVOEzQTun1Ni Kc5INNRiLipOBAAd1bjF+gIAAA== Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 18:57:18 -0000 On Wed, 2 Jan 2013, Robert Huff wrote: > (While this may not be a strictly CURRENT issue, I asked on > questions@, but have not found a solution.) > > Situation: > One of my boxes failed, and for various reasons it became easier to > just scrub and rebuild it. Like its predecessor it will run CURRENT > 1) Using BSDinstall, I flushed then created the first disk: > > ada2p1 freebsd-boot 128k > ada2p2 freebsd-swap 4g > ada2p3 freebsd-ufs 25g > > (There are non-bootable disks at ada0, -1, and -3.) For a full clean install, I believe that bsdinstall should prompt about installing bootcode around here. I don't really understand from your procedure how bsdinstall was used; there might be some edge case where there is no prompt about bootcode. > 2) Installed off the 9.0 CD, got it up and running, everything was > good. > 3) Used csup (tag=.) to update the source tree as of 00:01 on 12/30. > 4a) Built world - OK. > 4b) Build kernel - OK. > 4c) Ran mergemaster - OK. > 4d) Installed kernel - OK. > 5) On rebooting, the loader(??) claims to not be able to find a > bootable partition - i.e. I get a screen that ends in "mountroot > ". > Providing the presumptive value by hand returns "error 19". > 6) Boot using installation CD and use "gpart show" to double check > device names and partitions; everything looks good. > 7) Try normal booting again, no go. > > This is my first time installing to a completely GPT partitioned > system, and I have (obviously) failed to grok something. I checked > src/UPDATING and found nothing which covered this. > What have I bungled, and how do I fix it? I think you should investigate the 'bootcode' subcommand of gpart(8). -Ben Kaduk