I have these lines in loader.conf for the GhostBSD live image. mfsroot_load="YES" mfsroot_type="md_image" mfsroot_name="/data/ramdisk.ufs" vfs.root.mountfrom="ufs:/dev/md0" The mount worked on our April build but is no longer botting on our August 6 snapshot build on legacy boot. The code is from 14/stable, and the snapshot is from August 6. The error is that it can't mount ufs:/dev/md0. It stops at the mount prompt on the legacy boot, but it works perfectly on the EFI boot. I have tried to find what could have caused that issue on the freebsd-src 14/stable between April and August 6, and I cannot find anything. I will be testing this on a new snapshot, but I thought I would report it immediately in case it is not fixed.
So if I understand correctly, stable/14 as of April booted with those lines, while stable/14 as of August 6th does not. Is that correct? Can you flesh out a little more what one could use to reproduce the problem? How are you creating the image, what VM are you using (or bare metal), etc. I'd like to reproduce to confirm what's going on, and doing a bisection run would would likely be next if there's nothing suggesting itself immediately for why legacy would break.
(In reply to Warner Losh from comment #1) I use https://github.com/ghostbsd/ghostbsd-build; it is built to work only from the GhostBSD repository. Here is the last merge from FreeBSD https://github.com/ghostbsd/ghostbsd-src/pull/335. I have a ThinkPad T530. It usually boots on EFI, but I switched it to legacy boot to test the issue when some users reported their VMs and systems were not booting in legacy boot. We now use PKGBASE, and the 22.04.2 ISO booted fine on the legacy boot. I have been trying to find what could have caused that, but I can't find it. I am about to make a change to build GhostBSD without a desktop and point ghostbsd-build for FreeBSD PKGBASE and test the new packages. It will save me time to test if the latest changes still do that or if they are fixed.
Created attachment 253388 [details] Picture of the issue on the latest FrreeBSD base. I built an ISO with the latest packages from https://pkg.freebsd.org/FreeBSD:14:amd64/base_latest/. I took a picture of the error of that build and attached it as a JPEG.
I have built one with the release from https://pkg.freebsd.org/FreeBSD:14:amd64/base_release_1/, and it is booting fine, so the issue is probably near. After the release, I will try to narrow it down more.
OK, I did a build from the last commit on July 28, and it booted fine. From there, I started building the latest commit each day. Right now, I am building from August 1.
I was not able to test the August 01 build before now. The issue was introduced that day, so now I am looking at all the commits to see if I can find the problem.
I did build from https://github.com/ghostbsd/ghostbsd-src/commits/stable/14/?after=ec012e2cfba2ce148a5f3edf0d7cd3ba026a8922+139 this commit 1755b9d
OK, I think I have found the issue https://github.com/ghostbsd/ghostbsd-src/commit/b56cb540dbfa5d0d79240eb9f28f333d7d231e48#diff-2b9edc3289cd66dbec13f60fbaf9e08260246cd95596a4226c16cfa81e66bae8R10. /data/ramdisk.ufs is a gzip file.
I made a PR on my side: https://github.com/ghostbsd/ghostbsd-src/pull/342. I will let CI run and make a build tomorrow, and if it boots fine, I will close this ticket.
OK, this is fixed on the GHsotBSD side. I am closing this work as intended since we don't want this by default in FreeBSD.