July 19, 201213 yr First syslog is the first parity failed rebuild, second syslog is the second parity rebuild failed. The errors are a bit different, one points to SAS drivers multiple times, the other does not. The drive getting the write fails has been has extend SMART ran on it twice now and precleared successfully. SMART is absolutely fine... 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 - 0 3 Spin_Up_Time 0x0027 181 149 021 Pre-fail Always - 7916 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 35 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 100 100 000 Old_age Always - 97 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 - 33 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 24 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 47 194 Temperature_Celsius 0x0022 115 110 000 Old_age Always - 37 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 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Do you guys feel this is SAS driver related? syslog1.txt syslog2.txt
July 20, 201213 yr Author Well it seems like moving the parity drive to a different hotswap bay (that uses a different SAS2LP card), allowed me to rebuild parity. I was then able to move it back to the original hotswap bay, and run a parity sync which completed with 0 errors. This could just be related to chance because SAS errors on the earlier builds were random.
August 5, 201213 yr Author Still happening, this time it happened during normal usage. Anyone have any idea? I have a hard time believing it's the drive, it passes smart tests and has no smart errors. I am the only one still having SAS errors on RC6? errors1.txt
August 5, 201213 yr Author Next part of errors in syslog (wouldn't let me do both in one post, exceeded 192KB) errors2.txt
August 5, 201213 yr What is your hardware? If it uses a LSI chipset then your issues are related unless you're running the RC6-LSI-Experimental-Fixes-2 version.
August 5, 201213 yr Author What is your hardware? If it uses a LSI chipset then your issues are related unless you're running the RC6-LSI-Experimental-Fixes-2 version. Intel i3-2120 (3.3GHz) Supermicro MBD-X9SCM-F-O 8GB Kingston (DDR3 1333) 3x Supermicro AOC-SAS2LP-MV8 Using RC6-test1. I have 2 servers with the exact same parts, the other one has been running RC6-test1 for 18 days now with no issues. So I don't know why one would be fine, and not the other. I just can't find anything wrong, as soon as it drops the drive I re-assign it and it's fine. I could try RMAing the drive, but it passes every test I throw at it with no errors. They'd probably decline the RMA. All my testing points to it being an issue with writing to the parity drive. I did 3 parity syncs in a row, and there were 0 errors. If I actually rebuild the parity drive, that's when it starts happening. It took 3 attempts for it to successfully rebuild parity without taking the drive offline, however i've done a total of 3 parity sync since then and all were successful. So reading from the drive is fine, writing to it is not. This error popped back up when I was moving files from the cache drive over to the array, so it was writing to the parity then too.
Archived
This topic is now archived and is closed to further replies.