Re: Mountroot problems on RPi3/aarch64

Reply: Mark Millard : "Re: Mountroot problems on RPi3/aarch64"
In reply to: Mark Millard : "Re: Mountroot problems on RPi3/aarch64"
Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: bob prohaska <fbsd_at_www.zefox.net>
Date: Sat, 25 Jun 2022 21:51:19 UTC
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: <ASMT ASM105x 0> 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<NO_6_BYTE>
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:
  <fstype>:<device> [options]
      Mount <device> using filesystem <fstype>
      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)
  <empty line>    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: <ASMT ASM105x 0> 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<NO_6_BYTE>
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