From nobody Mon May 30 14:06:32 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 1F8B31B549A7 for ; Mon, 30 May 2022 14:06:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (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 4LBcfK2F9Zz3mmq for ; Mon, 30 May 2022 14:06:49 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe32.google.com with SMTP id z6so10947007vsp.0 for ; Mon, 30 May 2022 07:06:49 -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; bh=lOBLt3YBMC5XTWdJSq8B4nPOKB8aIDDqzHOjq1dvzdA=; b=yuB8OszjPsJqY01lr/fjKbRfvFHCxUbgZnBAbC+soCzY+XWDO+i4g4430DZJ92XWXK Y0IQ62MiNeLnJzFIetyO3/DkNfdAa/xLDmSD9HhZ0/1Ue+C9kVzGkHBBFCxl4rxYSIaa 5axO2ZhqTHQhmizgEcusadq8bkfb1hLDEG7xPixRPbsEbGuyhrpGf+VHxn8xFutGAKsh k1yv+sFvOn+jQrw045ZAHh6g0LbKtFP+WU9cc0V4KbyLsoyIqb+h6NbBZJ3T1Z2sLBPv OzvF9lD5AamdizzaTvGOp8ZLFDSqPyl2Gn+iMM2raz/xU9EEg+7VfAZAXaXVOoMy2dDO h+zA== 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; bh=lOBLt3YBMC5XTWdJSq8B4nPOKB8aIDDqzHOjq1dvzdA=; b=Or3bkvIBQtc2QsOzUbFqo3WR4pe+dH5aDCk/OoGku1oxYvgeDsd3n+JAxIGSEihvPB d53eS93Tngsi07I2c7h3epSbMJ9xfMOWXXYRBi2F2sNB6pcp6RIL+r+yzBQkQ2IlVxXH d3hjno5LsC1d8QgYPMV6qnvmaDzqYay0jfK0yNjzgGfPHkj2RCfx8FHlCjtm6NL+CO2+ epzX57aKzQnqMJPSWXhrr7lklt5Wy15/k0Xz5u0zVdCsFDuwRSJE/7qx4BX+aa/tHaXT tMiBKX+kf++2GTV/j1RbmTVgMSYOIfVDVTxP27Zv3u9afhxnfDrWP029NNcooaMUBjVR 1Flg== X-Gm-Message-State: AOAM531riFqOG/fNXqe6pPlfF5Z/EI6/gvRbYCtX5++OdLdK2rkz9M/U E5Dmr+zFFfZAM8GRi2vCIcox/DXRCeYvoKc8/bMMGb4WDI8= X-Google-Smtp-Source: ABdhPJwoGOk36kzyLmrs63iT7CcCULMBeIxNBGBwGcklUjiT4AneAMyluGI6kJq6VFAah66GTNb540Ir2/t/2ASbaO8= X-Received: by 2002:a05:6102:3054:b0:337:cd32:c39e with SMTP id w20-20020a056102305400b00337cd32c39emr13771786vsa.59.1653919603120; Mon, 30 May 2022 07:06:43 -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: In-Reply-To: From: Warner Losh Date: Mon, 30 May 2022 08:06:32 -0600 Message-ID: Subject: Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c To: David Wolfskill , Toomas Soome , FreeBSD Current , Warner Losh Content-Type: multipart/alternative; boundary="0000000000006e6ed905e03b2acb" X-Rspamd-Queue-Id: 4LBcfK2F9Zz3mmq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=yuB8Oszj; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::e32) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-2.86 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.864]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-0.998]; 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::e32:from]; MLMMJ_DEST(0.00)[current]; FREEMAIL_TO(0.00)[catwhisker.org,me.com,freebsd.org,bsdimp.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 --0000000000006e6ed905e03b2acb Content-Type: text/plain; charset="UTF-8" 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 that 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 --0000000000006e6ed905e03b2acb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, May 30, 2022 at 4:26 AM David= Wolfskill <david@catwhisker.org= > 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
--0000000000006e6ed905e03b2acb--