Need help - Pfsense hangs while shutting down

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

nthu9280

Well-Known Member
Feb 3, 2016
1,628
498
83
San Antonio, TX
I have this wierd issue with pfsense 2.3.4-Release as well as with 2.3.4 p1. Actually it was rock solid before on 2.3.4 and I tried to apply the patch P1 and trouble started. I wiped out and did a clean install and still has this issue. SMART does not show any errors on the 16gb SSD. My google fu hasn't been of much help. Can't do a clean shutdown & restart but can power off and on and seem to startup fine. Any ideas for troubleshooting?
Appreciate your help.

TIA
~nthu9280



 
Last edited:

RTM

Well-Known Member
Jan 26, 2014
956
359
63
I haven't seen this issue before, but here are some basic suggestions:
- The filesystem was full during upgrade and something messed up, perhaps a full reinstall (again) without installation of any extra packages
- The filesystem has an error, that it needs to fix (which may require giving it enough time in that state)
- The SSD has a weird firmware issue, have you looked for any firmware updates?

Could you give us some extra information about your install? such as:
- What device are you installing it all on?
- Are you installing any extra packages?
- What type of pfsense installation are you doing? nanobsd or regular install? You should not use nanobsd, as it is being removed in pfsense 2.4
 

nthu9280

Well-Known Member
Feb 3, 2016
1,628
498
83
San Antonio, TX
@RTM

This is happening on a fresh install of 2.3.4-Release also.

HW: HP T610 Plus Thin Client with Intel (IBM OEM) PRO/1000 4 x 1GBe NIC
AMD G-T56N CPU, 4GB RAM, 16 GB SATA SSD. Latest BIOS available for the sytem. CPU doesn't break a sweat for my needs. I have a 100/10 internet and OpenVPN performance also more than sufficient.

I was suspecting file system/disk issue too. SMART (log attached) says SSD is healthy. I've wiped and did a reinstalled the behavior continues. Right now I've switched over to my Wifi Router and working on this behind it. Disk, CPU don't show any more than 10% (See attached pix). I initiated the upgrade to 2.3.4 P1 again last night and it's moving really slow after about 10 hours, it's still on 14/133 packages but moving little faster in the last few min. It was 5/133 this morning.

If this update also behaves the same way when it comes time to reboot, I'll put another small SSD I have and try again.

I've read a post some where (freeNAS/freeBSD/pfSense) to stop the watchdogd.
# service watchdogd stop
I'll try that before restart and see if that helps


upload_2017-10-1_8-31-12.png
 

Attachments

SlickNetAaron

Member
Apr 30, 2016
50
13
8
43
I had a similar, but different issue.

Does your network have any DNS servers besides pfsense? Can pfsense use them?

The reason I ask is: I had pfsense running in kvm on what is basically solaris (Syneto storage appliance). If I cleanly shut down pfsense, the host would completely stop responding to any management interfaces (console, ssh, web gui). I would have to hard power off the host. I moved solutions before I figured it out, but it occurred to me that some DNS dependency caused things to hang (like ssh takes forever to answer if it can't do a reverse lookup of the client connecting to it).

After typing this, I doubt that is the issue, but it may be worth poking. I know Freenas would hang up if DNS wasn't working.. In your instance, I do suspect a storage failure as others mention.

Cheers!
 

nthu9280

Well-Known Member
Feb 3, 2016
1,628
498
83
San Antonio, TX
It was storage. I put in a 80GB Intel S3500 SSD and removed the 16GB Apacer SATA SSD that was in the unit. Now this thing is snappy.

Though SMART was reporting as passed, suspecting the LBAs written appears high. Need to look at what was doing so much writing.

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 16777215
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 100 100 050 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0
7 Unknown_SSD_Attribute 0x000b 100 100 050 Pre-fail Always - 0
8 Unknown_SSD_Attribute 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 6310
10 Unknown_SSD_Attribute 0x0013 100 100 050 Pre-fail Always - 0
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 32
168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0
175 Program_Fail_Count_Chip 0x0003 100 100 010 Pre-fail Always - 0
192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 040 100 000 Old_age Always - 40 (Min/Max 30/60)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
240 Unknown_SSD_Attribute 0x0013 100 100 050 Pre-fail Always - 0
160 Unknown_Attribute 0x0000 100 100 010 Old_age Offline - 236
161 Unknown_Attribute 0x0000 100 100 010 Old_age Offline - 236
162 Unknown_Attribute 0x0000 100 100 005 Old_age Offline - 26
163 Unknown_Attribute 0x0000 100 100 001 Old_age Offline - 21040
164 Unknown_Attribute 0x0000 100 100 001 Old_age Offline - 20239
165 Unknown_Attribute 0x0000 100 100 001 Old_age Offline - 20239
241 Total_LBAs_Written 0x0000 100 100 000 Old_age Offline - 7072992731