Stuck at Mountroot>

chpalmer

This is 2.7 related but I figure it is good for any recent version..

I am trying to load via a 4G CF card due to my install stopping at actually this exact place on that disk as of a couple updates ago.. I believe this is related to the hard drive stilll?? How do I wipe that drive and start from scratch? XTM5 box..

ada0 at ahcich0 bus 0 scbus1 target 0 lun 0
ada0: <WDC WD3200BEKT-00PVMT0 01.01A01> ATA8-ACS SATA 2.x device
ada0: Serial Number WD-WX91A8219759
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 305245MB (625142448 512 byte sectors)
Root mount waiting for: usbus4 ada
Root mount waiting for: usbus4
Root mount waiting for: usbus4
uhub3: 8 ports with 8 removable, self powered

Loader variables:
vfs.root.mountfrom=zfs:pfSense/ROOT/default

Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.

eg. ufs:/dev/da0s1a
    zfs:zroot/ROOT/default
    cd9660:/dev/cd0 ro
      (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input

mountroot>

PS.. this box will not allow me to load via a USB memory stick..

cursixx

Starting with 2.7 dev build 10.07 I'm getting a loader variables error and the load stops. Tried 10.11 this morning with the same issue. I also noticed the dev channel is not updating after 10.06 and the latest build is missing in the daily snapshot package repository but pfSense shows the latest snapshot and will update the build but gives the below error while loading.

Loader variables:
vfs.root.mountfrom=zfs:pfSense/ROOT/default
Manual root filesystem specification
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.

eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

? list valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input

mountroot>

stephenw10

There is currently an issue with the loader values not being added correctly we are investigating.
You can probably work around that by escaping to the loader prompt and then running:

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

It should then boot normally. Then add the lines back to loader.conf:

opensolaris_load="YES"
zfs_load="YES"

Steve

chpalmer

@stephenw10 said in Stuck at Mountroot>:

zfs_load="YES"

Thanks Steve! Im back in. One of these days I do have to figure out how to load this guy from scratch without having to transfer the drive.. ;)

stephenw10

If you flash the unlocked BIOS it will boot from USB and install like any standard appliance.

Steve

knight-of-ni

@stephenw10 said in Stuck at Mountroot>:

There is currently an issue with the loader values not being added correctly we are investigating.
You can probably work around that by escaping to the loader prompt and then running:
load /boot/kernel/kernel
load /boot/kernel/opensolaris.ko
load /boot/kernel/zfs.ko
boot
It should then boot normally. Then add the lines back to loader.conf:
opensolaris_load="YES"
zfs_load="YES"
Steve

Thank you, Sir.
I am testing 2.7 snapshot on new hardware with i226 nics when I ran into this boot issue, after trying to upgrade to a newer snapshot.

This workaround got me up and going again!

knight-of-ni

UPDATE:
I just upgraded to 2.7.0.a.20221017.0600 this morning, and did not have to apply the workaround. The ZFS driver was correctly re-inserted into loader.conf during the upgrade.

justmeusingpfsense

@stephenw10 Hello sir, i'm still stuck also after using your method, i have another error, error 97

Do you have any idea on how to solve this?
Thanks in advance!

stephenw10

If you enter ? there what does it show?

justmeusingpfsense

@stephenw10 This is the output of ?

And this is the output of ENTER

stephenw10

Hmm, so it's showing that whilst booting the installer?

That would be the USB (da0). Do you see any other drives listed in the boot logs above that?

Steve

justmeusingpfsense

@stephenw10 No sir, that's all i can see.

stephenw10

Ok but that is whilst booting the installer from USB or after installing?

What sort of drive is in that system you are trying to install to?

pfsvrb

@stephenw10
I had a virtualbox install of pfSense 2.5.1 installed on ZFS that I tried to upgrade this morning to the latest Development 2.7.0 snapshot. Unfortunately on rebooting for the upgrade I hit this same error.

stephenw10

Hmm, that looks like it's only seeing the drive sometime after it tries to mount root for some reason.

jimp

Looks like it isn't loading the ZFS kernel module since it says ZFS is an unknown filesystem.

Might be one you need to break out at a loader prompt and load the module manually, and then add it to loader.conf.local once you boot.