Re: Mountroot problems on RPi3/aarch64

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