From nobody Tue Dec 27 14:08:07 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NhGhc1Wb5z2c7D2 for ; Tue, 27 Dec 2022 14:08:16 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NhGhb6Kyfz4JyQ; Tue, 27 Dec 2022 14:08:15 +0000 (UTC) (envelope-from johannes-maria@t-online.de) Authentication-Results: mx1.freebsd.org; none Received: from fwd76.dcpf.telekom.de (fwd76.aul.t-online.de [10.223.144.102]) by mailout12.t-online.de (Postfix) with SMTP id 72218194B5; Tue, 27 Dec 2022 15:08:09 +0100 (CET) Received: from t-online.de ([194.140.113.103]) by fwd76.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1pAAci-2LhRei0; Tue, 27 Dec 2022 15:08:08 +0100 Received: by t-online.de (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) johannes-maria@t-online.de; Tue, 27 Dec 2022 15:08:08 +0100 (CET) Date: Tue, 27 Dec 2022 15:08:07 +0100 From: Johannes-Maria Kaltenbach To: questions@freebsd.org, Graham Perrin Subject: Re: Unable to boot from internal hard disks on new PC Message-ID: <20221227140807.GE11926@localhost.org> References: <20221227110800.GA11926@localhost.org> <45e305f7a1193cd6eac03dd0a1499e638c26ceda.camel@riseup.net> <20221227124617.GB11926@localhost.org> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) X-TOI-EXPURGATEID: 150726::1672150088-EF7F5A26-8761A2E9/0/0 CLEAN NORMAL X-TOI-MSGID: a3f4bff8-3cc4-4ff2-a777-bf1bc859bf76 X-Rspamd-Queue-Id: 4NhGhb6Kyfz4JyQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3320, ipnet:194.25.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, Dec 27, 2022 at 01:47:49PM +0000, Graham Perrin wrote: > On 27/12/2022 12:46, Johannes-Maria Kaltenbach wrote: > > > > =E2=80=A6 > > > > Output from efibootmgr: > > +Boot000B* UEFI: USB 2.0 PENDRIVE 1.0, Partition 1 > > Boot0008* UEFI OS > > Boot0002* UEFI: HTTP IPv4 Realtek PCIe GBE Family Controller > > Boot0003* UEFI: PXE IPv4 Realtek PCIe GBE Family Controller > > Boot0004* UEFI: HTTP IPv6 Realtek PCIe GBE Family Controller > > Boot000A* UEFI: PXE IPv6 Realtek PCIe GBE Family Controller > > > > (-b 000b is the installation stick and 0008 the other stick I tested; b= oth no problem) > > > > =E2=80=A6 > > > If the intention is to use the EFI system partition at ada0p2, and if > the operating system at ada0p4 is still bootable, and if you'll not boot that's what I wanted, but I never could boot from ada0 (or another ada#, only from da0 and da1). ada0p4 still contains the system installed from Boot000B, i. e. =66rom the USB with FreeBSD-13.1-RELEASE-amd64-memstick.img . I can still boot from Boot000B. > from the network: you can safely delete unwanted entries. yes, I do not boot from the network; so does that mean that I could delete Boot0002, Boot0003, Boot0004 and Boot000A? > If Boot0008 is mysterious, you could try activating it (and then Boot0008 is not mysterious; it's another USB containing a copy of the system of my old PC and I can boot this also. So I can boot from USB (da[01]), but not from the internal disks (ada[0-3]). > restarting the computer) to tell whether it's usable in relation to your > installation of FreeBSD. > > Things here are very sparse, enough for FreeBSD to boot: > > root@mowa219-gjp4-8570p-freebsd:~ # efibootmgr > Boot to FW : false > BootCurrent: 0000 > Timeout =C2=A0=C2=A0=C2=A0: 5 seconds > root@mowa219-gjp4-8570p-freebsd:~ # I tried to add ada0 using efibootmgr -a -c -l /mnt/efi/boot/BOOTx64.efi -L FreeBSD-13 that created an entry Boot0000* FreeBSD-13 but I didn't see a corresponding entry in bios after reboot and the system booted again from 000b. Best regards, Johannes-Maria