December 19, 200916 yr I am building parity for the first time on 1.5TB drive (all data drives are 1.5TB too) and unMenu shows me: Sync Errors 89 (Corrected). Is this something I should be concerned with? All drives have been fully precleared and the preclear script didn't show anything to be concerned with. I am using temporarily Promise TX4 as my Supermicros AOC-SAT2-MV8 have still not arrived. The syslog shows: Dec 19 06:09:12 startank kernel: md: disk5 read error Dec 19 06:09:12 startank kernel: handle_stripe read error: 1171460096/5, count: 1 Dec 19 06:09:12 startank kernel: md: disk5 read error Dec 19 06:09:12 startank kernel: handle_stripe read error: 1171460104/5, count: 1 Dec 19 06:09:12 startank kernel: md: disk5 read error Dec 19 06:09:12 startank kernel: handle_stripe read error: 1171460112/5, count: 1 Edit: removing remainder of syslog, as it is attached as a whole down below.
December 19, 200916 yr Author Here smartclt output for that drive5: root@startank:~# smartctl -d ata -A /dev/sdd smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === 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 100 006 Pre-fail Always - 159964260 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 83 5 Reallocated_Sector_Ct 0x0033 099 099 036 Pre-fail Always - 77 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2059475 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 247 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 43 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 087 087 000 Old_age Always - 13 190 Airflow_Temperature_Cel 0x0022 056 051 045 Old_age Always - 44 (Lifetime Min/Max 22/47) 194 Temperature_Celsius 0x0022 044 049 000 Old_age Always - 44 (0 21 0 0) 195 Hardware_ECC_Recovered 0x001a 054 022 000 Old_age Always - 159964260 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 97525822390486 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 60279812 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1158684912
December 19, 200916 yr Author Is there a way to know which files exactly are affected? After parity disk rebuild ended I got a status line saying: Parity is Valid:. Last parity check < 1 day ago . Parity updated 89 times to address sync errors. Anything I should do about those 89 sync errors?
December 19, 200916 yr Is there a way to know which files exactly are affected? After parity disk rebuild ended I got a status line saying: Parity is Valid:. Last parity check < 1 day ago . Parity updated 89 times to address sync errors. Anything I should do about those 89 sync errors? No way to know which files involved, nothing you can do about them. Parity was already updated to reflect what was read from the disks when the errors are reports. The errors should not appear if you do a subsequent parity check. If they do, you have hardware issues to resolve, as it indicates you cannot consistently read your disks contents. (memory,cabling,disks,power supply,motherboard, etc) Joe L.
December 19, 200916 yr Author This are 89 errors from disk5 when I first build the parity disk. Interesting unRAID Main do not show them, only unMenu Main shows those 89 erros alongside the disk. I wanted to check which files are affected in order to evaluate and delete or re-copy those files. What I was thinking is to rsync the contents to another disk and insert it instead of the disk5 and rebuilt parity from scratch. Would rsync indicate the errors again, probably with filenames? I can't leave with those 89 errors and need to do something. I don't think the parity is correct either, as it was build with those errors in place, or I am wrong? Thanks much!
December 19, 200916 yr This are 89 errors from disk5 when I first build the parity disk. Interesting unRAID Main do not show them, only unMenu Main shows those 89 erros alongside the disk. Errors on the INITIAL parity calculation are entirely different than those later, it might be why unRAID does not bother to show them. unMENU just is showing the internal counter. I have no idea of its meaning on an initial calculation, as differences from the initial values on the parity drive are expected. I'd do ANOTHER parity check and see if any errors show. They should not if all your disks are working properly. I wanted to check which files are affected in order to evaluate and delete or re-copy those files. What I was thinking is to rsync the contents to another disk and insert it instead of the disk5 and rebuilt parity from scratch. Would rsync indicate the errors again, probably with filenames? I can't leave with those 89 errors and need to do something. I don't think the parity is correct either, as it was build with those errors in place, or I am wrong? Thanks much! You have a problem with disk5 in your array, but you are apparently trying your best to make it difficult to see all the clues needed to assist in diagnosis by posting threads all over the place in different forums. This is as good a thread to post the FULL ZIPPED syslog. An excerpt as you've posted in the other thread is nowhere near as useful, as you do not know what to look for, and often neither will anyone trying to help until they see the full log. Until you fix the errors with disk5, NO PARITY will be correct. All files on DISK5 are suspect at this point, as there was no parity in place to protect them. There may be absolutely nothing wrong with them, as it could be a bad cable, or almost anything else.... If you are lucky, and concentrate your post to one thread for this issue, then perhaps RobJ will assist as I think he is the best at analyzing syslogs (provided you attach a complete one so he has the information needed for analysis) Joe L.
December 19, 200916 yr Author If you are lucky, and concentrate your post to one thread for this issue, then perhaps RobJ will assist as I think he is the best at analyzing syslogs (provided you attach a complete one so he has the information needed for analysis) Joe, which other threads are you referreing to? I didn't know I have posted with the same issue somewhere else as this is the only thread about this curious disk5 problem (I was inquiring about smartctl in general but not related to this issue). Attached the syslog and many thanks in advance!
December 19, 200916 yr Unfortunately, I'm out of time at the moment, but you do have bad sectors on Disk 5 ('media error', 'UNC' (UNCorrectable)). Unrelated issue, there was apparently a crash of the NFS daemon at the stopping of the array, search 'nfsd Not tainted'. This also appears in peter_sm's syslog, similar circumstances. It does not appear to have caused any problems because it was stopping, but it should be fixed, may leave orphaned resources (memory, threads, handles, etc). When I have time, I'll provide more detail in the v4.5 release thread.
December 19, 200916 yr Author Thanks, Rob! At the moment I am copying data using rsync away from that disk5 and closely monitoring syslog for error messages. I may be lucky and get out the data ok. Anything I should take care, or any procedures what/how to monitor the copy/rsync except syslog? There is definitely not a cable issue or the like, double checked everything, put the disc in another slot (using a backplane with 8087 cables). Thanks gain!
Archived
This topic is now archived and is closed to further replies.