February 8, 201610 yr Hi guys, can i please get a more experienced eye on this problem if possible, one of my disks is reporting errors and i randomly get interrupted transfers to the disk, please see below / attached. Disk 4 in array. It also appears that my parity sync now fails with this disk so I took it offline,. === 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: ( 60) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 6) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) 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 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 239 196 021 Pre-fail Always - 7041 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 414 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 087 087 000 Old_age Always - 9806 10 Spin_Retry_Count 0x0032 100 100 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 - 71 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 51 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1122 194 Temperature_Celsius 0x0022 115 111 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 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 Short offline Fatal or unknown error 10% 9806 - 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.
February 8, 201610 yr Hi. Sorry you're having issues. A few things though .... - I would NOT have taken your Parity disk offline. It is my understanding that while your parity check may have failed (if that is indeed what has happened) then having a failed disk and parity enabled keeps your data accessible (also allowing for you to rebuild that drive from the parity drive and the remaining drives assuming they are good and you are not unfortunate enough to have another failure). Not sure I would re-enable it now having taken it offline - perhaps someone else can chime in!? - As for the disk in question it looks FINE to me!? Any chance there could be power / cable issues? Has it been running fine for a long time or is this following a change / addition? The only things that looks slightly dodge is this: 194 Temperature_Celsius 0x0022 115 111 000 Old_age Always - 37 Note sure what that "111" figure means. I hope that is NOT what the worst case temperature has been!? That is WAY HOT if it is! I might be wrong though! I have looked at mine and it appears that for my Seagates what is reported in that column is the worst case temperature figure! So I hope your drive has never got to 111'C!! BUT to address your query, my advice would be STOP what you're doing. I believe your data is not in a protected state right (The fact is that none of your drives are protected by parity as you have disabled it) now and I don't know the best procedure is for you to recover. Don't make any more config changes. Grab your diagnostics file (via Tools Menu in the GUI) and post it. I would be asking for help just like you. The community will respond in fine fashion I am sure!
February 8, 201610 yr The temp attribute is fine, as the 115 and 111 are internal manufacturer values (the raw value is ok at 37C) That said if this is the smart report for the parity. I'd consider having some kind of manufacturer diagnostics done on it ASAP. The drive doesn't seem that old yet (under 2years of continuous operation) but the fact that SMART testing is failing miserably with an unknown reason is really bad in my opinion. I have a drive whose having some unreadable sectors and the smart test can't get past it either.
February 8, 201610 yr Community Expert Seems to be Disk4 reporting errors and SMART failure not parity. The SMART he posted however looks good and it is not clear that it is for Disk4. Having removed parity it will not be possible to rebuild disk4 in a normal way of course. Whether it's necessary or not and what might be done to recover the data we will leave for later. Go to Tools - Diagnostics and post the complete diagnostics zip. Like danioj said quite possibly just a connection issue and you should not have removed parity. Please ask before you do anything if you aren't sure.
February 9, 201610 yr Author the smart should be for the failing disk 4 the parity was added originally at which point it wanted to do a sync which it started to do but failed, I am assuming because disk4 gave an error. Once it failed i was locked out of enabling it back on the main screen with a green symbol hence why i opted just to leave it disabled for now. I can still access the data off disk4, so my strategy is: 1. move all data from disk4 and leave it blank 2. unshare disk 4 from any existing shares 3. shrink array and remove the disk4 from configuration by doing a new config via Tool re-add disk 1,2,3 in order to array (data was in-tack) re-add party back to array without the disk4 I am under the assumption that the data and the shares on disk 1,2, 3 would remain as well as existing share mappings, parity should sync fine providing all remaining disks including parity are not faulty. Can someone please validate above? especially the part of a new config without existing parity assigned would leave data in tack providing the disks are added to each slot correctly
February 9, 201610 yr Community Expert How much data do you have on disk4? If it is very much you could go ahead and get everything else to parity-protected status and then mount it outside the array with the Unassigned Devices plugin and move the data off it that way.
February 9, 201610 yr Author How much data do you have on disk4? If it is very much you could go ahead and get everything else to parity-protected status and then mount it outside the array with the Unassigned Devices plugin and move the data off it that way. so what you mean is, unassign disk4 and sync parity without it? wouldn't it then say its missing from the array unless i do a new disk config? or are you suggesting the below ij order: 1. removing disk4 from array (with remaining data still there as is now) 2. new disk config with disk4 unassigned from array 3. add parity back in after disk 1,2,3 have been re-added in order. then add parity and sync. move remaining disk 4 data via unassigned devices? if so can you please verify that a new disk config without a parity which need to happen first would leave disk 1,2,3 data in tack and associated shares?
February 9, 201610 yr Community Expert After New Config all of the data will be intact. The only thing that will happen is parity will be built when you start the array. Make very sure you don't assign a data disk to the parity slot. Still not clear there is anything wrong with the disk though. The reason I questioned whether you had given us the right SMART report is because there is nothing in it that indicates a problem, and you didn't include anything from the report that would have identified it as disk4 as seen in your screenshot. No matter, after you get the array protected and get the data from the disk you can preclear it to see if it passes.
February 9, 201610 yr Author Thanks for reply, I think you are correct about the smart test, I've run a short and long SMART test on disk4 and it hangs on 90% today and its been a few hours. I got confused, I put it down to stress over problem and data loss at the time of incident. I am assuming it won't compete. Yesterday I recall it error-ed out stating it can't complete. Funny thing is... When the disk was much fuller before i started moving data off it it threw a lot of errors on the disk as per my original screenshot. Today it only reported 1 error after reboot and the transfer so far have not interrupted for the last 5 hours. Would that have anything to do with a potential bad cluster on the disk that it now bypassed, seems strange but it certainly underlines a problem with the drive i suppose.
February 9, 201610 yr Community Expert Still haven't seen anything that clearly indicates a bad drive instead of a bad connection, cable, port, controller, etc. Maybe if you post a diagnostic by going to Tools - Diagnostics.
February 9, 201610 yr Community Expert If you're not running one of the latest releases disk can hang SMART test by spining down, I believe below 6.1.4
February 9, 201610 yr Author Im on 6.1.7 diagnostics attached hangs on 90% on disk4 only all other disks pass here is the smart report again for the disk4, got the message "Errors occurred - Check SMART report" here it is below: smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.15-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD60EFRX-68MYMN1 Serial Number: WD-WX11D4414078 LU WWN Device Id: 5 0014ee 003debbe0 Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: Not in smartctl database [for details use: -P showall] 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: Wed Feb 10 10:33:31 2016 AEDT 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: ( 49) A fatal error or unknown test error occurred while the device was executing its self-test routine and the device was unable to complete the self-test routine. Total time to complete Offline data collection: ( 60) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 6) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) 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 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 196 021 Pre-fail Always - 6033 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 418 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 9841 10 Spin_Retry_Count 0x0032 100 100 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 - 73 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 53 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1126 194 Temperature_Celsius 0x0022 114 111 000 Old_age Always - 38 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 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 Short offline Fatal or unknown error 10% 9832 - # 2 Extended offline Aborted by host 10% 9831 - # 3 Short offline Fatal or unknown error 10% 9806 - 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. n54l-diagnostics-20160210-0722.zip
Archived
This topic is now archived and is closed to further replies.