Created attachment 188488 [details] 11-STABLE boot log With the latest FreeBSD-11.1-STABLE-arm-armv6-RPI-B-20171130-r326381.img, mountroot /dev/ufs/rootfs fails. See attached log. With FreeBSD-11.1-RELEASE-arm-armv6-RPI-B.img it works fine. It seems the recent changes to the u-boot-rpi2 / rpi-firmware infrastructure broke things?
This submittal is a little confusing. You list: FreeBSD-11.1-STABLE-arm-armv6-RPI-B-20171130-r326381.img but mention: u-boot-rpi2 . For RPI2 there is at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224050 (different date as the 20171130 snapshot was apparently not successful) : FreeBSD-11.1-STABLE-arm-armv6-RPI2-20171116-r325866.img.xz Are you deliberately trying to use a build for a older RPI model on an RPI2? The RPI2 also has the V1.1 and before vs. V1.2 and later where the model of arm processors changed from armv7 (corex-A7) to aarch64 (cortex-A53). If an RPI2 is in use, which version is it? That might be important to analyzing any problems.
(In reply to Mark Millard from comment #1) Hmm. Looking at the log attachment it shows things like: RPI Model B+ CPU: ARM ARM1176 r0p7 BCM2835 Interrupt Controller This looks like it is not an RPI2 at all, but is instead an older model. So FreeBSD-11.1-STABLE-arm-armv6-RPI-B looks to be appropriate. But if you have used any material from the u-boot-rpi2 that you mentioned it is possibly inappropriate material. There is: sysutils/u-boot-rpi to get materials from instead. (But your "2" might just have been a typo for all I know.)
(In reply to Mark Millard from comment #2) My bad, the '2' is indeed mistyped. But note that the image files mentioned are all for RPI-B, which is also the model I'm using: Raspberry Pi Model B+ I was just considering that u-boot-rpi (not rpi2) might be related - but there have been also recent changes to RPI-B.conf and the release.sh stuff.
This appears to be fixed by base r322694 (bug #218344). A manually built FreeBSD-11.1-STABLE-arm-armv6-RPI-B-r326951.img boots and mounts the root ufs properly.