From owner-freebsd-current@freebsd.org Wed Aug 21 21:17:58 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 AFC99D474A for ; Wed, 21 Aug 2019 21:17:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10021901.me.com (pv50p00im-ztdg10021901.me.com [17.58.6.55]) (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 46DL9K4639z4YmS for ; Wed, 21 Aug 2019 21:17:57 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10021901.me.com (Postfix) with ESMTPSA id E176C882320; Wed, 21 Aug 2019 21:17:53 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found From: Toomas Soome In-Reply-To: Date: Thu, 22 Aug 2019 00:17:51 +0300 Cc: Karl Denninger , "freebsd-current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190821195847.577a165b@thor.intern.walstatt.dynvpn.de> <48D9A1D1-5A54-4FED-8DC8-40C9A5C9BE3A@me.com> <20190821213052.25d61cb4@thor.intern.walstatt.dynvpn.de> <480F8DE0-A38F-4BCA-9F36-0D812CDB7DD8@me.com> <20190821223140.643f6c63@thor.intern.walstatt.dynvpn.de> To: "Clay Daniels Jr." X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-21_07:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1812120000 definitions=main-1908210208 X-Rspamd-Queue-Id: 46DL9K4639z4YmS X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.59 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[me.com]; RCVD_IN_DNSWL_LOW(-0.10)[55.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)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[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)[]; IP_SCORE(0.00)[ip: (-9.75), ipnet: 17.58.0.0/20(-2.99), asn: 714(-2.78), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(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: Wed, 21 Aug 2019 21:17:58 -0000 > On 22 Aug 2019, at 00:07, Clay Daniels Jr. = wrote: >=20 > I would agree with Karl & Steffen about using rEFInd. It really gives = you a > lot more control of your computers boot. Take a look at Rod Smith's = pages: > http://www.rodsbooks.com/refind/ >=20 > I use it to triple boot Windows 10, MX Linux, and FreeBSD. >=20 > Clay rEFInd is fancy menu to start real boot loader, it really does not help = if your boot loader is broken. In worst case, you can get fragmented = memory from having rEFInd and native boot loader (depending on how = stupid/buggy the firmware is). rgds, toomas >=20 > On Wed, Aug 21, 2019 at 3:59 PM Karl Denninger = wrote: >=20 >> ----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA256 >>>=20 >>> Am Wed, 21 Aug 2019 22:34:21 +0300 >>> Toomas Soome schrieb: >>>=20 >>>>> On 21 Aug 2019, at 22:30, O. Hartmann = wrote: >>>>>=20 >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA256 >>>>>=20 >>>>> Am Wed, 21 Aug 2019 22:14:46 +0300 >>>>> Toomas Soome > schrieb: >>>>>=20 >>>>>> If you drop into efi shell, can you start efi/boot/bootx64.efi >>> manually? you should have >>>>>> fs0: or like for ESP. >>>>>>=20 >>>>>> rgds, >>>>>> toomas >>>>>=20 >>>>> Hello, >>>>>=20 >>>>> I can't even stop to gain access to the shell; there is no >>> timeframe to hit any key to >>>>> stop by and access the efi shell. >>>>>=20 >>>>> Kind regards, >>>>> oh >>>=20 >>>=20 >>>> hm? efi shell should be available from boot device menu, so you >>> mean, you can not even get >>>> into firmware setup? >>>=20 >>>> rgds, >>>> toomas >>>=20 >>> Sorry, >>> I confused loader prompt and EFI shell. >>>=20 >>> I do not have a EFI shell on that type of laptop, not to know about >>> it. I can access the >>> firmware setup and already performed a reset and switched back to >>> default settings. No effect. >>>=20 >>> I just downloaded the newest CURRENT mem stick and extracted both >>> boot1.efi and loader.efi and >>> installed those into the ESP as described, setting the efibootmgr = env >>> accordingly. Still the >>> same error. >>>=20 >>> It seems that there is indeed no EFI/UEFI shell. There are Lenovo >>> specific EFI boot options, >>> like "diagnostics" and so on, if selected, the UEFI boots into a >>> firmware embedded diagnostic >>> menu. I tried several from the list given via efibootmgr show -v, = but >>> there is no shell from >>> which I could access/boot an alternative loader. >>>=20 >>> How I'm supposed to achive the access to this EFI shell? I doubt = that >>> on the E540 (beware of >>> the E, it is not a L or T model) does have such a shell. >>>=20 >>> Regards, >>> oh >>=20 >> I would see if you can get REFIND loaded and use that. I have a = Lenovo >> X1 Carbon Gen 6 and that's the answer I used, as it allows multi-boot >> (e.g. Win10 and FreeBSD) easily. >>=20 >> I've not had trouble with 12.x on it, and I do use the >> geli-encrypted-aware loader.efi..... >>=20 >> If there's a way to get into the EFI shell on Lenovo's laptops from = the >> BIOS during the boot I've not found it yet. There's supposed to be = on >> all EFI devices, but you know how "supposed to" works in many cases, = right? >>=20 >> -- >> Karl Denninger >> karl@denninger.net >> /The Market Ticker/ >> /[S/MIME encrypted email preferred]/ >>=20 >>=20 >>=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"