From owner-freebsd-current@freebsd.org Thu Nov 7 19:07:15 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4129F1BD8AD for ; Thu, 7 Nov 2019 19:07:15 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 478CZT4hvNz49JJ for ; Thu, 7 Nov 2019 19:07:13 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id xA7J7Bwa051340 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Nov 2019 11:07:17 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: Toomas Soome In-Reply-To: <353EF18E-0421-4687-B64B-C5D5DBA69A30@me.com> From: Chris Reply-To: bsd-lists@BSDforge.com To: Subject: Re: CURRENT October images do not create a bootable install Date: Thu, 07 Nov 2019 11:07:17 -0800 Message-Id: <8796e4c2dedffbdd8502c07bab861c9a@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 478CZT4hvNz49JJ X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bsd-lists@BSDforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=bsd-lists@BSDforge.com X-Spamd-Result: default: False [-0.00 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bsd-lists@BSDforge.com]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.74)[-0.740,0]; IP_SCORE(0.31)[asn: 11404(1.61), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[BSDforge.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.48)[-0.482,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; FREEMAIL_CC(0.00)[me.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2019 19:07:15 -0000 On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tsoome@me=2Ecom said > > On 7=2E Nov 2019, at 19:37, Chris=2EH wrote: > >=20 > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tsoome@me=2Ecom said > >=20 > >> > On 7=2E Nov 2019, at 17:23, Daniel Nebdal wrote: > >> > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennjohn@gmail=2Ecom said > >> >> I chose GPT=2E > >> > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in = on > >> > "Legacy", and it only handles MBR disks (or disks < 2=2E2TB)? > >> > After all, it seems like "not booting" would be a standards-complian= t > >> > way for a classic BIOS to handle a GPT disk=2E > >> > if your system is not booting from GPT disk, it means it is not stan= dards > >> compliant=2E > > Interesting=2E So then RELENG-12 is not "Standards" compliant=2E While 13-C= URRENT > > is? >=20 >=20 > Can not tell if you do not provide actual information, we can not really = tell > too much=2E However, based on the partition tables below, I can tell a bit=2E >=20 > Those disks are using GPT, there is EFI partition, which does suggest UEF= I > boot and not BIOS boot=2E 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=2E Without seein= g > 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=2E In a similar way, without seeing EFI partition content, we can not t= ell > if UEFI boot is actually installed - EFI partition should have FAT file > system with specific directory tree=2E >=20 > To make things better, the exact description would be helpful, so the dev= s > taking care of installer could review the information and make fixes=2E Right=2E Sorry=2E I forgot you had asked for the output of dd(1)=2E I've done so, and will send you the output directly (off list)=2E Thank you! >=20 > rgds, > toomas >=20 >=20 [snip] --Chris