From nobody Wed Jun 01 21:44:01 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 DA26C1B5AC50 for ; Wed, 1 Jun 2022 21:44:04 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LD2hz4M0Mz4pTt for ; Wed, 1 Jun 2022 21:44:03 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 251Li1jB042525 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 1 Jun 2022 14:44:02 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 251Li14I042524 for freebsd-arm@freebsd.org; Wed, 1 Jun 2022 14:44:01 -0700 (PDT) (envelope-from fbsd) Date: Wed, 1 Jun 2022 14:44:01 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Mountroot problems on RPi3/aarch64 Message-ID: <20220601214401.GA42494@www.zefox.net> References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> X-Rspamd-Queue-Id: 4LD2hz4M0Mz4pTt X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-0.95 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[zefox.net]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.85)[-0.850]; MLMMJ_DEST(0.00)[freebsd-arm]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-ThisMailContainsUnwantedMimeParts: N 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.