From nobody Wed Jun 15 00:04:38 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 C21FB838A12 for ; Wed, 15 Jun 2022 00:04:48 +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 4LN5CM2qrLz3LKX for ; Wed, 15 Jun 2022 00:04:47 +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 25F04dqb020176 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 14 Jun 2022 17:04:39 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 25F04c0i020175; Tue, 14 Jun 2022 17:04:38 -0700 (PDT) (envelope-from fbsd) Date: Tue, 14 Jun 2022 17:04:38 -0700 From: bob prohaska To: Ronald Klop Cc: Mark Millard , freebsd-arm@freebsd.org Subject: Re: Mountroot problems on RPi3/aarch64 Message-ID: <20220615000438.GA19936@www.zefox.net> References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> <20220601214401.GA42494@www.zefox.net> <20220602045202.GA44686@www.zefox.net> <1B845A0C-EDDC-407C-96A8-AAF4E92C2A4D@yahoo.com> <20220613153325.GA12588@www.zefox.net> 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: X-Rspamd-Queue-Id: 4LN5CM2qrLz3LKX 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.92 / 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)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.83)[-0.827]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; 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]; FREEMAIL_CC(0.00)[yahoo.com,freebsd.org]; MID_RHS_WWW(0.50)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Tue, Jun 14, 2022 at 07:58:41PM +0200, Ronald Klop wrote: [big snip] > > Do you have a mix up with labels and partitions/slices on your disk? Could it be that a label was written over a filesystem and instead of mounting from the label your are mounting the corrupted filesystem. > If I understand your question, the answer is "no": /etc/fstab contains: bob@www:/usr/src % cat /etc/fstab # Custom /etc/fstab for FreeBSD embedded images #/dev/ufs/rootfs / ufs rw 1 1 /dev/da0s2a / ufs rw 1 1 /dev/da0s2b none swap sw #/dev/mmcsd0s2b none swap sw #/dev/msdosfs/MSDOSBOOT /boot/msdos msdosfs rw,noatime 0 0 /dev/da0s1 /boot/msdos msdosfs rw,noatime 0 0 #tmpfs /tmp tmpfs rw,mode=1777,size=50m 0 0 Once u-boot finds the USB disk, I use run bootcmd_usb0 to boot it. There is a microSD card in the slot, with a bootable 13.1-RC4 image on it, but AFAIK it doesn't come into play once u-boot finds the USB storage device and is told to boot that. Far as I can tell the USB filesystem isn't corrupt, but if it does get corrupted the -current version of fsck on the USB device still has problems finding superblocks. If I boot from the microSD card and use that system to run fsck it has no problem running fsck on the USB filesystem. The filesystem was created in June 2020, could that be incompatible with the recent changes to UFS? It's maybe worth noting that both -current and stable/13 behaved similary until a few days ago. Stable/13 became able to mountroot again hands-off, -current is still having trouble. The -current machine uses an ASMT usb-sata bridge, the stable/13 box uses a Jmicron bridge. Both hosts use Seagate Barracuda 1 TB mechanical disks. Thanks for writing! bob prohaska