From owner-freebsd-current@freebsd.org Fri Nov 8 18:34:18 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 DCB7615AEFB for ; Fri, 8 Nov 2019 18:34:18 +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 478pp12ynlz3Fh9 for ; Fri, 8 Nov 2019 18:34:16 +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 xA8IYBba070002 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 8 Nov 2019 10:34:18 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 In-Reply-To: <20191108103225.4333bc3b@ernst.home> From: Chris Reply-To: bsd-lists@BSDforge.com To: Subject: Re: CURRENT October images do not create a bootable install Date: Fri, 08 Nov 2019 10:34:18 -0800 Message-Id: <7cf7f5e255eedbfa2a442b40c24f2fd9@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 478pp12ynlz3Fh9 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 [-1.32 / 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)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; IP_SCORE(-0.24)[ip: (-1.77), ipnet: 24.113.0.0/16(-0.88), asn: 11404(1.52), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[BSDforge.com]; AUTH_NA(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998,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)[gmail.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: Fri, 08 Nov 2019 18:34:18 -0000 On Fri, 8 Nov 2019 10:32:25 +0100 gljennjohn@gmail=2Ecom said > On Thu, 07 Nov 2019 09:41:01 -0800 > Chris 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: = =20 > > > > > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennjohn@gmail=2Ecom said = =20 > > > >> I chose GPT=2E =20 > > > > > > Maybe whoever wrote the EFI/BIOS code in your machine went all-= in on=20 > >=20 > > > > "Legacy", and it only handles MBR disks (or disks < 2=2E2TB)? > > > > After all, it seems like "not booting" would be a standards-complia= nt > > > > way for a classic BIOS to handle a GPT disk=2E =20 > > > > > =20 > > > if your system is not booting from GPT disk, it means it is not stand= ards > > > compliant=2E =20 > > Interesting=2E So then RELENG-12 is not "Standards" compliant=2E While 13-C= URRE > > NT is? > > IOW I attempted in early October to install each of the (13-CURRENT) in= stal > > l > > images available=2E Both on a 500Gb disk, and a 1Tb disk=2E All w/o success= =2E In > > desperation, I settled for the then (most recent) RELENG-12=2E 12 install= ed > > as all previous FreeBSD installs have done successfully=2E > > So something in (recent) 13' boot layout has changed=2E I can boot Legacy= /UEF > > I/GPT > > on 12=2E But cannot boot at all in recent 13=2E > > >=20 > I noticed that your 12 disk has Stripesize: 0 on all partitions > but 13 has Stripesize: 4096 on all partitions=2E >=20 > My bootable 13 disk has Stripesize: 0 on all partitions=2E >=20 > Whether that is the cause of your problem I can't say=2E Thanks for the reply, Gary=2E Toomas also had some valuable input on my problem booting 13=2E In any case=2E I used the installer to create the disk layout=2E I didn't do anything different than I have for many years installing FreeBSD from the install sources=2E What puzzles me, is that RELENG-12 creates a bootable install, whereas 13-CURRENT won't=2E I've manually setup disks innumerable times in the past=2E I'll see if doing so produces bootable media doing it from a 13-CURRENT live DVD, or MEMSTICK, and report my findings=2E Thanks again for taking the time to reply, Gary=2E >=20 > [snip gpart output] >=20 > --=20 > Gary Jennejohn --Chris