Moussa

Thanks for the advice, I'll run the long smartctl test tomorrow and see if anything looks off.

Heh, yea I was pretty sure that read count was an error. Well the drive is currently in the process of recreating the parity info with no errors so far. When I have some time available where I can switch off my server I'll run memtest (I had run it for 24 hours when I first built the server) and see if anything pops up. Hopefully there's no silent corruption going on

Had my parity drive fail tonight, with a red ball and a large amount of errors. Switched off my server and checked all the connections and created a smartctl report. Please find it attached, along with a syslog. I am running unRAID 6.0-beta3 smart.txt syslog.txt

Is this for b6 specifically or would it work for any of the earlier betas? I'm still on b3 as I'm waiting for Dynamix to support b4+.

Awesome

If your talking about to being able to see the value the slide represents when you move it, I have the same issue of the top bubble being chopped off on my iPhone. Yep, that's the issue. I currently have no idea what those values are lol

I've recorded a video of the small bug I reported earlier speeding_ant, hope it helps clarify my issue.

That's not actually the point. Opening up your unRAID server to WAN is very insecure full stop. unRAID comes with pretty much no security features as it assumes your server is only accessible internally. Connecting to your home network over VPN and using your internal server address to connect the app is pretty safe however.

Purchased, love it. There is a small bug however, with the application settings sliders. When sliding them around and letting go, the little 'popup' that appears is hidden behind the slider above. So I can't see what values I'm setting the sliders to! Otherwise great job.

For those features and that design, it certainly is

Awesome. Look forward to it. Have you decided on a price?

Has this been submitted yet? Can't wait

FreeNAS uses the ZFS filesystem, and for optimum performance and data safety, people generally recommend a GB of ECC RAM for every 1TB of data you're protecting. unRAID is a very different beast and uses very little RAM. If you're doing nothing more on the server than running unRAID then 1GB of RAM is more than enough.

No problem, that makes perfect sense. Thanks!

Will this plugin be updated for unRAID v6 or does it by any chance work anyway?

Has anyone tried Dynamix with the new beta4? If so, is it all working correctly?

Just to let others wondering know, I've been running the 6.0 beta for a few days now and the error has disappeared. Thanks.

I've read that they're indicating a hardware fault in one of the CPU caches, and these messages are the CPU indicating that it's successfully recovered from them with a parity check. If so, wouldn't that indicate a long term problem and I should RMA the CPU? I'd like to stay on v5.* until the plugins are updated if you say this is harmless, but I will try running v6 for a few days to see if any more errors pop up.

Hi. I recently built my first unRAID server from these parts https://uk.pcpartpicker.com/user/moussekateer/saved/3DGU, and everything has been fine except for one issue. I keep seeing 'Blackbox kernel: mce: [Hardware Error]: Machine check events logged' in the syslog. Sometimes I go a few days without seeing anything and sometimes I see an error popup every few minutes or seconds. My array currently consists of two 3TB drives (no parity drive yet), both of which I have precleared with 3 cycles and saw no issues. I believe the errors sometimes correlate with heavy writing to the drives, but I cannot reproduce the errors on demand so it may just be a coincidence. I have made sure all the cables and parts inside the server are connected and seated properly so I don't believe it's a connection issue. I have also updated my BIOS to the latest version. I have run mcelog from the flash drive (before I eventually rebooted my server, when I had 20 or so of these errors) to investigate, and believe it's a internal hardware issue with the CPU? Please find the output attached, along with my syslog. I am running unRAID version: 5.0.5 Thank you for your help in advance. syslog-2014-03-06.txt mcelog_output.txt

Your disk is perfectly fine. Some initial values are put purposely close to their affiliated failure threshold by the manufacturer. Example: Even a few spin-up-failures (subsequently requiring a re-try) would indicate a mechanical issue with the drive. Therefore, the failure threshold is very close to the starting value for that parameter on that disk. That makes sense. Got the drive in my array now, all working fine. Thanks.

The important number for those is the VALUE, which for both is 100, as in 100% perfect, can't be any more perfect than that. It's not that they are close to the threshold, but that the manufacturer has factory set the thresholds to start so close to 100, who knows why. Your SMART reports for that drive appear to be perfect, nothing to worry about. That's good to hear, thanks for the help!

Hi guys. This is my first time building an unRAID server and I just wanted to make sure that I'm correct in thinking that this preclear report is A-OK. The only things that have me worried are the Spin_Retry_Count and the End-to-End_Error values because they seem to be near the thresholds. Thanks for any advice Thanks for any advice. preclear_start Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: W1F3J6S6 LU WWN Device Id: 5 000c50 06a5ae556 Firmware Version: CC27 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Feb 14 03:30:24 2014 GMT ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 105) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 327) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status 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 0x000f 118 099 006 Pre-fail Always - 194593040 3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 12 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 419986 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 44 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 12 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 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 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 071 067 045 Old_age Always - 29 (Min/Max 17/33) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 45 194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 16 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 41h+39m+16.926s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 17581599648 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 27037241817 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. preclear_finish Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: W1F3J6S6 LU WWN Device Id: 5 000c50 06a5ae556 Firmware Version: CC27 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Feb 15 19:05:38 2014 GMT ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 105) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 327) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status 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 0x000f 117 099 006 Pre-fail Always - 125433192 3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 12 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 792073 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 84 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 12 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 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 0 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 070 067 045 Old_age Always - 30 (Min/Max 17/33) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 46 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 16 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 81h+09m+32.314s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 29302666080 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 56755436299 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. preclear_rpt ========================================================================1.14 == invoked as: ./preclear_disk.sh -A -M 3 -c 2 /dev/sdb == ST3000DM001-1CH166 W1F3J6S6 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 2 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 5:49:09 (143 MB/s) == Last Cycle's Zeroing time : 5:08:45 (161 MB/s) == Last Cycle's Post Read Time : 11:44:01 (71 MB/s) == Last Cycle's Total Time : 16:53:45 == == Total Elapsed Time 39:35:14 == == Disk Start Temperature: 29C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 118 6 ok 125433192 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 70 71 45 near_thresh 30 Temperature_Celsius = 30 29 0 ok 30 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================