pfSense

FYI this situation is re-occurring on current 2.4.4 dev snapshots. (The problem started in the last week.)

It can be fixed with the workaround above and the aforementioned additions to /boot/loader.conf, which unfortunately currently get overwritten on updates to newer snapshots.

Satadru Pramanik wrote:

FYI this situation is re-occurring on current 2.4.4 dev snapshots. (The problem started in the last week.)

It can be fixed with the workaround above and the aforementioned additions to /boot/loader.conf, which unfortunately currently get overwritten on updates to newer snapshots.

I've pushed a fix to prevent update to overwrite loader.conf

Renato Botelho wrote:

I've pushed a fix to prevent update to overwrite loader.conf

Thanks.

As a point of clarification, should the following be in the loader.conf by default?

opensolaris_load="YES"
zfs_load="YES"

I hit this issue as well.

The workaround was to trigger the loader mode on bootup, then enter the commands:

load /boot/kernel/kernel
load /boot/kernel/opensolaris.ko
load /boot/kernel/zfs.ko
boot

However, the above comment seems to imply this is fixed - however, I've just updated to the 2018-07-21 nightly build, and it's still hanging on boot with "Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file system".

Is this expected?

Or is the latest build meant to fix this issue automatically, or are we meant to do something manually to fix the issue?

Victor Hooi wrote:

I hit this issue as well.

The workaround was to trigger the loader mode on bootup, then enter the commands:

load /boot/kernel/kernel
load /boot/kernel/opensolaris.ko
load /boot/kernel/zfs.ko
boot

However, the above comment seems to imply this is fixed - however, I've just updated to the 2018-07-21 nightly build, and it's still hanging on boot with "Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file system".

Is this expected?

Or is the latest build meant to fix this issue automatically, or are we meant to do something manually to fix the issue?

does your /boot/loader.conf contain

opensolaris_load="YES"
zfs_load="YES"

??

If you upgraded to a snapshot that clobbered your /boot/loader.conf contents then you would need to re-add the zfs_load="YES" line to /boot/loader.conf manually. Those upgrading from before the problem time to now will be OK. Those upgrading from the problematic snapshots who repaired their loader.conf will be OK.

Jim Pingle wrote:

If you upgraded to a snapshot that clobbered your /boot/loader.conf contents then you would need to re-add the zfs_load="YES" line to /boot/loader.conf manually. Those upgrading from before the problem time to now will be OK. Those upgrading from the problematic snapshots who repaired their loader.conf will be OK.

Thanks.

I googled the error when I first saw this problem, saw this thread, and added

opensolaris_load="YES"
zfs_load="YES"

to my loader.conf, and since it is being preserved, I've had no further problems (with this) since...

Got it - thanks for clarifying, Jim.

I added those two lines to the bottom of my /boot/loader.conf:

opensolaris_load="YES"
zfs_load="YES"

However, you're saying I only need the zfs_load line, right? I can take out the opensolaris_load line.

The joys of living on the bleeding edge, haha.

Having both won't hurt anything, but you only need zfs_load="YES" in loader.conf