pfSense/ROOT/default failed to mount with error 5
-
I am having a VERY frustrating issue with pfSense on a Sophos XGS117 hardware. This issue seems to be new as I dont recall having this issue prior to the latest pfSense version.
I'm not sure if this is directly related to pfSense or more a FreeBSD 12 issue, but everytime the firewall is not recoverable and results in the need to completely reinstall. This seems to only be the issue if the power is lost suddenly.
Running latest version of pfSense Plus. if I manually shutdown, the I can restart without issues, however, pull the power cable out and its toast.
I am using ZFS filesystem.pfSense actually boots, but it then fails to MOUNT the pfSense/default partition? See screenshots below.
Any ideas to a fix is greatly appreciated.
Sophos XGS116
64GB SSD (m2)
-
What devices are shown if you enter
?there?What value do you have set (if any) for
kern.cam.boot_delayin the loader? -
@stephenw10 Thanks, I have reflashed the device as I need it for internet. Reinstalled and restored from backup.
Is there a way I can check the boot loader for this with a running device?
-
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.
-
Hi,
I suffered pretty much the same issue,and given this is first google hit thought would update solution for me here in case it helps others.
Exactly the same as here:
https://forum.netgate.com/topic/184135/mounting-failed-with-error-5/7Pfsense Plus power cut (backup exhausted) bad shutdown.
Then failed to start.
Root mount waiting for: CAM (lots)
Then:
Mounting from zfs:Pfsense/ROOT/Default failed with error 5
Error 5, as per screen shots here.Any zpool command gave error
“Invalid file system specification“I pulled PC, pulled drive, booted from USB Pfsense stick.
Pulled hair.
Could not seem to get to bottom of.
Was going to reinstall Pfense (not plus) from USB stick - no drive to be found other than USB (?). Was going to replace drive altogether.Then discovered one post, in a forum, somewhere, which I will link to if ever can find again, talking about BIOS drive settings changed in power cut.
Solution:
Somehow power surge/power cut had changed BIOS to RAID for drives from AHCI. (interestingly did so for another PC I discovered later - Pfsense was first job - this was Windows PC and failed to Boot altogether)
Oddly here though - Pfsense partially booted - as above so for drive was readable for parts…. (Hence hadn’t considered drive issue)Solution:
Check BIOS Settings
Hard Drives - Selection - AHCI. (not RAID)Hopefully this helps someone else in the future.
