FreeNAS 11.1 locking up roughly every 24 hours

Status
Not open for further replies.

theaddies

Contributor
Joined
Mar 28, 2015
Messages
105
I have actually been running FreeNAS for quite sometime. I seem to be one of the lucky ones to have not had a large number of issues. However, because of this I am also a NOOB. I know I need to collect information to help identify the issues, but I don't know where to start. My hardware is very standard as I knew that would help remove a lot of possibilities. Perhaps there is something in the console output posted below. Thanks in advance for the help. I am totally willing and able to work at it. I am just at a loss as to where to start.

E3-1231
24 GB ram
Supermicro MBD-X10SL7-F-O

EDIT: I should also say that I am getting a warning for having 81% of the storage full.

Code:
Dec 15 07:22:34 freenas daemon[3177]:	 2017/12/15 07:22:34 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:24:37 freenas daemon[3177]:	 2017/12/15 07:24:37 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:26:40 freenas daemon[3177]:	 2017/12/15 07:26:40 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:28:43 freenas daemon[3177]:	 2017/12/15 07:28:43 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:30:45 freenas daemon[3177]:	 2017/12/15 07:30:45 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:32:48 freenas daemon[3177]:	 2017/12/15 07:32:48 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:34:51 freenas daemon[3177]:	 2017/12/15 07:34:51 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:36:54 freenas daemon[3177]:	 2017/12/15 07:36:54 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:38:57 freenas daemon[3177]:	 2017/12/15 07:38:57 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:41:00 freenas daemon[3177]:	 2017/12/15 07:41:00 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:43:03 freenas daemon[3177]:	 2017/12/15 07:43:03 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:45:06 freenas daemon[3177]:	 2017/12/15 07:45:06 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:47:09 freenas daemon[3177]:	 2017/12/15 07:47:09 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:49:11 freenas daemon[3177]:	 2017/12/15 07:49:11 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:51:14 freenas daemon[3177]:	 2017/12/15 07:51:14 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:53:17 freenas daemon[3177]:	 2017/12/15 07:53:17 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:55:20 freenas daemon[3177]:	 2017/12/15 07:55:20 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:57:24 freenas daemon[3177]:	 2017/12/15 07:57:24 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 07:59:27 freenas daemon[3177]:	 2017/12/15 07:59:27 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:01:30 freenas daemon[3177]:	 2017/12/15 08:01:30 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:03:33 freenas daemon[3177]:	 2017/12/15 08:03:33 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:05:50 freenas daemon[3177]:	 2017/12/15 08:05:50 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:08:20 freenas daemon[3177]:	 2017/12/15 08:08:20 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 08:10:50 freenas daemon[3177]:	 2017/12/15 08:10:50 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 08:13:07 freenas daemon[3177]:	 2017/12/15 08:13:07 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:15:19 freenas daemon[3177]:	 2017/12/15 08:15:19 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:17:25 freenas daemon[3177]:	 2017/12/15 08:17:25 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:19:28 freenas daemon[3177]:	 2017/12/15 08:19:28 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:21:58 freenas daemon[3177]:	 2017/12/15 08:21:58 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 08:24:28 freenas daemon[3177]:	 2017/12/15 08:24:28 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 08:26:58 freenas daemon[3177]:	 2017/12/15 08:26:58 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 08:29:25 freenas daemon[3177]:	 2017/12/15 08:29:25 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:31:36 freenas daemon[3177]:	 2017/12/15 08:31:36 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:33:40 freenas daemon[3177]:	 2017/12/15 08:33:40 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:35:44 freenas daemon[3177]:	 2017/12/15 08:35:44 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:38:02 freenas daemon[3177]:	 2017/12/15 08:38:02 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:40:07 freenas daemon[3177]:	 2017/12/15 08:40:07 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:42:10 freenas daemon[3177]:	 2017/12/15 08:42:10 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:44:14 freenas daemon[3177]:	 2017/12/15 08:44:14 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:46:18 freenas daemon[3177]:	 2017/12/15 08:46:18 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:48:26 freenas daemon[3177]:	 2017/12/15 08:48:26 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:50:29 freenas daemon[3177]:	 2017/12/15 08:50:29 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:52:58 freenas daemon[3177]:	 2017/12/15 08:52:58 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:55:02 freenas daemon[3177]:	 2017/12/15 08:55:02 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:57:06 freenas daemon[3177]:	 2017/12/15 08:57:06 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 08:59:09 freenas daemon[3177]:	 2017/12/15 08:59:09 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:01:12 freenas daemon[3177]:	 2017/12/15 09:01:12 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:03:15 freenas daemon[3177]:	 2017/12/15 09:03:15 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:05:19 freenas daemon[3177]:	 2017/12/15 09:05:19 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:07:24 freenas daemon[3177]:	 2017/12/15 09:07:24 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:09:27 freenas daemon[3177]:	 2017/12/15 09:09:27 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:11:29 freenas daemon[3177]:	 2017/12/15 09:11:29 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:13:32 freenas daemon[3177]:	 2017/12/15 09:13:32 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:15:35 freenas daemon[3177]:	 2017/12/15 09:15:35 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:17:38 freenas daemon[3177]:	 2017/12/15 09:17:38 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:19:41 freenas daemon[3177]:	 2017/12/15 09:19:41 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:21:44 freenas daemon[3177]:	 2017/12/15 09:21:44 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:23:47 freenas daemon[3177]:	 2017/12/15 09:23:47 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:25:51 freenas daemon[3177]:	 2017/12/15 09:25:51 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:27:54 freenas daemon[3177]:	 2017/12/15 09:27:54 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:29:59 freenas daemon[3177]:	 2017/12/15 09:29:59 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:32:02 freenas daemon[3177]:	 2017/12/15 09:32:02 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:34:05 freenas daemon[3177]:	 2017/12/15 09:34:05 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:36:08 freenas daemon[3177]:	 2017/12/15 09:36:08 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:38:11 freenas daemon[3177]:	 2017/12/15 09:38:11 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:40:14 freenas daemon[3177]:	 2017/12/15 09:40:14 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:42:16 freenas daemon[3177]:	 2017/12/15 09:42:16 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:44:21 freenas daemon[3177]:	 2017/12/15 09:44:21 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:46:24 freenas daemon[3177]:	 2017/12/15 09:46:24 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:48:27 freenas daemon[3177]:	 2017/12/15 09:48:27 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:50:30 freenas daemon[3177]:	 2017/12/15 09:50:30 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:52:38 freenas daemon[3177]:	 2017/12/15 09:52:38 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:54:41 freenas daemon[3177]:	 2017/12/15 09:54:41 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:56:46 freenas daemon[3177]:	 2017/12/15 09:56:46 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 09:59:08 freenas daemon[3177]:	 2017/12/15 09:59:08 [WARN] agent: Check 'service:nas-health' is now warning
Dec 15 10:01:38 freenas daemon[3177]:	 2017/12/15 10:01:38 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 10:04:09 freenas daemon[3177]:	 2017/12/15 10:04:09 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 10:06:39 freenas daemon[3177]:	 2017/12/15 10:06:39 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 10:09:09 freenas daemon[3177]:	 2017/12/15 10:09:09 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 10:10:57 freenas xhci0: Resetting controller
Dec 15 10:10:57 freenas uhub2: at usbus0, port 1, addr 1 (disconnected)
Dec 15 10:10:57 freenas ugen0.2: <vendor 0x0557 product 0x7000> at usbus0 (disconnected)
Dec 15 10:10:57 freenas uhub5: at uhub2, port 7, addr 1 (disconnected)
Dec 15 10:10:57 freenas ugen0.3: <vendor 0x0557 product 0x2419> at usbus0 (disconnected)
Dec 15 10:10:57 freenas ukbd0: at uhub5, port 1, addr 2 (disconnected)
Dec 15 10:10:57 freenas ukbd0: detached
Dec 15 10:10:57 freenas ums0: at uhub5, port 1, addr 2 (disconnected)
Dec 15 10:10:58 freenas ums0: detached
Dec 15 10:10:58 freenas uhub5: detached
Dec 15 10:10:58 freenas ugen0.4: <CPS CP1500PFCLCD> at usbus0 (disconnected)
Dec 15 10:10:58 freenas ugen0.5: <SanDisk Ultra USB 3.0> at usbus0 (disconnected)
Dec 15 10:10:58 freenas umass0: at uhub2, port 16, addr 4 (disconnected)
Dec 15 10:10:58 freenas da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
Dec 15 10:10:58 freenas da0: <SanDisk Ultra USB 3.0 1.00> s/n 4C530001190909116372 detached
Dec 15 10:10:58 freenas (da0:umass-sim0:0:0:0): Periph destroyed
Dec 15 10:10:58 freenas umass0: detached
Dec 15 10:10:58 freenas ugen0.6: <SanDisk Ultra USB 3.0> at usbus0 (disconnected)
Dec 15 10:10:58 freenas umass1: at uhub2, port 17, addr 5 (disconnected)
Dec 15 10:10:58 freenas da1 at umass-sim1 bus 1 scbus9 target 0 lun 0
Dec 15 10:10:58 freenas da1: <SanDisk Ultra USB 3.0 1.00> s/n 4C530001040809104273 detached
Dec 15 10:10:58 freenas (da1:umass-sim1:1:0:0): Periph destroyed
Dec 15 10:10:58 freenas umass1: detached
Dec 15 10:10:59 freenas xhci0: Port routing mask set to 0xffffffff
Dec 15 10:10:59 freenas uhub2: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Dec 15 10:11:00 freenas uhub2: 17 ports with 17 removable, self powered
Dec 15 10:11:01 freenas ZFS: vdev state changed, pool_guid=16153893611131903492 vdev_guid=14372043713050901659
Dec 15 10:11:02 freenas ugen0.2: <vendor 0x0557 product 0x7000> at usbus0
Dec 15 10:11:02 freenas uhub5 on uhub2
Dec 15 10:11:02 freenas uhub5: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 1> on usbus0
Dec 15 10:11:02 freenas uhub5: 4 ports with 3 removable, self powered
Dec 15 10:11:04 freenas ugen0.3: <vendor 0x0557 product 0x2419> at usbus0
Dec 15 10:11:04 freenas ukbd0 on uhub5
Dec 15 10:11:04 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Dec 15 10:11:04 freenas kbd1 at ukbd0
Dec 15 10:11:05 freenas ums0 on uhub5
Dec 15 10:11:05 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 2> on usbus0
Dec 15 10:11:05 freenas ums0: 3 buttons and [Z] coordinates ID=0
Dec 15 10:11:07 freenas ugen0.4: <CPS CP1500PFCLCD> at usbus0
Dec 15 10:11:11 freenas ugen0.5: <SanDisk Ultra USB 3.0> at usbus0
Dec 15 10:11:11 freenas umass0 on uhub2
Dec 15 10:11:11 freenas umass0: <SanDisk Ultra USB 3.0, class 0/0, rev 3.00/1.00, addr 4> on usbus0
Dec 15 10:11:11 freenas umass0:  SCSI over Bulk-Only; quirks = 0x8100
Dec 15 10:11:11 freenas umass0:8:0: Attached to scbus8
Dec 15 10:11:13 freenas da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
Dec 15 10:11:13 freenas da0: <SanDisk Ultra USB 3.0 1.00> Removable Direct Access SPC-4 SCSI device
Dec 15 10:11:13 freenas da0: Serial Number 4C530001190909116372
Dec 15 10:11:13 freenas da0: 400.000MB/s transfers
Dec 15 10:11:13 freenas da0: 14663MB (30031250 512 byte sectors)
Dec 15 10:11:13 freenas da0: quirks=0x2<NO_6_BYTE>
Dec 15 10:11:13 freenas upsd[2313]: Data for UPS [ups] is stale - check driver
Dec 15 10:11:15 freenas ugen0.6: <SanDisk Ultra USB 3.0> at usbus0
Dec 15 10:11:15 freenas umass1 on uhub2
Dec 15 10:11:15 freenas umass1: <SanDisk Ultra USB 3.0, class 0/0, rev 3.00/1.00, addr 5> on usbus0
Dec 15 10:11:15 freenas umass1:  SCSI over Bulk-Only; quirks = 0x8100
Dec 15 10:11:15 freenas umass1:9:1: Attached to scbus9
Dec 15 10:11:15 freenas da1 at umass-sim1 bus 1 scbus9 target 0 lun 0
Dec 15 10:11:15 freenas da1: <SanDisk Ultra USB 3.0 1.00> Removable Direct Access SPC-4 SCSI device
Dec 15 10:11:15 freenas da1: Serial Number 4C530001040809104273
Dec 15 10:11:15 freenas da1: 400.000MB/s transfers
Dec 15 10:11:15 freenas da1: 14663MB (30031250 512 byte sectors)
Dec 15 10:11:15 freenas da1: quirks=0x2<NO_6_BYTE>
Dec 15 10:11:15 freenas upsd[2313]: UPS [ups] data is no longer stale
Dec 15 10:11:40 freenas daemon[3177]:	 2017/12/15 10:11:40 [WARN] Timed out (30s) running check '/usr/local/etc/consul-checks/freenas_health.sh'
Dec 15 13:37:45 freenas daemon[3177]: ==> Newer Consul version available: 1.0.2 (currently running: 1.0.0)
Dec 15 16:47:22 freenas syslog-ng[1767]: syslog-ng starting up; version='3.7.3'
Dec 15 16:47:22 freenas Copyright (c) 1992-2017 The FreeBSD Project.
Dec 15 16:47:22 freenas Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Dec 15 16:47:22 freenas	 The Regents of the University of California. All rights reserved.
Dec 15 16:47:22 freenas FreeBSD is a registered trademark of The FreeBSD Foundation.
Dec 15 16:47:22 freenas FreeBSD 11.1-STABLE #0 r321665+d4625dcee3e(freenas/11.1-stable): Wed Dec 13 16:33:42 UTC 2017
Dec 15 16:47:22 freenas root@gauntlet:/freenas-11-releng/freenas/_BE/objs/freenas-11-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
Dec 15 16:47:22 freenas FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on LLVM 5.0.0svn)
Dec 15 16:47:22 freenas VT(efifb): resolution 800x600
Dec 15 16:47:22 freenas CPU: Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz (3400.06-MHz K8-class CPU)
Dec 15 16:47:22 freenas Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c  Stepping=3
Dec 15 16:47:22 freenas Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Dec 15 16:47:22 freenas Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
Dec 15 16:47:22 freenas AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
Dec 15 16:47:22 freenas AMD Features2=0x21<LAHF,ABM>
Dec 15 16:47:22 freenas Structured Extended Features=0x2fbb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG>
Dec 15 16:47:22 freenas XSAVE Features=0x1<XSAVEOPT>
Dec 15 16:47:22 freenas VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Dec 15 16:47:22 freenas TSC: P-state invariant, performance statistics
Dec 15 16:47:22 freenas real memory  = 26306674688 (25088 MB)
Dec 15 16:47:22 freenas avail memory = 24910540800 (23756 MB)
Dec 15 16:47:22 freenas Event timer "LAPIC" quality 600
Dec 15 16:47:22 freenas ACPI APIC Table: <SUPERM SMCI--MB>
Dec 15 16:47:22 freenas FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
Dec 15 16:47:22 freenas FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
Dec 15 16:47:22 freenas WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Dec 15 16:47:22 freenas ioapic0 <Version 2.0> irqs 0-23 on motherboard
Dec 15 16:47:22 freenas SMP: AP CPU #1 Launched!
Dec 15 16:47:22 freenas SMP: AP CPU #5 Launched!
Dec 15 16:47:22 freenas SMP: AP CPU #6 Launched!
Dec 15 16:47:22 freenas SMP: AP CPU #4 Launched!
Dec 15 16:47:22 freenas SMP: AP CPU #7 Launched!
Dec 15 16:47:22 freenas SMP: AP CPU #2 Launched!
Dec 15 16:47:22 freenas SMP: AP CPU #3 Launched!
Dec 15 16:47:22 freenas Timecounter "TSC-low" frequency 1700030536 Hz quality 1000
Dec 15 16:47:22 freenas random: entropy device external interface
Dec 15 16:47:22 freenas kbd0 at kbdmux0
Dec 15 16:47:22 freenas module_register_init: MOD_LOAD (vesa, 0xffffffff80fc34c0, 0) error 19
Dec 15 16:47:22 freenas random: registering fast source Intel Secure Key RNG
Dec 15 16:47:22 freenas random: fast provider: "Intel Secure Key RNG"
Dec 15 16:47:22 freenas nexus0
Dec 15 16:47:22 freenas cryptosoft0: <software crypto> on motherboard
Dec 15 16:47:22 freenas aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
Dec 15 16:47:22 freenas padlock0: No ACE support.
Dec 15 16:47:22 freenas acpi0: <SUPERM SMCI--MB> on motherboard
Dec 15 16:47:22 freenas acpi0: Power Button (fixed)
Dec 15 16:47:22 freenas cpu0: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas cpu1: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas cpu2: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas cpu3: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas cpu4: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas cpu5: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas cpu6: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas cpu7: <ACPI CPU> on acpi0
Dec 15 16:47:22 freenas hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Dec 15 16:47:22 freenas Timecounter "HPET" frequency 14318180 Hz quality 950
Dec 15 16:47:22 freenas Event timer "HPET" frequency 14318180 Hz quality 550
Dec 15 16:47:22 freenas atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
Dec 15 16:47:22 freenas atrtc0: registered as a time-of-day clock, resolution 1.000000s
Dec 15 16:47:22 freenas Event timer "RTC" frequency 32768 Hz quality 0
Dec 15 16:47:22 freenas attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Dec 15 16:47:22 freenas Timecounter "i8254" frequency 1193182 Hz quality 0
Dec 15 16:47:22 freenas Event timer "i8254" frequency 1193182 Hz quality 100
Dec 15 16:47:22 freenas Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Dec 15 16:47:22 freenas acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
Dec 15 16:47:22 freenas pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Dec 15 16:47:22 freenas pci0: <ACPI PCI bus> on pcib0
Dec 15 16:47:22 freenas pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
Dec 15 16:47:22 freenas pci1: <ACPI PCI bus> on pcib1
Dec 15 16:47:22 freenas pcib2: <ACPI PCI-PCI bridge> irq 16 at device 1.1 on pci0
Dec 15 16:47:22 freenas pci2: <ACPI PCI bus> on pcib2
Dec 15 16:47:22 freenas mps0: <Avago Technologies (LSI) SAS2308> port 0xe000-0xe0ff mem 0xf7240000-0xf724ffff,0xf7200000-0xf723ffff irq 17 at device 0.0 on pci2
Dec 15 16:47:22 freenas mps0: Firmware: 20.00.02.00, Driver: 21.02.00.00-fbsd
Dec 15 16:47:22 freenas mps0: IOCCapabilities: 5a85c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,MSIXIndex,HostDisc>
 
Last edited:
D

dlavigne

Guest
Anything in /var/log/messages? Which build version (System -> Information)?
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
I seem to be one of the lucky ones to have not had a large number of issues.

Most people don't have any issues, and only come here if they do.

Is the memory approved for that motherboard? Please identify the power supply and drives.
 

theaddies

Contributor
Joined
Mar 28, 2015
Messages
105
6 x WD RE 2 TB Enterprise Hard Drive
RAID Z2
Crucial 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3L 1600 (PC3L 12800) Server Memory
Rosewill 80 PLUS Platinum Certified Power Supply ATX12V / EPS12V 550 Power Supply FORTRESS-550
 

theaddies

Contributor
Joined
Mar 28, 2015
Messages
105
Anything in /var/log/messages? Which build version (System -> Information)?
Build is FreeNAS-11.1-RELEASE.
I looked at the message. It appears that it is the same information I extracted from the console. I believe that is what you call the green bar at the bottom of the browser.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Also, you don't clearly define what you mean by "locking up". Does that mean the GUI stops responding? Is the system console (with a monitor and keyboard connected directly to the machine) still responding?
 

theaddies

Contributor
Joined
Mar 28, 2015
Messages
105
wI7pZ
Also, you don't clearly define what you mean by "locking up". Does that mean the GUI stops responding? Is the system console (with a monitor and keyboard connected directly to the machine) still responding?
Fair point. I didn't. The shares become unavailable and the GUI is inaccessible. It is about 24 hours since my post and alas, it is dead. The GUI does not respond. The shares are unavailable. SSH does not work. I tried to attach the current output from the KVM IPMI.
wI7pZ
 
Last edited:

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,974
I'd guess that your boot drive is failing. Replace it.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,974
I'd strongly suggest switching to a cheap SSD for a boot device. That or get a USB 2.0 drive. Some have reported that the Sandisk USB 3.0 drives die due to excess heat that they produce vs the 2.0 versions. I run a SSD boot device so I can't comment from experience, only what others have posted.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,974
Any inexpensive one will do. Some have purchased used enterprise drives from ebay fairly cheap.
 

Waco

Explorer
Joined
Dec 29, 2014
Messages
53
I'm having the same problem - Plex seems to be the only thing up and running without issue on a reboot (after it hung ~24 hours after installing), but I can't hit up the WebUI, access shares, or ssh into the server. No issues up until the upgrade from 11 to 11.1, and I can't even get into the WebUI or ssh to grab logs to see what the heck is going on. Boot device checks out cleanly on other machines.

I guess I get to play the game of installing a video card into the server to log in locally to poke around and/or boot into the older installation.

EDIT: I was able to quickly get the WebUI up for a few seconds prior to it going awol - switched back to 11.0RC4 and no issues on reboot.
 
Last edited:

arcanoia

Cadet
Joined
Dec 18, 2017
Messages
2
I'm (was) having a similar problem after updating to 11.1-RELEASE

those were the symptoms::

1- scrub automatically started, while scrub was running I was doing some very simple actvities with the server.. like moving files from folder to folder.. after some hours scrub stalled, after a while more I wasn't able to access to the webui and I wasn't able to access to SSH. I didn't have any monitor or keyboard attached to the server.. so I could only soft-reset the server (scary I know).. after booting up, all the changes I did to the server (all files I copied or moved) were reverted (more scary)

2- After my initial panic I saw that everything was back to normal (despite that i lost all the changes I did after upgrading and restarting).. Scrub started again.. this time i started sabnzbd and it started to download some files from usenet. After some hours, same problem again, system stalled, no access to SSH, no acces to webui (scary).. so I hat to soft-reset the server again. After rebooting I lost all what i queded to sabnzbd.. even the nzb files that i just copied to the NAS where physically gone.. the sabnzbd que was empty (poltergeist scary)

3- I decided that I didn't want to play scary anymore.. to I attached a monitor/keyboard to the server. I stoped the scrub and restarted it again. I let the system untouched (only the damned scrub running). After a while scrub stalled at 12TB (out of 48TB) for one complete day.. I tried to stop the scrub and i wasn't able to do it (command stalled). I went to the console and tried to perform a clean reboot. The system returned an error that he wasn't able to stop some process (I don't remember the exact message.. just something that was not able to stop some process and that I should try some ps command).. so I had to reset again

4- I gave up and reverted to 11.0-U4. Everything seems to be working fine now.. scrub is still running without stalling.
 
Last edited:

jsylvia007

Explorer
Joined
Oct 4, 2011
Messages
84
Adding myself as a "ditto" here as well... System runs for about 24-hours and then locks up (no access to shares, VMs hosted on an NFS mount to VMware start to fail, can't ssh in to reboot, no web GUI, etc.).

My environment has been rock-solid for a long time now, and I even had no issues at all...

I hesitate to post here because I know I'm going to get pounced on, BUT, I run FreeNAS in a hyperconverged VMware stack, much in the same way here: https://b3n.org/freenas-9-3-on-vmware-esxi-6-0-guide/

In fact, I used Ben's guide to setup my own environment.

As I said, everything has been rock-solid from FreeNAS 9 through 11.0-U4. Once upgrading to 11.1-RELEASE, I've exhibited the same things mentioned here...

I've now also rolled back to 11.0-U4. I will track and see if the stability comes back, but I don't see why it wouldn't. This is the only thing I've changed in my environment. Looks like I'm going to have to wait for an 11.1-U1 update.
 
Last edited by a moderator:

Pointeo13

Explorer
Joined
Apr 18, 2014
Messages
86
I'v been running 11.1-U1 for four days without any issues, today I replaced a 3TB drive with a 5TB drive. The pool begin to re-silver and ended up getting stuck at 22.94%, with the time only increasing. At the same time my CIFS became unstable, the network connections were going in and out on all the servers that had mapped drives. I'm rebooting the FreeNAS server right now and reverting back to 11.0-U4. Two week ago I replaced 11 3TB drives with 5TB drives without any re-silvering issues / CIFS issues.

Edit: Server is back up on 11.0-U4, so far so good, everything is back to normal, resilvered is at 0.79% right now. I'll update once resilvering is at 22.94%

Edit2: Everything looks good, no issues with resilvering, currently at 26.14% on 11.0-U4
 
Last edited by a moderator:

KingJ

Cadet
Joined
Jan 4, 2014
Messages
5
I also ran in to this ~22 hours after upgrading. Suddenly all network services hung - SMB, SSH, the WebUI, the only network service that worked was ping. I also couldn't get on the shell locally, nothing happened after selecting option 9 on the console. Like some of the others mentioned, an automatic scrub was in progress at the time.

It did respond to a graceful reboot request however and i've switched back to 11.0-U4 for now.
 

vvuk

Cadet
Joined
Jun 6, 2016
Messages
5
Adding a "me too" here. It's been a while since upgrading, but it locked up sometime last night with identical symptoms to here. No response via IPMI serial console either while locked up. Rebooted and rolled back to 11.0-U4 as well.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
No response via IPMI serial console either while locked up. Rebooted and rolled back to 11.0-U4 as well.
That is... unexpected. Even if FreeNAS has a problem, it should not affect IPMI. Please post your hardware.
 
Status
Not open for further replies.
Top