From owner-freebsd-current@freebsd.org Sun Jul 29 08:10:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4B50104F840 for ; Sun, 29 Jul 2018 08:10:10 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17B53763B7 for ; Sun, 29 Jul 2018 08:10:10 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id o11-v6so9672453wmh.2 for ; Sun, 29 Jul 2018 01:10:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=46pveQZO7zSeUOkRlNLcxhA5YVL+gpjAtmLKQ62CHwA=; b=Mxmy80IEMNTISLKOOf3ALTFbK7G3CybsnHNXdIU2PmZxzlwiUvml/2JYU1VUXMhI7E tCBuq0Al7ZrfPnbLLnV6PHaro+uqVbhWTyAsrGVOPOrvXOq/fGwL5EE0dtycpi7IZh8x RPI6jR9v438q//0UW14qroRAYqKGBWsEyCjSDU7ETjy3ZNwfKcD9LWjbcdFAyCbh14aH /H19CeMac+iIopEk6WFaveZpmxY6d6pC0sDCwUnR5Jj9IDS6UpZ7BjCU2GrSBCqbgI9Y bw5pGvqceXWl5V35O+2fJWgGGhALNBvBq8a8N6qT4M8eUdhJIM22o+5GREnhb3Me9kln zKHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=46pveQZO7zSeUOkRlNLcxhA5YVL+gpjAtmLKQ62CHwA=; b=U++aIP8+ClE5AodGErms9hjJCGZIIMA9IVdH5XTrVLBcZprYJTJRGINvTGZ7WU5Y8B mhlDJisdCTI1HTXOhDITTZvtvJFzWZ/coKhhUDiF6k5YRJY4FYxC485Gr/CCvzaO8/cH aJKcRRKnpsECfM9TwcUio0AcCLinG1jn60f9AhDnpJ6TvKGjaxFaVzZ8YDvkOVgrgmrj Iw0lEPYD3jjhQJ5Ppgkcj2BmDWYbf21AZPnMgXtLksxt7iZn+RIgzD0dG/VX8/q89qnd ec7VPc2bFHflQqaESN89dKOKINCyd0tLp6AT/MaBy4zjV2BkuzPI98WoUear5ZoCdOwZ cLTg== X-Gm-Message-State: AOUpUlEqT9inL3H/+bGOJ5pktlyhy/Jwry8fM9j0bXkozDY7mkyTrgIy 85wskJdVzkc8o/g+qLh8a0Nm1fshk+o= X-Google-Smtp-Source: AAOMgpd9ab2Lfg2urwqKUAXGrdAnIYTQBXYkplNDYuRyJfjrmyv5g/zB24gHboGTNkRhbLbIepYpWQ== X-Received: by 2002:a1c:ac44:: with SMTP id v65-v6mr10273397wme.25.1532851808962; Sun, 29 Jul 2018 01:10:08 -0700 (PDT) Received: from kloomba ([95.104.142.14]) by smtp.gmail.com with ESMTPSA id u7-v6sm5051633wmd.46.2018.07.29.01.10.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Jul 2018 01:10:08 -0700 (PDT) Sender: Roman Bogorodskiy Date: Sun, 29 Jul 2018 12:09:58 +0400 From: Roman Bogorodskiy To: "O. Hartmann" Cc: freebsd-current@freebsd.org Subject: Re: EFI issues Message-ID: <20180729080957.GB2216@kloomba> References: <20180728072938.GA28778@kloomba> <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <20180729094502.180dabc0@thor.intern.walstatt.dynvpn.de> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Sun, 29 Jul 2018 08:10:11 -0000 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable O. Hartmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > Am Sat, 28 Jul 2018 11:29:40 +0400 > Roman Bogorodskiy schrieb: >=20 > > Hi, > >=20 > > I have a test box that's updated to -CURRENT usually once in a week or > > two. This box boots using UEFI. After a regular update about two weeks > > ago it started to panic on boot frequently (not UEFI related), but I > > could not get a crash dump because my swap partition was too small. So I > > moved data to the backup drive, repartitioned the main drive and boot > > again. This went fine, so I decided to upgrade to fresh -CURRENT from > > ~Jul 27th. Booting with the new kernel went fine, but after installworld > > machine stopped booting, and on the screen I see: > >=20 > > FreeBSD/amd64 EFI loader, ... > >=20 > > .. > >=20 > > BootOrder: .... > >=20 > > And then it gets stuck and nothing happens. > >=20 > > As I already have a fresh backup, I decided that it'd be easier to > > just re-install and copy data back over (maybe I messed up with > > repartitioning). So I've downloaded a fresh snapshot: > >=20 > > FreeBSD-12.0-CURRENT-amd64-20180726-r336739-memstick.img > >=20 > > And re-installed. In the installer I choose all the same settings that > > were before: UEFI + GPT, default partition scheme it suggested (efi > > followed by freebsd-ufs followed by freebsd-swap), just increased the > > swap size. > >=20 > > And the newly installed system won't boot just like a previous one: > >=20 > > https://people.freebsd.org/~novel/misc/freebsd_efi_lookup.jpg > >=20 > > Is there a way to recover this? > >=20 > > Roman Bogorodskiy >=20 > Just curious: >=20 > When I installed FreeBSD last time from the recent (2018-07-26) USB flash= drive on a SSD, > the freebsd-swap partition followed immediately after the ESP and/or free= bsd-boot GPT > loader partition. But in most cases I used to use ZFS for testing. When I reinstalled it yesterday from -CURRENT snapshot mentioned above, in guided mode it suggested a similar partitioning schema that I use: =3D> 40 1953525088 ada0 GPT (932G) 40 409600 1 efi (200M) 409640 1803550720 2 freebsd-ufs (860G) 1803960360 148897792 3 freebsd-swap (71G) 1952858152 666976 - free - (326M) The only difference it that the freebsd-swap size was 3.5G (and therefore, freebsd-ufs is large), the order was the same. > Since I had my UEFI adventure of my own these days and received valuable = hints from the > development/maintenance team on some UEFI aspects, it would be of interes= t to know your > recent hardware and, more importantly since I see the boot order presente= d in you > screenshot, a dump of the efi variable settings. Just for curiosity. For = that, you have > to boot the recent USB flash drive image with UEFI-only, then logon as ro= ot and perform >=20 > kldload efirt >=20 > and then issue=20 >=20 > # efibootmgr -v >=20 > In my case, it looks like >=20 > [...] > [ohartmann]: sudo efibootmgr -v > BootCurrent: 0001 > Timeout : 3 seconds > BootOrder : 0001, 0002, 0003, 0004, 0005, 0000 > +Boot0001* FreeBSD-12 \ > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/File(\efi\bo= ot\BOOTx64.efi) \ > ada0p1:/efi/boot/BOOTx64.efi (null)=20 > Boot0002* Hard Drive BBS(HD,,0x0) > Boot0003* CD/DVD Drive BBS(CDROM,,0x0) > Boot0004* USB BBS(USB,,0x0) > Boot0005* Network Card BBS(Network,,0x0) > Boot0000 FreeBSD-12 > HD(1,GPT,e1460941-e2e9-11e5-b913-d0509907ef09,0x28,0x640)/File(\efi\boot\= BOOTx64.efi) > ada0p1:/efi/boot/BOOTx64.efi (null) >=20 >=20 > Unreferenced Variables: > [...] >=20 > Boot0000 is the same as Boot0001 and is defined due to some "bug" Warner = Losh has fixed > recently, it is the same as Boot0001 Motherboard is (from dmidecode): Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 0806 Release Date: 02/20/2014 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: B85M-E Version: Rev X.0x Serial Number: 140526238405585 Asset Tag: To be filled by O.E.M. = = =20 Features: = = =20 Board is a hosting board = = =20 Board is replaceable = = =20 Location In Chassis: To be filled by O.E.M. = = =20 Chassis Handle: 0x0003 = = =20 Type: Motherboard = = =20 Contained Object Handles: 0 'efibootmgr -v' output: BootCurrent: 0004 Timeout : 1 seconds BootOrder : 0001, 0002, 0003, 0004 Boot0001* Hard Drive BBS(HD,,0x0) Boot0002* Network Card BBS(Network,,0x0) Boot0003* UEFI OS HD(1,GPT,78459ec0-9303-11e8-97e6-98ded0009b1c,0x28,0x640= 00)/File(\EFI\BOOT\BOOTX64.EFI) ada0p1:/EFI/BOOT/BOOTX64.EFI (null) Path(0,0,ae84b11df581724e85442bab0c2cac5c020000020000) +Boot0004* UEFI: SanDisk PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x4,0x= 0)/HD(1,MBR,0x90909090,0x1,0x640) VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6,53006100= 6e004400690073006b000000) Unreferenced Variables: > Kind regards, >=20 > oh >=20 > - --=20 > O. Hartmann >=20 > Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr > Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs. 4 B= DSG). > -----BEGIN PGP SIGNATURE----- >=20 > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW11wfgAKCRDS528fyFhY > lMojAf929USx1x7I/sSGLtEWKO8rm9IXf1JEpQ7GSdI6YHid364x7fbrUBhDZYuT > JVanY57Li2oLOXogHtMw6eDUyD+aAf9GTE30LUNRhmcJ7el62Vwpm0oUBG2as52i > +v58EZ9c20yKQKuXt446dhbILyODDPKmc9ykAvnE0TtMiTHk6vRn > =3DM7vi > -----END PGP SIGNATURE----- Roman Bogorodskiy --RASg3xLB4tUQ4RcS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbXXZVAAoJEMltX/4IwiJqJu8IAMS11Fhah0Sv2lbRdIszqLKM TGQnSLOF+gw6M5WxoF059m/fM4SEKwNUsTH+7R/tLg/m7I9NWA+vxz8DJC9PeEMF GDRITpkbiSlGCZx1LvmnpAUTCO4av9+sX+bqeKYSO15a4Xn+vY1H5tMfmZW8hD+X 1bd20rveUpqyj3tlbaegvoRK5bT48joQRnYF20V+S3tqRwRzfON5iAfshfQlwsSM sjeu/gz2pEowpa9C6qNGrNLNO/B6OkDE5l6CTgtl+l7gCl3YaBTTuc9JsHNGrg88 RYg9Nnz2Y1VGGy2K3Rzn6UFOLLCwGHJxeldyaS1kitU1YDOKp5kIZ6eMhoN1IyI= =tcvb -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS--