CURRENT October images do not create a bootable install

[Toomas Soome]

> On 7. Nov 2019, at 10:38, Chris <bsd-lists at BSDforge.com> wrote:
> 
> On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tsoome at me.com <mailto:tsoome at me.com> said
> 
>> > On 7. Nov 2019, at 10:05, Chris <bsd-lists at BSDforge.com> wrote:
>> > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennjohn at gmail.com said
>> > >> On Wed, 06 Nov 2019 17:23:08 -0800
>> >> Chris <bsd-lists at BSDforge.com> wrote:
>> >> > I put a box together to test 13 about a mos ago.
>> >> > It's a second gen core i3. But whether choosing automatic
>> >> > disk layout, or choosing manual. When the install finishes, and
>> >> > boots to the drive. The BIOS reports no bootable media.
>> >> > I finally gave up, and grabbed the most recent RELENG-12. Which
>> >> > worked as expected.
>> >> > While I have no troubles booting (U)EFI. Isn't the so-called
>> >> > LEGACY boot option still supported?
>> >> > > Thank you for all your time, and consideration.
>> >> > > > Thanks for taking the time to respond, Gary.
>> > >> I installed the latest FreeBSD 13 memstick image (UEFI) yesterday
>> >> and had no problem booting it.  I used manual disk partitioning. In fact,
>> > when I added the / partition the installer automatically
>> >> created and populated the EFI boot partition for me.
>> > > Same here. But in spite of it. The reboot proved to be unsuccessful. :(
>> >> I used UEFI because that was already set in the BIOS and the
>> >> computer doesn't belong to me.
>> >> LEGACY mode should still work as long as the BIOS offers that. My main
>> > FreeBSD 13 box uses LEGACY booting.
>> > > My BIOS offers both. Yet neither option proved fruitful. :(
>> >> -- >> Gary Jennejohn
>> > > Thanks again, Gary! :)
>> > Do you have more detailed information? any error messages, screenshots?
> 
> Thanks for the reply, toomas.
> 
> It's just the standard BIOS report about non-bootable device, please inset
> bootable medium...
> 
> IOW it doesn't recognize the freshly installed 13-CURRENT on the hard drive
> as being a bootable OS.
> 
> I'm wondering what happened between RELENG-12, and 13 that made the change?
> 

If the BIOS does not find bootable disk, it likely does check the MBR, please use dd to read out sector 0 from your boot disk (something like dd if=/dev/da0 of=mbr.dd count=1) and mail it to me directly so I can check what is there.

rgds,
toomas