From nobody Wed Jun 1 21:45:51 2022 X-Original-To: freebsd-arm@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 2BC1F1B5B1A8 for ; Wed, 1 Jun 2022 21:46:03 +0000 (UTC) (envelope-from irontree043111@gmail.com) Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 4LD2lG3t1Yz4pst for ; Wed, 1 Jun 2022 21:46:02 +0000 (UTC) (envelope-from irontree043111@gmail.com) Received: by mail-yb1-xb2d.google.com with SMTP id w2so5178831ybi.7 for ; Wed, 01 Jun 2022 14:46:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SS95ZzxBdzPlGyzqK3bMOXBj/OWetyTwI05MjjuGmN8=; b=UuvwvggLfobps/q7wvFJ2dFeunZMdWAts0P+ddFPvUNfgOXzs32ybYrDejrUDtJ+lF br5R/49vpDQM9okcZU959RrEgayXoo2D4DIz73mFdAiAuUoGsFUMfL+g81B8vCRvLZnE 3Rwz4JSXP8q2BIysPmn/UYamYaP2secCTDX+vNO/Aef+5inp/3c/UONP5vwBzUC2tnmH kUTPMeoyeM5o3FHODQiph5oJeD19R2HMbgKF5KHgbx1U2GDE5IPdFJVMe6O79/JfeZJs mpGRqqNV0Z0caCuDUxBRYH8MJeVcH8JilW+16fgkd9xI+ntbR1CXUDzJAYYdbjETXdVu wB4w== 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=SS95ZzxBdzPlGyzqK3bMOXBj/OWetyTwI05MjjuGmN8=; b=MImxIyyUUHXt9A5zuZuHmC5z1NJdyW/iuhLHcKo/61RLdV1T0gTQ4qA+HGBjWsl0xi Ay+yiaPuseKhh2E17saMh99WrOWyKqr1dGctSpgFea/sJ4xLIz8cdYO+yLvG5nrOk2xh FLj1mp3sV1qE53w4rsYRyjrOoKR6iJI1kPpapmOtuUHc5qoDesIpkLlOw8rJuEY45WIs 6/y09xEYccXZS92o8FQlq+/pYNd7M9vLLO9/dS8MRaHyKY4ik313JqebHn2zpNgkAKZd d/El72+T3DFntX951dKffR4HszB1dg38+AJkICYfcJAoQv+i7U/YTySbL3ZBy3E7tgXv WGPw== X-Gm-Message-State: AOAM5302fK5JUx7Fk5I4GjbP1jJgkAr6r0vSwWmDvLU1w3c/oNd/Yq2z 6XBNa69hovZ56qchlAp536g5USIP5wIblsM/2VE3I8oguZKLXw== X-Google-Smtp-Source: ABdhPJw4ox0fFp0ec8m1qH4t9CPWCFU56gSj9pw58BqKgHKPs00Mbcercr5Um6koDndbA2Rup2ywR6BHOn8yBgBBomI= X-Received: by 2002:a25:6155:0:b0:65d:3a65:a801 with SMTP id v82-20020a256155000000b0065d3a65a801mr2065840ybb.224.1654119961967; Wed, 01 Jun 2022 14:46:01 -0700 (PDT) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> <20220601214401.GA42494@www.zefox.net> In-Reply-To: <20220601214401.GA42494@www.zefox.net> From: Robert Montano Date: Wed, 1 Jun 2022 14:45:51 -0700 Message-ID: Subject: Re: Mountroot problems on RPi3/aarch64 To: bob prohaska Cc: Free BSD Content-Type: multipart/alternative; boundary="000000000000bfbda105e069d016" X-Rspamd-Queue-Id: 4LD2lG3t1Yz4pst X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=UuvwvggL; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of irontree043111@gmail.com designates 2607:f8b0:4864:20::b2d as permitted sender) smtp.mailfrom=irontree043111@gmail.com X-Spamd-Result: default: False [-3.94 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2d:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm]; NEURAL_HAM_SHORT(-0.94)[-0.938]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N Status: O Content-Length: 4403 Lines: 131 --000000000000bfbda105e069d016 Content-Type: text/plain; charset="UTF-8" I'm a newbie to all of this. Sorry I don't really understand the nomenclature! On Wed, Jun 1, 2022, 2:44 PM bob prohaska wrote: > On Wed, Jun 01, 2022 at 09:17:10AM -0700, Mark Millard wrote: > > On 2022-Jun-1, at 08:41, bob prohaska wrote: > > > > > Since about 05/29 mountroot has been failing on a Pi3 self-hosting > -current, > > > using a usb mechanical hard disk. > > > > > > Anybody else seen this sort of behavior? > > > > You do not report much context. FreeBSD version? UFS? ZFS? > > -current, UFS. > > > > > However, there has been today (for main): > > > > git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integrity > checks when reading a superblock > > > > that is for fixing boot problems in UFS contexts. See: > > > > > https://lists.freebsd.org/archives/dev-commits-src-main/2022-June/006977.html > > > > This is for fixes related to the 2022-May-27 change: > > > > ??? git: 076002f24d35 - main - Do comprehensive UFS/FFS superblock > integrity checks when reading a superblock. Kirk McKusick > > > > It sounds like there's some hope the trouble isn't purely local to my > machines. I'll just continue to update and hope for the best. A Pi3 > running -current as well as a Pi3 running stable/13 seem to be affected. > A Pi4 running -current works perfectly. All use UFS on mechanical > hard disks. > > FWIW, one boot attempt followed the mountroot failure > with a kernel panic and backtrace, but I inadvertently wiped > out the console transcript before I could post it. If that > happens again I'll take more care. > > Thanks to everyone who replied, especially Mark! > > bob > > > > it. > > --000000000000bfbda105e069d016 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm a newbie to all of this. Sorry I don't really= understand the nomenclature!

=

On Wed, Jun 1, 2022, 2:44 PM bob prohaska <fbsd@www.zefox.net> wrote:
On Wed, Jun 01, 2022 at 09:17:10AM -0700, Mark Millard wr= ote:
> On 2022-Jun-1, at 08:41, bob prohaska <fbsd@www.zefox.net> w= rote:
>
> > Since about 05/29 mountroot has been failing on a Pi3 self-hostin= g -current,
> > using a usb mechanical hard disk.=C2=A0
> >
> > Anybody else seen this sort of behavior?
>
> You do not report much context. FreeBSD version? UFS? ZFS?

-current, UFS.

>
> However, there has been today (for main):
>
> git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integri= ty checks when reading a superblock
>
> that is for fixing boot problems in UFS contexts. See:
>
> https:/= /lists.freebsd.org/archives/dev-commits-src-main/2022-June/006977.html<= br> >
> This is for fixes related to the 2022-May-27 change:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0??? git: 076002f24d35 - main - Do comprehens= ive UFS/FFS superblock integrity checks when reading a superblock. Kirk McK= usick
>

It sounds like there's some hope the trouble isn't purely local to = my
machines. I'll just continue to update and hope for the best. A Pi3
running -current as well as a Pi3 running stable/13 seem to be affected. A Pi4 running -current works perfectly. All use UFS on mechanical
hard disks.

FWIW, one boot attempt followed the mountroot failure
with a kernel panic and backtrace, but I inadvertently wiped
out the console transcript before I could post it. If that
happens again I'll take more care.

Thanks to everyone who replied, especially Mark!

bob



it.

--000000000000bfbda105e069d016--