From owner-freebsd-current@freebsd.org Thu Nov 7 20:50:07 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 6A08B1787E9 for ; Thu, 7 Nov 2019 20:50:07 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10022001.me.com (pv50p00im-ztdg10022001.me.com [17.58.6.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 478FsB3806z4K9B for ; Thu, 7 Nov 2019 20:50:06 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10022001.me.com (Postfix) with ESMTPSA id 6ED46A0708; Thu, 7 Nov 2019 20:50:03 +0000 (UTC) From: Toomas Soome Message-Id: <84DD38AC-4D18-431E-8C34-7493C2C032EF@me.com> Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: CURRENT October images do not create a bootable install Date: Thu, 7 Nov 2019 22:50:01 +0200 In-Reply-To: <8796e4c2dedffbdd8502c07bab861c9a@udns.ultimatedns.net> Cc: Current To: "bsd-lists@bsdforge.com" References: <8796e4c2dedffbdd8502c07bab861c9a@udns.ultimatedns.net> X-Mailer: Apple Mail (2.3601.0.10) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-07_06:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911070196 X-Rspamd-Queue-Id: 478FsB3806z4K9B X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(0.00)[ip: (-4.90), ipnet: 17.58.0.0/20(-2.44), asn: 714(-2.52), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[58.6.58.17.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 20:50:07 -0000 > On 7. Nov 2019, at 21:07, Chris wrote: >=20 > On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tsoome@me.com = said >=20 >> > On 7. Nov 2019, at 19:37, Chris.H 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 = 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