Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Apr 2018 20:41:57 +0200
From:      Polytropon <>
To:        Robert Fitzpatrick <>
Cc:        Robert Fitzpatrick via freebsd-questions <>
Subject:   Re: Restoring bootcode
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Mon, 30 Apr 2018 12:28:47 -0400, Robert Fitzpatrick via freebsd-questions wrote:
> Polytropon wrote:
> > As this seems to be a MBR setup, the commands should probably be:
> >
> > 	# gpart bootcode -b /boot/mbr ada0
> > 	# gpart set -a active -i 1 ada0
> > 	# gpart bootcode -b /boot/boot ada0s1
> Didn't work, I failed to post the messages received before kicking out 
> to the OK loader prompt. I'm seeing this...
> can't open 'boot/menu.4th': no such file or directory
> Error while including /boot/menu.rc, in the line:
> include /boot/menu.4th
> \
> can't load 'kernel'

This shows that a file required for boot isn't there, but
this has nothing to do with the MBR stage. It's related to
what files need to be present in /boot (usually on /dev/ada0s1a,
if no specific separate boot partition has been created).

> I can see that menu.4th is not in the /boot directory. I do see the 
> below in my menu.rc, all of the files are present in /boot except the 
> menu.4th and menu-commands.4th. The only file in the /boot folder 
> starting with menu is the menu.rc.
> \ Load required Forth modules
> include /boot/version.4th
> include /boot/brand.4th
> include /boot/menu.4th
> include /boot/menu-commands.4th
> include /boot/shortcuts.4th

This indicates your /boot directory's content is damaged.
You proably need to reinstall its content from source, or
hope a freebsd-update will bring it back. The easiest way
to get the file probably is to copy it from the source
directory to /boot manually (directly from its location
in /usr/src).

See "man 8 menu.4th" for details.

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>