AeroSteveO

I love the flexibility of it all. I can mix and match drive sizes, I can swap between dual and single parity, I can run containers to use those extra clock cycles, it's just amazingly flexible. Edit: forgot what I want to see next: better data integrity tools, I've had some aging disks lose data quietly and parity check just tells me the data is gone, I wish I could go further than that to rebuild or figure out which disk is bad

I don't have checksums for the data. Might be something to figure out and setup. Thanks for the help.

Full diagnostics attached diagnostics-20161105-1926.zip

The auto parity check that unraid does was correcting errors. However if the data disk is corrupting, correcting the parity disk is the wrong thing to do. So i'm trying to find the data disk thats causing issues.

The smart stats for disks 7 and 4 give some interesting values. Multi zone error rate of 2 on disk 4, and both a Seek Error Rate of 89990744 and a Read Error Rate of 7187952 on disk 7. Disk 4 Smart Stats: SMART Attributes Data Structure revision number: 16 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 200 200 051 Pre-fail Always - 12 3 Spin_Up_Time 0x0027 168 167 021 Pre-fail Always - 6600 4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3934 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 048 048 000 Old_age Always - 38366 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 299 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 252 193 Load_Cycle_Count 0x0032 043 043 000 Old_age Always - 473458 194 Temperature_Celsius 0x0022 115 101 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 2 SMART Error Log Version: 1 No Errors Logged Disk 7 Smart Stats: 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 104 099 006 Pre-fail Always - 7187952 3 Spin_Up_Time 0x0003 091 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2807 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail Always - 89992625 9 Power_On_Hours 0x0032 070 070 000 Old_age Always - 26526 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 80 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 096 096 000 Old_age Always - 4 190 Airflow_Temperature_Cel 0x0022 063 051 045 Old_age Always - 37 (Min/Max 23/37) 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 - 64 193 Load_Cycle_Count 0x0032 054 054 000 Old_age Always - 92839 194 Temperature_Celsius 0x0022 037 049 000 Old_age Always - 37 (0 15 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 - 7775h+18m+45.736s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 63827102384 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 500695428198 SMART Error Log Version: 1 No Errors Logged

No unclean shutdowns since the last parity check. This was the most errors i've seen, previous parity check had 4 errors. And yes i know this means theres corruption somewhere on my array, i was just hoping to narrow it down to a certain disk. I'm not too worried about small numbers of errors like this, but i'd like to figure it out and fix it before it becomes a real issue. I've started long smart tests on all disks, hopefully that will find the issue.

I have noticed a few errors showing up in my latest parity checks, but have been rather busy so i'm just looking into them now. The below is the syslog from the parity check. From the look of it, its the parity disk at error, but it isn't reporting the corresponding data disk for me to run a smart test on. I have run a smart test on the parity disk itself and have posted that below. Oct 30 13:47:23 ShadowOfIntent kernel: mdcmd (176): check NOCORRECT Oct 30 13:47:23 ShadowOfIntent kernel: md: recovery thread: check P ... Oct 30 13:47:23 ShadowOfIntent kernel: md: using 1536k window, over a total of 5860522532 blocks. Oct 30 14:12:39 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=332010776 Oct 30 20:14:19 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=3909737688 Oct 31 00:05:43 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6443181832 Oct 31 00:05:44 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6443397608 Oct 31 00:05:45 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6443569616 Oct 31 00:05:50 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6444617432 Oct 31 00:05:51 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6444813920 Oct 31 00:05:51 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6444875504 Oct 31 00:05:54 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6445480352 Oct 31 00:05:58 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6446318832 Oct 31 00:05:58 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6446374384 Oct 31 00:05:58 ShadowOfIntent kernel: md: recovery thread: P incorrect, sector=6446401792 Oct 31 07:03:56 ShadowOfIntent kernel: md: sync done. time=62193sec Oct 31 07:03:56 ShadowOfIntent kernel: md: recovery thread: completion status: 0 The smart test has no glaring issues in it, and the long test ran without any problems as well. I'm not sure if theres a way to determine the data disk involved with the sections, as right now i'm running 9 data disks, so guess and check is a bit time intensive. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.19-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: HGST Deskstar NAS Device Model: HGST HDN726060ALE610 Serial Number: LU WWN Device Id: 5 000cca 24dc47d95 Firmware Version: APGNT517 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Nov 4 21:43:51 2016 CDT 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: ( 113) 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: ( 785) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 137 137 054 Pre-fail Offline - 104 3 Spin_Up_Time 0x0007 155 155 024 Pre-fail Always - 488 (Average 360) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 263 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 128 128 020 Pre-fail Offline - 18 9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 7840 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 22 192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 2259 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 2259 194 Temperature_Celsius 0x0002 171 171 000 Old_age Always - 35 (Min/Max 20/51) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 7739 - # 2 Extended offline Completed without error 00% 4432 - 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. Edit: Unraid Version 6.2 is on the server at the moment

Great news, i'll move forward with my server upgrade then.

Wondering if anyone has tested the plugins on unraid 6.2 yet? Specifically plex and sickrage.

Preclear also goes through multiple phases, it reads the entire disk, writes zeros to the entire disk, and then reads the entire disk again, so you may be seeing 76% on the initial read of the disk, as it tracks the process through each section, not the overall process

Updated the bios, ran a parity sync, and there were no problems, i think that solved it, thanks for the help

The error from trying to install a non-existant package is actually from my go script, which i forgot to modify to remove the hamachi install from. i have no sata cards installed, all ports being used are based on the motherboard, i'll look for a bios update though, and see if that helps fix the problem, i'll also remove the hamachi install part of my go script

I recently got a new 4TB Seagate hdd (http://www.newegg.com/Product/Product.aspx?Item=N82E16822178338) and have been having some troubles integrating it into my current server. First, when trying to preclear it on my main server, it would error during the clear, and crash the server, causing the machine to drop off my network, and any attempt to wake the machine with a local keyboard would fail. however, when i put the disk on an 8 year old dell i had laying around, i was able to preclear it with zero issues. I put the drive back into my main server thinking i had a corrupt file, and updated that server to unraid 5.0 final (moving only the config directory to the new build, and installing unmenu) in order to try using the drive again. i removed the parity from the server, started it, stopped it, put the new 4TB drive as parity, the old 3TB parity drive as another data disk, and started the server again to rebuild the parity. it made it past the 50% mark before crashing, however this time i managed to get some info from the computer. The pictures i have of the error are at the following link The first image is from a crash while using 5.0 rc11 to run the pre-clear, the second is from using 5.0 final to run the parity check. The only error i've seen showing up is the irq error, which happens as the computer crashes, with nothing before it in the syslog (sadly i don't know where that syslog text file has gone). Any help on figuring this out would be appreciated EDIT: just noticed i still have a putty window open root@ShadowOfIntent:/# Message from syslogd@ShadowOfIntent at Tue Oct 22 23:26:49 2013 ... ShadowOfIntent kernel: do_IRQ: 0.77 No irq handler for vector (irq -1)

I will update to 5.0 final as well then, for stability and to avoid this error in the future, thank you for the help

I think the issue is arising from file name limits in unraid, as the steam backup tried to create a folder with every name of every game inside it, when replicating this onto a usb hdd in windows, the folder name was 255 characters long before the backup crashed, i think removing these folders somehow will fix the problem i'd like to have my server running with all the shares intact before updating to 5.0 final EDIT: fixed the issues i had, removing the poorly named folders allowed me to regain access