From owner-freebsd-questions@freebsd.org Sun Dec 10 22:16:47 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 196C2E9ECD9 for ; Sun, 10 Dec 2017 22:16:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 79F0865768 for ; Sun, 10 Dec 2017 22:16:45 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.18.98]) by mrelayeu.kundenserver.de (mreue002 [212.227.15.167]) with ESMTPA (Nemesis) id 0Lyvo0-1fAR4i0CRs-0149c4; Sun, 10 Dec 2017 23:16:32 +0100 Date: Sun, 10 Dec 2017 23:16:30 +0100 From: Polytropon To: Robert Fitzpatrick Cc: Robert Fitzpatrick via freebsd-questions Subject: Re: Boot issue after upgrade Message-Id: <20171210231630.800ae3d8.freebsd@edvax.de> In-Reply-To: <5A2D9082.9060706@webtent.org> References: <5A2D9082.9060706@webtent.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:0BiTXZH0oYmuj8nyC3H5JoKMe0pAikAdjgaIjmddGVpg/BBj9Qy aL7Sr+P+86DxvBh3KTFjkJaJmS+asfXQsDdZm/Bcafs6FI+Qva/fPDbz4mJKQYYDRx35tYe N/Wk4Jg+mwXLlf82LKrJ3+PmZwAWy0zFOcOhNckcJWqiOAR5n1MyDQM5zjaraX2+yLMZlJ1 70uqzV7uWnMNu7N42kMAA== X-UI-Out-Filterresults: notjunk:1;V01:K0:WKq9p33ssFc=:dXVQ6z7158sAWDYMrj9L1v oUlSMmjckS8rDMUxUUgBfjPH3iRHtiwFKfDep83BoHGtQBWnjfnWZAhk4L7m7+Wil3OLVKFGo jOAdAKfcBBwICzLJy1iJeCepb3YWR2aHRuyFFHfXU8bWDzTjNY1y6AfoYPmv18gai2rMnMA0+ +WGjaFPAnTIJp1JDKycL6HR5o5F/BKBCXdF1XFPiGvONUAmPznPeWTKEm124juBqJ/tY1oazV VO5wyoWtysQ0bg21o+7Q6H0NHS5sZczCatQ9/J1DWHgGCYhV7o+ojBku/2z87JSc+y9tPXSNd D1rVPtEALJkANzAVGbCwb+iOdLOIYZShSo7EnH+6mm5JvCg0lzS2FHgmHIlnRAsJKlEErOuOC sRVsQtFfVaadXeXSCLze5mX1bjf3GUAtJ/tQxC94/ca/OKtIORKidsYx94N8/gIy6v5xRpMJY jMkXOxS8kXNE+2bRqRLOuOGuXsiCF7UAOzLDk3P7Vq9f/RVzNrRdxtGdoJePKanuLJLYf0I71 5fnzIGoPSkXZGhWnuNvAfvEe/FQvIt1XH/QMZpCZ1qugzHLSQ6Vu3wc2QFPAvoexcVL+xdsC0 Talav+kLrQV7bXIlWtV5ncsU8xbBmsMSmbMZWrL/289L8OIG0e2/YIBGg2c+NV94r0anws3S5 tjYSjRbW6jEAXmwta8xqYBU0f9qhbxMU/N5vD8s4TtTQOyGqf9Ln2mSYUWUChzS97AGMsuf4Q hI+iuYsSY/yLY7vRzkgOK9rPlX5yAsKzZTLzvLQwUUwmIOhMyPST2kUX1WM= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 22:16:47 -0000 On Sun, 10 Dec 2017 14:52:34 -0500, Robert Fitzpatrick via freebsd-questions wrote: > Since I upgraded a server from FreeBSD 10.1 to 10.4, it no longer boots > to the standard BSD menu. Instead, it kicks me to an OK prompt where I > have to 'set currdev=disk0s1a', then boot. How can I get my automatic > boot menu back? The prompt you're seeing indicates that the boot process has been interrupted prior to the loader (that displays the BSD boot menu). Somehow your boot code got damaged, so the device to boot from needs to be entered manually. Depending on disk partitioning, labels, or setup in general, I'd guess that you need to run "gpart bootcode" with the device to boot from. Compare with the list of commands here: http://www.wonkity.com/~wblock/docs/html/disksetup.html This should fix your problem. Still, I cannot tell you why the required information from the 1st boot stage has been lost... For further reference: https://www.freebsd.org/doc/handbook/boot-introduction.html Note that fdisk is still mentioned here. It will usually still work, but using gpart is today's fashion. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...