From nobody Sat Jun 25 21:51:19 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 BF7FE87D73E for ; Sat, 25 Jun 2022 21:51:28 +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 4LVnkR2vJYz4Tn0 for ; Sat, 25 Jun 2022 21:51:27 +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 25PLpKgj017808 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 25 Jun 2022 14:51:20 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 25PLpK7p017807; Sat, 25 Jun 2022 14:51:20 -0700 (PDT) (envelope-from fbsd) Date: Sat, 25 Jun 2022 14:51:19 -0700 From: bob prohaska To: Mark Millard Cc: Free BSD Subject: Re: Mountroot problems on RPi3/aarch64 Message-ID: <20220625215119.GA17770@www.zefox.net> References: <20220602045202.GA44686@www.zefox.net> <1B845A0C-EDDC-407C-96A8-AAF4E92C2A4D@yahoo.com> <20220613153325.GA12588@www.zefox.net> <50CE21C4-CBE5-4ECB-A27E-42B7AAF71822@yahoo.com> <20220619042225.GA2267@www.zefox.net> <3458F90E-CFC9-4B91-8C4A-DD5788239172@yahoo.com> <20220621192448.GA1874@www.zefox.net> <54365257-9DA2-4058-9354-B5D76E7AAC70@yahoo.com> <47AFE262-8425-4A4D-A425-41CF39AA381E@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: <47AFE262-8425-4A4D-A425-41CF39AA381E@yahoo.com> X-Rspamd-Queue-Id: 4LVnkR2vJYz4Tn0 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 [2.16 / 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)[]; R_SPF_NA(0.00)[no SPF record]; NEURAL_SPAM_SHORT(0.34)[0.339]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.92)[0.920]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-arm]; FREEMAIL_TO(0.00)[yahoo.com]; 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 Thu, Jun 23, 2022 at 06:43:24PM -0700, Mark Millard wrote: > There is another checkin to main for superblock handling: > > QUOTE > The branch main has been updated by mckusick: > > URL: https://cgit.FreeBSD.org/src/commit/?id=50dc4c7df4156863148e6a9609c03e852e2aeb35 > Here's the tail of the boot transcript: Root mount waiting for: CAM da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 12345678D558 da0: 40.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors) da0: quirks=0x2 UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) Mounting from ufs:/dev/da0s2a failed with error 22; retrying for 3 more seconds UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) Mounting from ufs:/dev/da0s2a failed with error 22: Invalid fstype. Loader variables: vfs.root.mountfrom=ufs:/dev/da0s2a vfs.root.mountfrom.options=rw Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:zroot/ROOT/default cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> Rebooting using a kernel of: FreeBSD 14.0-CURRENT #74 main-n255816-e26ef41f799: Wed May 25 15:05:14 PDT 2022 bob@www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 stops in single user with: Root mount waiting for: CAM da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 12345678D558 da0: 40.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors) da0: quirks=0x2 Warning: no time-of-day clock registered, system time will not be set accurately Dual Console: Serial Primary, Video Secondary Setting hostuuid: 30303030-3030-3030-3064-626136386435. Setting hostid: 0x5cd40a6a. Starting file system checks: UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) Cannot find file system superblock UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) Cannot find file system superblock Warning! Some of the devices might not be available; retrying Restarting file system checks: UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) Cannot find file system superblock UFS2 superblock failed: fs->fs_csaddr (806456) != cgdmin(fs, 0) (5056) Cannot find file system superblock Unknown error 3; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! 2022-06-25T14:23:46.792050-07:00 - init 1 - - /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: root@:/ # However, simply exiting the single-user shell seems to bring up normal multi-user operation. Network connectivity remains sporadic, but is much helped by an outgoing ping process. Could it be significant that this filesystem was created on June 4, 2020? Thanks for writing! bob prohaska