pfSense/ROOT/default failed to mount with error 5
-
Yes you can see what it's set to by running:
sysctl kern.cam.boot_delay -
@stephenw10 Thanks output is,
kern.cam.boot_delay: 10000 -
Hmm, not that then.
So it only does this if you hard reset the device? And it does it every time?
-
@stephenw10 Yes, correct.
I have hard reset 3 times, mostly mistakes on my part, and everytime now I have had to reinstall pfSense from scratch as I CANNOT for the life of me get past the mountroot screen.
Seems like if I shut it down gracefully, all is good.
-
Hmm, I've never seen ZFS fail like that without something else in play It's normally very resilient to that.
-
@stephenw10 This just happened again today.
Forced me to throw a Mikrotik in temporarily.
I really need to fix this but not sure where to start.
What could be causing this? Any idea on how to troubleshoot?
-
What pfSense version are you using? 23.09.1/2.7.2 included ZFS fixes.
-
@stephenw10 I was using latest version of pfSense +.
Fully up to date.
-
@stephenw10 Ok, i've had a play with this today and its back in production.
I changed from legacy boot to UEFI, not sure if this will help.
I powered it up and pulled the power several times trying to force the failure, didn't fail to boot once. I do have a feeling its only once there is some data written to the drive, such as firewall logs, trafiic and host data etc. Any way we will see.
Is there any logs while i is running that I can get that may shed more light on this issue?
Thanks!
-
Nothing other than the system log. Any sort of filesystem issue should log an error.
