USB disk attaches late in 13.1-BETA1

I have a USB SSD drive attached to a Raspberry Pi 4 that has been running
13.0 and 14-CURRENT.  The drive is not the root, and is mounted from
/etc/fstab.  I just booted 13.1-BETA1 on it and set it up as I usually do.
Now the system fails to check the filesystem from the USB disk during the
fsck, so goes to single user.  Then the disk attaches.  That portion of
the console output with the failure is appended.

I had been running a fairly recent -current without problems.  I just
tested the March 3 snapshot of -current; it works too.

Anyone have any idea what is different?  Are there changes in the USB
stack that would cause timing changes?

		Mike

Copied and pasted from console:

Can't stat /dev/da0p1: No such file or directory
/dev/da0p1: CANNOT STAT /dev/da0p1: No such file or directory

/dev/da0p1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
        ufs: /dev/da0p1 (/mnt)
Automatic file system check failed; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
2022-03-09T22:29:15.629342-06: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: uhub1: 4 ports with 4 removable, self powered
usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ADATA SD600Q (0x125f:0xa88a)
usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage device ADATA SD600Q (0x125f:0xa88a)
ugen0.3: <ADATA SD600Q> at usbus0
umass0 on uhub0
umass0: <ADATA SD600Q, class 0/0, rev 3.00/93.01, addr 2> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:0:0: Attached to scbus0
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
da0: <ADATA SD600Q 9301> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 40118905201B
da0: 400.000MB/s transfers
da0: 228936MB (468862128 512 byte sectors)