February 1, 201115 yr Unraid version: 4.6 free (2 data disks, 1 parity) System: Supermicro C2SEA with all the other bits and pieces based on the premade systems by limetech. This showed up on the web interface, after running a monthly parity check last night: Check will start a Parity-Check. (Last checked on 2/1/2011 8:13:51 AM, finding 11 errors.) Syslog relating to the error: Feb 1 00:00:01 tower kernel: mdcmd (61): check NOCORRECT Feb 1 00:00:01 tower kernel: Feb 1 00:00:01 tower kernel: md: recovery thread woken up ... Feb 1 00:00:01 tower kernel: md: recovery thread checking parity... Feb 1 00:00:01 tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Feb 1 00:06:02 tower dhcpcd[7193]: sending DHCP_REQUEST for 192.168.x.xxx to 192.168.x.xxx Feb 1 00:06:02 tower dhcpcd[7193]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Feb 1 00:06:02 tower dhcpcd[7193]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Feb 1 00:06:02 tower dhcpcd[7193]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Feb 1 00:06:02 tower dhcpcd[7193]: DHCP_ACK received from (192.168.x.xxx) Feb 1 00:17:06 tower kernel: md: parity incorrect: 165008568 Feb 1 01:06:02 tower dhcpcd[7193]: sending DHCP_REQUEST for 192.168.x.xxx to 192.168.x.xxx Feb 1 01:06:02 tower dhcpcd[7193]: dhcpIPaddrLeaseTime=7200 in DHCP server response. Feb 1 01:06:02 tower dhcpcd[7193]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec Feb 1 01:06:02 tower dhcpcd[7193]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec Feb 1 01:06:02 tower dhcpcd[7193]: DHCP_ACK received from (192.168.x.xxx) Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627136 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627144 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627152 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627216 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627224 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627232 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627568 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627576 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627648 Feb 1 01:19:22 tower kernel: md: parity incorrect: 741627656 (everything above, and everything below that is normal behaviour, DHCP requests from and to the firewall) Smart report for disk 0 (parity): 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_VAL UE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 243 241 021 Pre-fail Always - 9850 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 38 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 098 098 000 Old_age Always - 1807 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 15 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 185 185 000 Old_age Always - 46152 194 Temperature_Celsius 0x0022 129 119 000 Old_age Always - 23 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 - 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): Smart report for disk 1 (data disk 1): 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 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 074 074 011 Pre-fail Always - 8600 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 233 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 2572 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 129 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 085 057 000 Old_age Always - 15 (Lifetime Min/Max 14/19) 194 Temperature_Celsius 0x0022 085 056 000 Old_age Always - 15 (Lifetime Min/Max 12/20) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 530880464 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 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): Smart report for disk 2 (data disk 2) 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 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 074 074 011 Pre-fail Always - 8710 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 153 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 10733 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 2524 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 129 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 086 057 000 Old_age Always - 14 (Lifetime Min/Max 13/18) 194 Temperature_Celsius 0x0022 084 056 000 Old_age Always - 16 (Lifetime Min/Max 11/20) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 618204199 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 099 000 Old_age Always - 1 201 Soft_Read_Error_Rate 0x000a 100 100 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 Aborted by host 30% 811 - # 2 Short offline Completed without error 00% 808 - # 3 Extended offline Completed without error 00% 783 - # 4 Extended offline Aborted by host 60% 763 - # 5 Extended offline Completed without error 00% 747 - # 6 Conveyance offline Completed without error 00% 742 - # 7 Extended offline Aborted by host 50% 741 - # 8 Short offline Completed without error 00% 740 - # 9 Short offline Completed without error 00% 725 - 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): Have not done anything else, did NOT run reiser check on any of the disks. Should I be worried? Thank you in advance. If you need more information about something let me know. Edit: Forgot to add that all disks show as green on webpage Edit 2: attaching syslog to this post in case someone misses it from my post below syslog.zip
February 1, 201115 yr Did you have an unclean shutdown (e.g., power failure) recently? You need to post a full syslog for the Linux experts to help. The snippet from the parity check is not enough. I don't see anything unusual in the smart reports.
February 1, 201115 yr Author syslog cannot be attached because it's too big. attached last entries around the time of the errors. Power outage was about a month ago, but I've since ran a parity check with no errors.
February 1, 201115 yr I see a good few members using pastebin.com for hosting their syslogs - might be of use?
February 1, 201115 yr syslog cannot be attached because it's too big. attached last entries around the time of the errors. Power outage was about a month ago, but I've since ran a parity check with no errors. You could Zip the log up that should make it smaller. Might then all be uploadable.
February 1, 201115 yr If syslog is big likely something is going on that makes it especially important the you post it.
February 1, 201115 yr Author Attached syslog. Sorry for the inconvinience caused, my mistake syslog.zip
February 2, 201115 yr Author Since I or someone else cannot find anything wrong with the smart reports, and there is nothing in the syslog showing further details about this, I'm assuming that the array is in a usable state, and the parity errors were bits left behind during the outage last month/deletion of the boinc1 directories. If this continues the most likely cause is silent data corruption on the data disks I believe (samsung HD103SI both of them, parity drive is a WD20EADS).
Archived
This topic is now archived and is closed to further replies.