Date: Thu, 7 Nov 2019 22:50:01 +0200 From: Toomas Soome <tsoome@me.com> To: "bsd-lists@bsdforge.com" <bsd-lists@BSDforge.com> Cc: Current <freebsd-current@freebsd.org> Subject: Re: CURRENT October images do not create a bootable install Message-ID: <84DD38AC-4D18-431E-8C34-7493C2C032EF@me.com> In-Reply-To: <8796e4c2dedffbdd8502c07bab861c9a@udns.ultimatedns.net> References: <8796e4c2dedffbdd8502c07bab861c9a@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 7. Nov 2019, at 21:07, Chris <bsd-lists@BSDforge.com> wrote: >=20 > On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tsoome@me.com = <mailto:tsoome@me.com> said >=20 >> > On 7. Nov 2019, at 19:37, Chris.H <chris.h@ultimatedns.net> wrote: >> > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tsoome@me.com said >> > >> > On 7. Nov 2019, at 17:23, Daniel Nebdal <dnebdal@gmail.com> = wrote: >> >> > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennjohn@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-CURRENT >> > is? >> Can not tell if you do not provide actual information, we can not = really tell >> too much. However, based on the partition tables below, I can tell a = bit. >> Those disks are using GPT, there is EFI partition, which does suggest = UEFI >> boot and not BIOS boot. There is no freebsd-boot partition, meaning = the >> standard pmbr boot block does not work (if installed) =E2=80=94 pmbr = does search >> for freebsd-boot and will load its content and jumps on it. Without = seeing >> your sector 0, I can not tell what code is there (if any), and based = on >> partitions on that system, it is possible the BIOS boot is not = installed at >> all. In a similar way, without seeing EFI partition content, we can = not tell >> if UEFI boot is actually installed - EFI partition should have FAT = file >> system with specific directory tree. >> To make things better, the exact description would be helpful, so the = devs >> taking care of installer could review the information and make fixes. >=20 > Right. Sorry. I forgot you had asked for the output of dd(1). >=20 > I've done so, and will send you the output directly (off list). >=20 neither of disks had boot code in MBR block, so BIOS boot was definitely = not going to happen there (the regular pmbr there would not help because = there is no freebsd-boot partition). Therefore the question is if the = ESP was set up properly. My personal suggestion for x86 setups would be to set up both bios and = efi boot. rgds, toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84DD38AC-4D18-431E-8C34-7493C2C032EF>