@stephenw10 Thanks very much for that.
I did the upgrade and have not had the issue since.
I did try looking for instructions on how to do this, but Google was not very helpful with the terms that I used.
Either way, thanks again for the help.
sorry, my mistake. i had another drive (empty but normally mounted) that was the real problem, not zfs. i removed it from fstab and the system boot completed.
again sorry for the false alarm...
@stephenw10 thanks for responding -- yup pfSense update solved this particular issue. Now I'm running into TLS/ cert issues on my dockerized graylog setup, which is probably outside the scope of this forum.
Would be nice to have a standard way to securely manage logs in Pfsense -- one that does not encourage people to send logs in the clear.
I know you can just run a local server and have some security with Rules, but would suggest to have a more formal secure integration with Graylog given how popular it seems to be with people here. Also for people that want to monitor more than one network with one Graylog instance
@Gertjan thanks for the info, I got brave yesterday and ordered this one...
APC Back-UPS 600VA, 120V, 1 USB charging port, 7 NEMA outlets (2 surge)
BE600M1
@stephenw10 I set a session timeout of 10 minutes. I have never entered a value in that field before. Logged back in after it timed out, cleared the session timeout field. This morning the login page came up normally.
Yes and you can set it to import only the aliases in the import utility so you don't mess up your config.
Use "Restore Area"
[image: 1721240177107-screenshot-2024-07-17-at-11.15.07.png]