Re: CURRENT October images do not create a bootable install

From: Chris <bsd-lists_at_BSDforge.com>
Date: Fri, 08 Nov 2019 11:23:25 -0800
On Fri, 8 Nov 2019 20:43:33 +0200 Toomas Soome tsoome_at_me.com said

> > On 8. Nov 2019, at 20:34, Chris <bsd-lists_at_BSDforge.com> wrote:
> > 
> > On Fri, 8 Nov 2019 10:32:25 +0100 gljennjohn_at_gmail.com
> > <mailto:gljennjohn_at_gmail.com> said
> > 
> >> On Thu, 07 Nov 2019 09:41:01 -0800
> >> Chris <bsd-lists_at_BSDforge.com> wrote:
> >> > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tsoome_at_me.com said
> >> > > > > On 7. Nov 2019, at 17:23, Daniel Nebdal <dnebdal_at_gmail.com> wrote: 
> > > > > > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennjohn_at_gmail.com said  > > >>
> > I chose GPT.  > > > > > Maybe whoever wrote the EFI/BIOS code in your machine
> > went all-in on > > > > "Legacy", and it only handles MBR disks (or disks <
> > 2.2TB)?
> >> > > > After all, it seems like "not booting" would be a standards-compliant
> >> > > > way for a classic BIOS to handle a GPT disk.  > > > >  > > if your
> > system is not booting from GPT disk, it means it is not standards
> >> > > compliant.  > Interesting. So then RELENG-12 is not "Standards"
> > compliant. While 13-CURRE
> >> > NT is?
> >> > IOW I attempted in early October to install each of the (13-CURRENT)
> > instal
> >> > l
> >> > images available. Both on a 500Gb disk, and a 1Tb disk. All w/o success.
> > In
> >> > desperation, I settled for the then (most recent) RELENG-12. 12 installed
> >> > as all previous FreeBSD installs have done successfully.
> >> > So something in (recent) 13' boot layout has changed. I can boot
> > Legacy/UEF
> >> > I/GPT
> >> > on 12. But cannot boot at all in recent 13.
> >> >
> >> I noticed that your 12 disk has Stripesize: 0 on all partitions
> >> but 13 has Stripesize: 4096 on all partitions.
> >> My bootable 13 disk has Stripesize: 0 on all partitions.
> >> Whether that is the cause of your problem I can't say.
> > 
> > Thanks for the reply, Gary.
> > Toomas also had some valuable input on my problem booting 13.
> > In any case. I used the installer to create the disk layout. I didn't
> > do anything different than I have for many years installing FreeBSD from
> > the install sources. What puzzles me, is that RELENG-12 creates a
> > bootable install, whereas 13-CURRENT won't.
> > I've manually setup disks innumerable times in the past. I'll see
> > if doing so produces bootable media doing it from a 13-CURRENT live
> > DVD, or MEMSTICK, and report my findings.
> > 
> > Thanks again for taking the time to reply, Gary.
> >> 
> 
> Did you manage to check what is in your efi (ESP) partition? Also, can you
> confirm if your system is set to boot in BIOS or UEFI mode? Note this may be
> tricky to figure, for example my AMI bios depends on which device is set for
> boot device. Also for UEFI boot, we do not support secure boot.

Thanks for the reminder.

It appears that the installer didn't *format* the ESP/EFI partition. Following
are the results of my investigation -- I'm also attaching a copy of the session,
should it be easier to read.

Script started on Fri Nov  8 11:04:11 2019
root_at_thirteen:~ # 

root_at_thirteen:~ # ls -la /dev/gpt/

total 1
dr-xr-xr-x   2 root  wheel      512 Nov  7 00:54 .
dr-xr-xr-x  15 root  wheel      512 Nov  6 16:54 ..
crw-r-----   1 root  operator  0x8e Nov  7 00:54 throot
crw-r-----   1 root  operator  0x91 Nov  7 00:54 thswap
crw-r-----   1 root  operator  0x96 Nov  7 00:54 thusr
crw-r-----   1 root  operator  0x93 Nov  7 00:54 thvar
crw-r-----   1 root  operator  0x99 Nov  7 00:54 thxtra
crw-r-----   1 root  operator  0x72 Nov  6 16:54 troot
crw-r-----   1 root  operator  0x75 Nov  7 00:54 tswap
crw-r-----   1 root  operator  0x7a Nov  6 16:54 tusr
crw-r-----   1 root  operator  0x77 Nov  6 16:54 tvar
crw-r-----   1 root  operator  0x7d Nov  6 16:54 txtra
root_at_thirteen:~ # mount -t msdosfs /dev/ada0p1 /mnt

root_at_thirteen:~ # ls -la /mnt/

total 21
drwxr-xr-x   1 root  wheel  16384 Jan  1  1980 .
drwxr-xr-x  22 root  wheel   1024 Nov  7 00:54 ..
drwxr-xr-x   1 root  wheel    512 Apr 12  2016 EFI
root_at_thirteen:~ # ls -la /mnt/EFI/

total 17
drwxr-xr-x  1 root  wheel    512 Apr 12  2016 .
drwxr-xr-x  1 root  wheel  16384 Jan  1  1980 ..
drwxr-xr-x  1 root  wheel    512 Apr 12  2016 BOOT
root_at_thirteen:~ # ls -la /mnt/EFI/BOOT/

total 130
drwxr-xr-x  1 root  wheel     512 Apr 12  2016 .
drwxr-xr-x  1 root  wheel     512 Apr 12  2016 ..
-rwxr-xr-x  1 root  wheel  131072 Apr 12  2016 BOOTX64.EFI
-rwxr-xr-x  1 root  wheel      12 Apr 12  2016 STARTUP.NSH
root_at_thirteen:~ # umount /mnt/

root_at_thirteen:~ # mount -t msdosfs /dev/ada1p1 /mnt

mount_msdosfs: /dev/ada1p1: Invalid argument
root_at_thirteen:~ # ls /dev/ada*

/dev/ada0   /dev/ada0p2 /dev/ada0p4 /dev/ada0p6 /dev/ada1p1 /dev/ada1p3 /dev/ada1p5
/dev/ada0p1 /dev/ada0p3 /dev/ada0p5 /dev/ada1   /dev/ada1p2 /dev/ada1p4 /dev/ada1p6
root_at_thirteen:~ # mount /dev/ada1p1 /mnt/

mount: /dev/ada1p1: No such file or directory
root_at_thirteen:~ # exit

exit

Script done on Fri Nov  8 11:09:35 2019


Thanks again!

--Chris
> 
> rgds,
> toomas

Received on Fri Nov 08 2019 - 18:23:17 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC