From nobody Mon May 30 14:16:20 2022 X-Original-To: current@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 EAFD61B57CF7 for ; Mon, 30 May 2022 14:16:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LBcsY08TQz3qsb for ; Mon, 30 May 2022 14:16:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe31.google.com with SMTP id 68so10929471vse.11 for ; Mon, 30 May 2022 07:16:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2p1GsMG2IfHrQrwm21FTNrPYXGnD6sLcZaDR4RXf8vo=; b=0tCPcCYtx2Nlz7MbDOJY89f5QTvMuKdSjRxUnDQSJgi08beN4/0vwModYGBmJnSM6a gG6SR7v/FDrcYB436kr+342WjjGwr5Tlb0KbIY3qGQHFLT/Sp2zYNEmn/2GYimnFVsj9 W1y9fv/bgot/V/dyGGKazG/A2sYvOFXUtiWY22mctN+YXs8ax9d25s7UApPztk+LzGdx vuIRzoYfckqjiCcFHRNEWGLh2RNj/ZmOtpnl7Z6FloOQ64545PBHgUVq/6RXUQSeJmHy r2tyKEHZrnuUXbibs5T4WKoK7XnSr5RExMizTMNz2tUY0RrevAXCOQuRNQDvhLGei82B IocA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2p1GsMG2IfHrQrwm21FTNrPYXGnD6sLcZaDR4RXf8vo=; b=bQPUDNYDHsiwcsKoq5n6JAafQDm6ATXs0EaVKQxVWq/3UGPA5cI1XiSq1K/TB9tWpi k2gqAcpJCRwDrfo3zbUbR0X8HW3m7dDqm2HVYBSNEVgrvWuGBARq7zvwW1f+911YnjIm rDU+1dgpNvROTGbWj9eRrho7wFwxqbRMkWr2VO/YzmyG51oma1Krzk9fmLlPOLCB3C5v kqBGC5SRiAb3MtgMssaBjOlv6SCNhEKqk+dhabvV+dLEBO6NkZs9ht09ddR0Oe3aW57f Wf4RJyzacZuQtvcnBTOMPzSXTLlYQl0aH3eN+tfiq48VcguEmuzr48aWupe/rY7itK1w xvVQ== X-Gm-Message-State: AOAM5307hKcpDKvI4l9+OXaeTPwKBziyLNeHGIyT/Aezdo6oWy1jCF/d V7PNwIVZWMORKOJGuwmnI1GA3kuHWN9fodNHu03smBvN9MM= X-Google-Smtp-Source: ABdhPJzrONEWGgcBLiAKUsjKMkx2a0ggIpnTwxev1GSkHsg6WSA0x9afBodbXkxnfOemEL4JT0RIwC4O/GM73hu8pzM= X-Received: by 2002:a67:e01b:0:b0:337:9729:acc2 with SMTP id c27-20020a67e01b000000b003379729acc2mr17634848vsl.10.1653920191773; Mon, 30 May 2022 07:16:31 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <7BEE44CC-4D31-4CBC-BC12-9A327424299C@me.com> In-Reply-To: <7BEE44CC-4D31-4CBC-BC12-9A327424299C@me.com> From: Warner Losh Date: Mon, 30 May 2022 08:16:20 -0600 Message-ID: Subject: Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c To: Toomas Soome Cc: David Wolfskill , FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000008495bd05e03b4d42" X-Rspamd-Queue-Id: 4LBcsY08TQz3qsb X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=0tCPcCYt; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::e31) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-2.97 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.973]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::e31:from]; MLMMJ_DEST(0.00)[current]; FREEMAIL_TO(0.00)[me.com]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --0000000000008495bd05e03b4d42 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, May 30, 2022 at 8:14 AM Toomas Soome wrote: > > > On 30. May 2022, at 17:06, Warner Losh wrote: > > > > On Mon, May 30, 2022 at 4:26 AM David Wolfskill > wrote: > >> On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: >> > ... >> > Does loader_4th have same issue? >> > .... >> >> I don't know; I hadn't tried it. I will do so later today & report >> back. >> > > So if it's only one system, and it's only UFS, then what does fsck of tha= t > UFS system tell you? > The loader can't find its UFS filesystem to read the configuration from. > So either its having trouble > finding the device (unlikely since that code hasn't changed in a long > time), or its having heartburn > with the UFS system for some reason it's being silent about (within the > realm of possibilities because > there might be an unknown edge case in Kirks recent UFS integrity > changes). I suspect that the 4th > boot loader will have the same issue, but a different error message. > > Others have reported issues with GELI, but that's not in play here, If I'= m > reading this correctly. Right? > > Warner > > > Ye, thats why I was asking about loader_4th. I=E2=80=99m trying to spot t= he issue > from ufs image sample. > I thought it was a good suggestion. My guess on it not working wasn't to imply it wasn't. Warner --0000000000008495bd05e03b4d42 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, May 30, 2022 at 8:14 AM Tooma= s Soome <tsoome@me.com> wrote:


On 30.= May 2022, at 17:06, Warner Losh <imp@bsdimp.com> wrote:

=


On Mon, May 30, 2022 at 4:26 AM David Wolfskill <david@catwhisker.or= g> wrote:
On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote:
> ...
> Does loader_4th have same issue?
> ....

I don't know; I hadn't tried it.=C2=A0 I will do so later today &am= p; report
back.

So if it's only one system, a= nd it's only UFS, then what does fsck of that UFS system tell you?
The loader can't find its UFS filesystem to read the configuratio= n from. So either its having trouble
finding the device (unlikely= since that code hasn't changed in a long time), or its having heartbur= n
with the UFS system for some reason it's being silent about= (within the realm of possibilities because
there might be an unk= nown edge case in Kirks recent=C2=A0 UFS integrity changes). I suspect that= the 4th
boot loader will have the same issue, but a differen= t=C2=A0error message.

Others have reported issues = with GELI, but that's not in play here, If I'm reading this correct= ly. Right?

Warner

Ye, thats why I was asking about loader_4= th. I=E2=80=99m trying to spot the issue from ufs image sample.=C2=A0
=

I thought it was a good suggestion. = My guess on it not working wasn't to imply it wasn't.
Warner=C2=A0
--0000000000008495bd05e03b4d42--