FreeNAS suddenly crashing

[Shogoki]

Hey Guys,

some weeks ago, I started to build my FreeNAS system.
I am running on an HP N54l Microserver with an additional NIC (HP NC360T, OEM Intel NIC)
I already did the general configuration steps, created some Datasets in my zpool and also installed plexMediaServer Plugin.
Now, I am encountering 2 major problems...
Important one first:
If I start copy (or moving) big files via CIFS , after a while the NAS is suddenly crashing (just rebooting).
I checked the logs afterwards now several times (I already redirected Log Path to persistent storage) but I am unable to interpret the cause there..

Second one is:
If i leave my NAS alone for some time it becomes unresponsive over the network.I cannot see any issue on the local console then. If i try to ping any host (from local console) ping eports the following error: "no buffer space availabe"

Actually these issues are Project-Stoppers for the migration of my data onto the NAS. I would appreciate every help, suggestions or hints on these topics.
Kind Regards
Shogoki

 

[warri]

Can you attach the log output? Which FreeNAS Version are you running and what's the rest of your hardware (HDDs, RAM)? Using ZFS or UFS? Are you running with ECC RAM and if not did you already test your memory?

 

[Shogoki]

Hi warri,

Thank you for your quick reply .
The requested information:
I am using 3x WD Red Hard drives with 2TB each.Using RaidZ (ZFS equivalent for RAID5)
I am using HP Memoy Modules (2x 2GB (HP Part # 500209-061)), which is unbuffered ECC RAM.
Plan is to upgrade to 8GB RAM later.
I am running FreeNAS version 9.2
Following are the log entries from today where i booted up the system, started the copy job, and it crashed, then booted up again.
I attached the log until the boot process after the crash is finished (i think so, next log entry is 21:32).

Did I miss out anything else? I
hope this helps, helping me ;-).

 

[gpsguy]

ZFS on FreeNAS needs a minimum of 8Gb of RAM.

Instead of upgrading to 8Gb, go straight to 16. I've got 16Gb of ECC RAM in a N54L.


Sent from my phone

 

[rm-r]

i had similar disconnection issues - i moved from AMD to intel cpu, supermicro MB with intel nics - same freenas USB works flawlessly - will be hardware compatibility issue.

 

[warri]

I agree with the others, you should upgrade to at least 8 GB. But I don't think it's a general AMD incompatibility, since there are a lot of users with a N54l without those symptoms.

I see some ATA errors in the log, not sure if they are related.

Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): SETFEATURES ENABLE SATA FEATURE. ACB: ef 10 00 00 00 40 00 00 00 00 02 00
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): RES: 51 04 00 00 00 40 00 00 00 02 00
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): Retrying command
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): SETFEATURES ENABLE SATA FEATURE. ACB: ef 10 00 00 00 40 00 00 00 00 02 00
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): CAM status: ATA Status Error
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): RES: 51 04 00 00 00 40 00 00 00 02 00
Jan 28 21:09:19 ksnas01 kernel: (aprobe0:ahcich3:0:0:0): Error 5, Retries exhausted

What is the ada3 device? It seems to be causing those.

Jan 28 20:56:56 ksnas01 kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
Jan 28 20:56:56 ksnas01 kernel: ada3: <VB0250EAVER HPG9> ATA-8 SATA 2.x device
Jan 28 20:56:56 ksnas01 kernel: ada3: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Jan 28 20:56:56 ksnas01 kernel: ada3: Command Queueing enabled
Jan 28 20:56:56 ksnas01 kernel: ada3: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C)
Jan 28 20:56:56 ksnas01 kernel: ada3: Previously was known as ad10

Can you post the output of smartctl -a -q noserial /dev/ada3?

 

[Shogoki]

I agree with the others, you should upgrade to at least 8 GB. But I don't think it's a general AMD incompatibility, since there are a lot of users with a N54l without those symptoms.

Okay, I will think about upgrading to 16GB instead of just 8GB. But I do not think that my system is crashing because of the amunt of RAM, correct me if I may be wrong.. Also with the AMD I am your opinion, warri.

I see some ATA errors in the log, not sure if they are related.


What is the ada3 device? It seems to be causing those.


Can you post the output of smartctl -a -q noserial /dev/ada3?

ada3 is actually the 250GB SATA drive that shipped with the server. I forgot to mention, as I do not use it at the moment.
Do you think it may causes the problems?
The SMART output:

Code:

~# smartctl -a -q noserial /dev/ada3
smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
 
=== START OF INFORMATION SECTION ===
Model Family:    HP 250GB SATA disk VB0250EAVER
Device Model:    VB0250EAVER
Firmware Version: HPG9
User Capacity:    250,059,350,016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:  ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Jan 28 23:16:00 2014 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
 
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
 
General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (  0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  625) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (  2) minutes.
Extended self-test routine
recommended polling time:        (  46) minutes.
SCT capabilities:              (0x1039) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.
 
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate    0x002f  109  100  006    Pre-fail  Always      -      21696663
  3 Spin_Up_Time            0x0023  097  097  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      938
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x002f  100  253  030    Pre-fail  Always      -      65680
  9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      280
10 Spin_Retry_Count        0x0033  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      58
180 Unknown_HDD_Attribute  0x002b  100  100  000    Pre-fail  Always      -      7962985
183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0
184 End-to-End_Error        0x0032  100  100  097    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0
188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0
189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0
190 Airflow_Temperature_Cel 0x0022  077  070  045    Old_age  Always      -      23 (Min/Max 14/26)
194 Temperature_Celsius    0x0022  023  040  000    Old_age  Always      -      23 (0 12 0 0 0)
195 Hardware_ECC_Recovered  0x003a  045  045  000    Old_age  Always      -      21696663
196 Reallocated_Event_Count 0x0032  100  100  036    Old_age  Always      -      0
197 Current_Pending_Sector  0x0032  100  100  000    Old_age  Always      -      0
198 Offline_Uncorrectable  0x0030  100  100  000    Old_age  Offline      -      0
199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0
 
SMART Error Log Version: 1
No Errors Logged
 
SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]
 
 
SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Again, Thanks to all of you for help.

 

[jgreco]

But I do not think that my system is crashing because of the amunt of RAM, correct me if I may be wrong..

Consider yourself corrected. ZFS *and* a piggy plugin like Plex shouldn't run at all on 4GB.

 

[rm-r]

I'm not saying AMD is generally broken - just my experience

 

[Yatti420]

Hmm.. Check sata cable? I'd power off any drive it if not in use (make sure it's not in use! - Don't brick your pool!).. Reboots should not occur!.. I trust you did the normal testing/burn in and checked for any bios specific needs for freenas/hardware.. Something isn't playing nice..

 

[warri]

Yeah, the SMART data looks ok but I'd also just disconnect the drive if you don't need it. If you want to keep it, trying a new sata cable can't hurt and can be done quick and easy.
I'm not using jails by myself so I have no experience about the memory needs..

If you can't upgrade the RAM soon, you could try to get rid of the jail and see if that helps.
To troubleshoot further, you could disconnect any hardware which is not needed to run the system (all drives etc.) and see if it still freezes after a while.

 

[Shogoki]

just as an update:
I upgraded my RAM now to 16GB.
FreeNAS is still crashing some minutes after I started the copy.

To troubleshoot further, you could disconnect any hardware which is not needed to run the system (all drives etc.) and see if it still freezes after a while.

That is what I will try now.

 

[ewhac]

I see some ATA errors in the log, not sure if they are related.

What is the ada3 device? It seems to be causing those.

I have an N54L as well, and the 250GB drive that came with it also started throwing those messages when I upgraded to FreeNAS 9.x. Given the other suspicious behaviors that drive has exhibited, I've named it 'faulty' and only put extremely non-critical data on it.

 

[Yatti420]

It's only 250gb I'd just remove it if not needed.. Frees up space for another drive.. The easiest thing to start with is sata cable / standard checks..

 

[gpsguy]

Can you verify that you have this setting in your BIOS? I don't think it is/was the default.

Advanced/IDE Configuration/SaTA Controller Mode/AHCI

 

[Shogoki]

I tried to plug out the drive. and the system was still crashing.

It's only 250gb I'd just remove it if not needed.. Frees up space for another drive.. The easiest thing to start with is sata cable / standard checks..

As you say, its only 250GB. I think I will keep it removed from my NAS. Anyway. i think on N54 SATA Cable is not that easy, because the drives are connected to the Backplane of the server.

Can you verify that you have this setting in your BIOS? I don't think it is/was the default.

Advanced/IDE Configuration/SaTA Controller Mode/AHCI

I think I´ll check that this evening.

But one important thing: Yesterday night, i tried to plug out my PCI NIC (HP NC360T) too. Therefore I connected my network cable to the onboard NIC and configured the new interface.
I started the standard test again and figured out, that my NAS was not crashing again! I will start some more tests this evening, but if you may have some ideas what could be the reason for that, I would be glad to hear them.