Regression #13550
closedPfsense 2.7 October 7 Snapshot manualmount, failed boot
0%
Description
Pulled October 7th Snapshot fails to boot and stops as manualroot> prompt. none of the options work.
Loader variables:
vfs.root. mount from=zfs: pfSense3/ROOT /de fault
Manual root filesystem specification:
(fstype>: <device> [options]
Mount <device> using filesystem <fstupe> and with the specified (optional) option list.
eg. ufs: /dev/daßsla
2fs: zroot/ROOT/de fault cd9660:/dev/cd0 ro
(which is equivalent to: mount
-t cd9660 -0 ro /dev/cdo /)
?
List valid disk boot devices
Yield 1 second (for background tasks)
<emptu line>
Abort manual input
mountroot>
Files
Related issues
Updated by RED SKULL about 2 years ago
FYI: I see the October 7th update shows error 404 when attempting to download on pfsense site but is still available on the Pfsense webUI as upgrade path
Updated by Christian McDonald about 2 years ago
Reboot into the loader prompt, press 3 at the pfSense/FreeBSD boot menu
Then run the following
load /boot/kernel/kernel
load /boot/kernel/opensolaris.ko
load /boot/kernel/zfs.ko
boot
Updated by Kris Phillips about 2 years ago
Christian McDonald wrote in #note-2:
Reboot into the loader prompt, press 3 at the pfSense/FreeBSD boot menu
Then run the following
load /boot/kernel/kernel
load /boot/kernel/opensolaris.ko
load /boot/kernel/zfs.ko
exit
Christian,
Is there a fix pending for this in the next build? I can confirm this happens every time I boot 2.7 on the Oct 7th builds and requires manual intervention to boot.
Updated by RED SKULL about 2 years ago
thanks Christian. I found that this is partially correct. the load commands work but you will need to enter the following afterwards instead of 'exit' as 'exit' is not a recognized command:
reloadbe
autoboot
Updated by RED SKULL about 2 years ago
btw, this is also an issue on the latest October 9th build so I will open another ticket
Updated by Jim Pingle about 2 years ago
- Has duplicate Bug #13551: Pfsense 2.7 October 9 Snapshot manualmount, failed boot added
Updated by RED SKULL about 2 years ago
Also noticed that /boot/loader.conf is almost empty and missing the usual params.. Only has this:
autoboot_delay="3"
net.link.ifqmaxlen="128"
vs prior builds that had this:
kern.cam.boot_delay=10000
kern.ipc.nmbclusters="1000000"
kern.ipc.nmbjumbop="524288"
kern.ipc.nmbjumbo9="524288"
opensolaris_load="YES"
zfs_load="YES"
kern.geom.label.gptid.enable="0"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
opensolaris_load="YES"
zfs_load="YES"
autoboot_delay="3"
net.link.ifqmaxlen="128"
Updated by Chris W about 2 years ago
- File Screenshot from 2022-10-15 13-03-36.png Screenshot from 2022-10-15 13-03-36.png added
- File Screenshot from 2022-10-15 13-05-09.png Screenshot from 2022-10-15 13-05-09.png added
- Status changed from New to Resolved
From the Oct 14 snapshot (current latest at the time), this is resolved. The system boots normally, GUI is accessible, and loader.conf is fully populated.
Updated by Jim Pingle almost 2 years ago
- Tracker changed from Bug to Regression
- Target version set to 2.7.0
- Release Notes changed from Default to Force Exclusion