The mfs_load loader.conf setting and recent FreeBSD

N

Nasrudin

FreeBSD 13.4-STABLE and in loader.conf I have:
Code: 
mfs_load="YES"
mfs_type="mfs_root"
mfs_name="/mfsboot"

I'm doing an ISO boot off of a DVD here. This process (which worked flawlessly on 13.3-STABLE) now fails on cloud servers ... but works on bare metal. ?

The error on cloud servers is:
Code: 
can't find '/mfsboot'
but if I escape to loader prompt and ls I see /mfsboot.gz there just the same.

Again, this methodology worked fine at 13.3 for both cloud and bare metal. Does anyone have any insight into this issue? Thanks in advance.
 
Some more data on this issue.

The "cloud vs bare" idea is likely a bad distinction. I make a hybrid boot to support both old school BIOS and new school UEFI booting for my ISO. So I noticed on one of my bare metal machines that I had something called "compatibility support module" enabled, which apparently gives me old BIOS behavior. With that switched on, I get the error described above. With that switched off, it boots normally.
 
So - if you turn CSM OFF, it works? i.e. non-legacy support means it works - which points to it only working with UEFI on 13.4 (which isn't quite released yet - only RC3?)

But are you saying it worked either way CSM or not - on 13.3?

I don't have the answer, just trying to understand what the problem is.
 
To clarify:

- I'm working with a very recent 13.4-STABLE (1ec3289e48) and previous DVDs I made were from 13.3-STABLE (d823e80ef5).
- On my desktop, if I turn CSM OFF this 13.4 works, but 13.3 worked with it on (I didn't test off and 13.3, my desktop is pretty old).
- This 13.4 does not work at Vultr via custom ISO, but the 13.3 did.
 
You must log in or register to reply here.
Back
Top