Hard drive activity light on solid after upgrade to 2.4.0

Bent82

Yeah I sort of figured that, I was assuming my write speed would be more than .17 MB/s :)

After I posted all that, I had started looking into the logs. I see a lot of things being logged into the firewall log that look like this?:

  Oct 13 15:54:21  LAN      [fe80::9af1:70ff:fe46:d201]:5353	     [ff02::fb]:5353	 UDP

All of them are using IPv6, which I thought I had disabled, but I couldn't find where I initially configured that years ago just yet. All of them are on UDP and to either port 5353 or 5355. They show up on both the LAN interface or bridge0, which is a bridge I created for a OpenVPN TAP connection, though nobody is currently connected to the VPN. I have never seen this before and I'm not sure what I have going on.

At this point I don't seem to have a hardware issue, so maybe this post should be moved?

johnpoz

5353 is mdns.. Most likely just utter noise if your not running ipv6.. So either disable ipv6 at the clients sending it.. Or set it not to log that nonsense.

5355 would be LLMNR.. Yet again a noisy nonsense multicast name resolution protocol that could just be turned off at the client if your not actively using it.

You have windows machines I take it - they are some noisy POS if you ask me ;)

Bent82

Yeah pretty much exclusively Windows. Nothing else has changed in my network in the past day, the new pfSense version is the only thing. I wonder why the sudden increase in logging, and with it disk activity? My desk is right next to the box so I know the old version didn't light the disk like this. I'll look into ignoring the logging for those items on Monday, thanks.

Bent82

I think I need a little more help in figuring this all out. When I click on the X next to the log entry to find out why it is being blocked, I see this message:

The rule that triggered this action is:
@7(1000105585) block drop in log inet6 all label "Default deny rule IPv6"

But when I go to my firewall rules, under LAN rules I see:

 0 /0 B IPv6 *  LAN net  *  *  *  *  none     Default allow LAN IPv6 to any rule

That was the only related rule I see and to me it appears to be allowing IPv6 traffic on the LAN interface, not blocking. Am I understanding how this works wrong, or is there an issue?

jimp

Check the main IPv6 switch at System > Advanced, Networking tab.

If "Allow IPv6" is unchecked it doesn't matter what IPv6 rules you add, it will be blocked by default.

Bent82

Hmm. Allow IPv6 is checked.

Bent82

So it seems I stumped everyone! I didn't have any more time to look at this today but need to see if I can figure this out again tomorrow. Any other ideas where I should look for issues?

Bent82

I found the issue, seems I was on the wrong track. Unplugging my CD-ROM drive made the light go off and now I see normal activity. Seems for some reason the system was constantly checking the status of the drive, and this made the hard drive activity light light up for some reason. I am open to suggestions on how to stop this, but I obviously don't have a major issue and I can either ignore it or unplug the seldom-used optical drive.

jimp

@Bent82:

I found the issue, seems I was on the wrong track. Unplugging my CD-ROM drive made the light go off and now I see normal activity. Seems for some reason the system was constantly checking the status of the drive, and this made the hard drive activity light light up for some reason. I am open to suggestions on how to stop this, but I obviously don't have a major issue and I can either ignore it or unplug the seldom-used optical drive.

Probably SNMP. See https://redmine.pfsense.org/issues/6882

Bent82

Yep, that looks like it. I plugged the optical drive back in and bsnmp starting using a lot of cpu. I hadn't checked that before, guess I should have. Reading the bug report, it seems I can just leave a disc in the drive to work around this for now, and I can confirm it does. For an actual fix, it seems my best bet may be to wait for 2.4.1, correct?

jimp

Unplug the drive, put media in the drive, disable the hostres module in SNMP. Any of those will mitigate the issue. It's solved in 2.4.1 so it should be better after the upgrade.

Bent82

Good deal. I appreciate all the help with the issue jimp!