February 17, 201511 yr Hi, So my parity drive failed a while ago and I just replaced it with a 6TB drive. After plugging it in, I started the parity rebuild last night and it was all going swimmingly until I woke up and checked the status. It estimated about a day to complete the whole thing. Now this morning when I checked, Disk 6 had 128 errors and the speed has dropped to anything from 5mb to 1mb. I tried reading up on the error and everything I can find says it's okay to have that since it'll just get rewritten to another sector with the parity as a reference. But I'm trying to rebuild my parity and not sure what the read error means here. Does that mean data is lost? And if so, is there a way to figure out which data? Since it's my latest disk, I may still be able to replace what's bad. Also, why did the parity check speed drop so much? Is that an indication of something else that's wrong? SO many problems and I have no idea what to do Thanks!
February 17, 201511 yr I would expect that the parity speed dropped because of problems reading the disk that indicated it had errors. I would suggest that you post a Syslog and a SMART report for the drive indicating it has errors. This might allow for better guidance to be given.
February 17, 201511 yr Author Do I need to run a (long or short) smart test? Or can I just post the existing smart report? Thanks
February 17, 201511 yr Do I need to run a (long or short) smart test? Or can I just post the existing smart report? Jut a report gibing the current values of all the SMART attributes should be enough. That will show whether any values are indicating potential issues.
February 17, 201511 yr Author Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354552 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354560 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354568 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354576 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354584 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354592 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354600 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354608 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354616 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354624 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354632 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354640 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354648 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354656 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354664 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354672 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354680 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354688 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354696 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354704 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354712 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=3144354720 Feb 17 09:05:49 Tower kernel: md: disk6 read error, sector=314435472 So that's that syslog looks like Can't post the whole thing since it's millions of the same thing. Tried to get a smart report, but /dev/sdd is missling alltogher! I guess that's not a good sign Could this possibly be a bad cable issue? Or am I completely screwed and the drive is gone and all data lost
February 17, 201511 yr Author Sigh. So restarted the server and now disk6 says "unformatted" with a redball. This is the smart report: Is there any hope for data recovery? Even if it's just the file lists. Thanks! smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: S3008HXA LU WWN Device Id: 5 000c50 06d3abfb6 Firmware Version: CC54 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Device is: In smartctl database [for details use: -P show] 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: Tue Feb 17 19:10:16 2015 EST 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 97) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 512) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) SCT Status supported. 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 112 099 006 Pre-fail Always - 42823784 3 Spin_Up_Time 0x0003 098 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 093 093 020 Old_age Always - 7429 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 6167637 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3648 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 27 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 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 052 045 Old_age Always - 30 (Min/Max 29/30) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 3681 193 Load_Cycle_Count 0x0032 085 085 000 Old_age Always - 30571 194 Temperature_Celsius 0x0022 030 048 000 Old_age Always - 30 (0 19 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 - 553h+11m+07.483s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 11280352946 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 67732071656 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): 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.
Archived
This topic is now archived and is closed to further replies.