Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Dec 2017 23:16:30 +0100
From:      Polytropon <freebsd@edvax.de>
To:        Robert Fitzpatrick <robert@webtent.org>
Cc:        Robert Fitzpatrick via freebsd-questions <freebsd-questions@freebsd.org>
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>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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, ...



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20171210231630.800ae3d8.freebsd>