The drive showing > 100% usage with UFS is not that unusual as UFS has some "extra" space it holds, it just means that it's really full when it hits around what you see there.

Something you have must be holding open a log file somewhere that's consuming the space. If it goes away on reboot then it may be files in /tmp as well. You'd have to inspect the contents of the filesystem when it's close to full to see what is using the space.

https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-usage.html

It's also possible the filesystem has some slight corruption that is making the numbers look off from reality, and running a manual filesystem check may help:

https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html

If/when you do reinstall, you're probably better off moving to ZFS, but that wouldn't help if something is actually filling up the disk.

Yes you could use two 1G links in a lagg. You won't see 2G for a single connection though.

@stephenw10 said in PFsense monitoring (Centralized monitoring) over WAN:

We have our own solution in the works but no ETA for that yet.

You always leaving us on a cliff-hanger 😊

@stephenw10
Interesting..Must be a v9 thing then.

Thanks for checking.

@stephenw10 its gone now I had to reboot all devices since then there has been no more entries like that.

@Thondwe said in Hardware Failure Transfer NDI (question):

And a separate trial option with a 30 day expiration or similar for dev/test/setup check...

This would be great, in the old days (2 weeks ago) I would test things on my old desktop pfSense+, now I cross fingers and hope.

@stephenw10 Thanks so much, Stephen, for your excellent help!

Problem solved. Disk was full....

Took me a few minutes to figure that one out...

I ran into this for the first time last night after running a Gen2 VM for many years. I haven't had time to dive into it, but here is what I noticed.

Windows Server 2022 Standard Gen 2 VM, 4 cores, 4096MB RAM (not dynamic) 2 nics (WAN and LAN) VM version 10 pfSense+ 23.05 First had an issue when I upgraded from 23.05 to 23.09. When it rebooted, it came up with the error. It sat like this for several hours until I could get to it physically. In the boot menu, it had "kernel.old" as an option and that would allow it to boot. "kernel" would cause the error and hang. I installed pfSense 2.7 fresh and after it rebooted, it hung with the error. I noticed that if I messed around with the boot menu - just pressing keys to look at the options - when I pressed enter to continue booting, it would work. The next reboot would hang again. Creating a Gen 1 VM worked fine.

I have been running this VM for years without any upgrade issues. The only thing I changed recently was upgrading the VM version from 9 to 10. I have a backup of it where it is still version 9, so I'll try restoring it and doing the upgrade to see if it still hangs.

@stephenw10 I found an old post to follow settings to enter the External IP to Monitor. That led me astray because Pfsense version changes have moved settings. Anyway, I found it under Status\Gateways\Related Settings (screen top right)\Edit WAN_PPOE\Monitor IP for anybody else looking for it. I'll do a config backup so I don't have to remember the path again!

Hmm, OK. We are looking at it....

@jimp
Gotcha. Thanks for the very quick response.

Sorry that was aimed @Link01. The symptoms they are seeing are common when ramdisks are in use.

@stephenw10
Done.
Appreciate your quick assist on this.

@stephenw10
Thanks for following up, turns out I'd purchased though the subscription in products site, instead of the support tab (facepalm). So that's 100% on me, got ticket open for it and is now resolved. I should have looked harder for the support that asked for the NDI.

Thanks!

@jimp Thanks!

I did a clean install and am back up and running now. Thanks for your quick responses!

@SteveITS

Hello, I wanted to thank you for the help I figured out where I went wrong. Essentially I created the ports added the needed DHCP server setting had all that correct. What I failed to do was allow traffic from the wan to the second LAN port correctly. I had defined in the rules for the LAN2 ports LAN2 -> WAN was okay when in fact I needed to do WAN -> LAN2 okay. Now my DMZ is wokring. All my servers are on the pfSense only and all my other devices behind the router are connected to the pfSense.

@drkpny19 said in New pfSense install good down/bad upload.:

I will do another test when I get home. I’ll make windows desktop the server and pfsense the client,

You can also just use the -R switch to reverse the test direction.

What is the WAN port connected to? What speed is it linked at?

@bushman666
Thank you. This solution perfectly works for me. From 2.6.0 to 2.7.0 upgrade.