Hard drive activity light on solid after upgrade to 2.4.0
-
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.
-
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 ruleThat 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?
-
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.
-
Hmm. Allow IPv6 is checked.
-
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?
-
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.
-
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
-
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?
-
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.
-
Good deal. I appreciate all the help with the issue jimp!
