From owner-freebsd-current@freebsd.org Tue Oct 8 23:49:41 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 3F7CD13AAB3 for ; Tue, 8 Oct 2019 23:49:41 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 46nvGD2Dvdz3Brf for ; Tue, 8 Oct 2019 23:49:39 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 076EC6FE for ; Tue, 8 Oct 2019 19:49:37 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 08 Oct 2019 19:49:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:from:to:references:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=f dffce3G5qTtX5CrX4zI/oofeyuNB07bHwwLLsasnE0=; b=ajtgbEG7ZQ2fyuBIO r1qP6XmghZGoH4KFOLFPkF0u2Qc3zzmowB3H3PKG79LJXIIyGBWw90i4Q2Z9YBXO ZW9R1VVWO0mDTid01yrokgWTTcw4xw9NKwfB6IPwAClJ+oGs3csZH5t3dF6JCvoU SQ/zUhKKU9nzrOJmL7r6qsXLRZOAPr8EZJ0PJpnXGedVi2jmCim1uYLIxDZwiMFN YRRRkbuxEq/OX8J3BAXGwJyAhXN5+rV7ISdsYvdeRG8/eNEaJZ6815pA7SL3rZ1/ DfAt4+4bbHxzpdspRlITyHLKqMYEmHrj/fy5jA8SGAMpifzESBn+jJU+30Vh1dHD 2/fuw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=fdffce3G5qTtX5CrX4zI/oofeyuNB07bHwwLLsasn E0=; b=eNNiaV9oSuhzr40zmEuxTvcUdvIuZdvzd0aRJ7qhXkGsioMTWjViZVXUn HEbdQZWdyl3qqTVyAWQq2arw/ImOVdPeML7EuHbZqtNGupwKVrFKfjuuv7FBzXfF LBPJ5v/iWkeFSASfQIBCSmVOPYb0Vhk4M7JWD4pXR9Y/hyamodDP7H9PekCj36OZ TNfYJxWvrU7rSp/V0e4hBFOMJygzP30T+RJi4M+wytO3SEbSDzdBQTrrsuESIMEQ vrQzUFh3c68wSdFB8xp5agLZ8IRIZQEnlvz3DASpM17Uuw9SMgdUXQa9VCJeZb81 1du5mrxpmJwFe5PU3cvM87nekGHIQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedriedtgddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffhvfhfkffffgggjggtgfesthejre dttdefjeenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihuhhrihhpvheshihurhhi phhvrdhnvghtqeenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucfkphepkeehrd dujedvrdehgedruddugeenucfrrghrrghmpehmrghilhhfrhhomhephihurhhiphhvseih uhhrihhpvhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from [192.168.1.11] (unknown [85.172.54.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 64D86D6006E for ; Tue, 8 Oct 2019 19:49:36 -0400 (EDT) Subject: Re: memstick installer doesn't install loader.efi into ESP From: Yuri Pankov To: freebsd-current@freebsd.org References: Message-ID: <05d75a5a-5474-2f2c-3066-5426e77871f5@yuripv.net> Date: Wed, 9 Oct 2019 02:49:34 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46nvGD2Dvdz3Brf X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.net header.s=fm1 header.b=ajtgbEG7; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=eNNiaV9o; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.net designates 64.147.123.25 as permitted sender) smtp.mailfrom=yuripv@yuripv.net X-Spamd-Result: default: False [-6.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[yuripv.net:s=fm1,messagingengine.com:s=fm1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[yuripv.net:+,messagingengine.com:+]; DMARC_NA(0.00)[yuripv.net]; IP_SCORE(-3.48)[ip: (-9.78), ipnet: 64.147.123.0/24(-4.90), asn: 11403(-2.68), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[25.123.147.64.list.dnswl.org : 127.0.5.1]; RECEIVED_SPAMHAUS_PBL(0.00)[114.54.172.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[] 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: Tue, 08 Oct 2019 23:49:41 -0000 On 10/8/2019 9:07 AM, Yuri Pankov wrote: > On Mon, Oct 7, 2019, at 5:23 AM, Yuri Pankov wrote: >> Just tried reinstalling the system on my laptop using the latest >> available memstick snapshot >> (https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20191004-r353072-memstick.img), >> using UEFI boot, and default ZFS partitioning, and it didn't boot after >> installation. Booting into the installer again, I noticed that ESP is >> empty. >> >> Reinstalling again after wiping pool labels and clearing partitions >> didn't change anything, though I noticed the "/tmp/bsdinstall-esps: no >> such file or directory" in the installer log. >> >> Mounting ESP, creating EFI/FreeBSD/ directory, copying /boot/loader.efi >> there, and creating appropriate Boot variable solves it, of course, but >> I'm wondering what have gone wrong. >> >> Laptop has NVMe drive (nvd0, empty, gpart destroy -F nvd0), SATA drive >> (ada0, empty, gpart destroy -F ada0), and is booting from USB memstick >> (da0); no Boot variables defined when booting to installer (other than >> defaults ones for laptop). Any other details I should provide here? > > I think I see the problem, bootconfig script uses ZFSBOOT_DISKS variable that isn't defined and always empty and auto-detection must be unreliable in some cases, at least for me as I reproduced it on another system with NVMe device adding a SATA disk as well (didn't look into the details). Should be easy to fix, review incoming. https://reviews.freebsd.org/D21930