From owner-freebsd-current@freebsd.org Fri Nov 8 18:43:39 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 81B1D15B33D for ; Fri, 8 Nov 2019 18:43:39 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-ztdg06021201.me.com (mr85p00im-ztdg06021201.me.com [17.58.23.189]) (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 478q0p3wBNz3GBW for ; Fri, 8 Nov 2019 18:43:38 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by mr85p00im-ztdg06021201.me.com (Postfix) with ESMTPSA id CAC8A121229; Fri, 8 Nov 2019 18:43:35 +0000 (UTC) From: Toomas Soome Message-Id: <18D24655-A43E-4B56-8754-571C3978FA0D@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: Fri, 8 Nov 2019 20:43:33 +0200 In-Reply-To: <7cf7f5e255eedbfa2a442b40c24f2fd9@udns.ultimatedns.net> Cc: freebsd-current@freebsd.org To: "bsd-lists@bsdforge.com" References: <7cf7f5e255eedbfa2a442b40c24f2fd9@udns.ultimatedns.net> X-Mailer: Apple Mail (2.3601.0.10) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-08_07:, , 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-1911080183 X-Rspamd-Queue-Id: 478q0p3wBNz3GBW 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)[]; 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: (-3.32), ipnet: 17.58.16.0/20(-1.72), asn: 714(-2.49), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[189.23.58.17.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:714, ipnet:17.58.16.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=us-ascii 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: Fri, 08 Nov 2019 18:43:39 -0000 > On 8. Nov 2019, at 20:34, Chris wrote: >=20 > On Fri, 8 Nov 2019 10:32:25 +0100 gljennjohn@gmail.com = said >=20 >> On Thu, 07 Nov 2019 09:41:01 -0800 >> Chris 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-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. >=20 > 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. >=20 > Thanks again for taking the time to reply, Gary. >>=20 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. rgds, toomas