ilovegoodnugz Posted March 27, 2016 Share Posted March 27, 2016 So I just started rebuilding a 2tb data drive that failed and it's going 1% per day, I would wait it out but I need to move in 2 days and I'm pretty sure it won't finish. Can I stop the rebuild turn off the server, move and continue the rebuild? Thanks Quote Link to comment
trurl Posted March 27, 2016 Share Posted March 27, 2016 Assuming everything is working as it should, you can't resume a rebuild, but you can restart a rebuild. However, you obviously have problems if it is going that slowly. Post a syslog. Quote Link to comment
ilovegoodnugz Posted March 27, 2016 Author Share Posted March 27, 2016 So looking at the syslog it looks like Disk6 has a ton of errors while trying to rebuild Disk1, is all hope lost? Thanks syslog_copy.txt Quote Link to comment
trurl Posted March 28, 2016 Share Posted March 28, 2016 Possibly just bad connection to disk6 caused when you were changing disks. Check all connections and try again. If it still happens post SMART for disk6. Quote Link to comment
ilovegoodnugz Posted March 28, 2016 Author Share Posted March 28, 2016 smart on webgui is a red thumbs down. Can you tell me how to obtain a smart report to post? Thanks Quote Link to comment
ilovegoodnugz Posted March 28, 2016 Author Share Posted March 28, 2016 root@Tower:~# smartctl -a -A /dev/sde smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF) Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA2076362 LU WWN Device Id: 5 0014ee 655ef0897 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Mon Mar 28 08:43:16 2016 EDT 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. 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: (37680) 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: ( 363) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status 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 001 001 051 Pre-fail Always FAILING_NOW 636056 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1108 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 86 5 Reallocated_Sector_Ct 0x0033 179 179 140 Pre-fail Always - 406 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 045 045 000 Old_age Always - 40548 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 - 83 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 43 193 Load_Cycle_Count 0x0032 195 195 000 Old_age Always - 15557 194 Temperature_Celsius 0x0022 121 114 000 Old_age Always - 29 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 365 197 Current_Pending_Sector 0x0032 196 196 000 Old_age Always - 1380 198 Offline_Uncorrectable 0x0030 200 196 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 001 001 000 Old_age Offline - 428425 SMART Error Log Version: 1 ATA Error Count: 10 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 10 occurred at disk power-on lifetime: 35115 hours (1463 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 50 85 19 ef Error: UNC at LBA = 0x0f198550 = 253330768 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 f8 84 19 ef 08 00:36:07.823 READ DMA c8 00 00 f8 7b 19 ef 08 00:36:07.808 READ DMA Error 9 occurred at disk power-on lifetime: 35115 hours (1463 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 b8 3f e3 ed Error: UNC at LBA = 0x0de33fb8 = 232996792 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 a8 3f e3 ed 08 00:33:03.707 READ DMA c8 00 00 a8 36 e3 ed 08 00:33:03.665 READ DMA Error 8 occurred at disk power-on lifetime: 35114 hours (1463 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 10 c0 32 ed Error: UNC at LBA = 0x0d32c010 = 221429776 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 a8 bf 32 ed 08 00:31:32.467 READ DMA c8 00 00 a8 b6 32 ed 08 00:31:32.452 READ DMA Error 7 occurred at disk power-on lifetime: 35114 hours (1463 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 20 14 13 ed Error: UNC at LBA = 0x0d131420 = 219354144 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 f8 13 13 ed 08 00:31:08.487 READ DMA c8 00 00 f8 0a 13 ed 08 00:31:08.472 READ DMA Error 6 occurred at disk power-on lifetime: 35114 hours (1463 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 00 cd ac ec Error: UNC at LBA = 0x0caccd00 = 212651264 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 f8 cc ac ec 08 00:29:42.928 READ DMA c8 00 00 f8 c3 ac ec 08 00:29:42.181 READ DMA 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. root@Tower:~# Quote Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 Disk 6 is bad, IMO your best option, if you have the space, is canceling the rebuild, start the array with no disk assigned to disk1 and copy everything you can from the emulated disk1 and disk6. Success will depend on how bad disk6 is. Quote Link to comment
ilovegoodnugz Posted March 28, 2016 Author Share Posted March 28, 2016 So it actually just finished, and Disk1 looks pretty good except it is showing faulty and I cannot run smart reports but it mounts and i can access the data, should I get another disk1 or should I try to rebuild disk6? Man this keeps getting worse. Thanks Quote Link to comment
trurl Posted March 28, 2016 Share Posted March 28, 2016 So it actually just finished, and Disk1 looks pretty good except it is showing faulty and I cannot run smart reports but it mounts and i can access the data, should I get another disk1 or should I try to rebuild disk6? Man this keeps getting worse. Thanks Do you mean disk1 rebuild finished? What exactly do you mean it is showing faulty? Post a SMART for that disk. Quote Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 It didn't finish rebuilding, it probably dropped offline as there are also errors for disk1, is it a new disk? You'll need to power cycle the server to get a SMART report. Quote Link to comment
ilovegoodnugz Posted April 3, 2016 Author Share Posted April 3, 2016 So it looked like disk 1 is fine, can I replace and rebuild the failing disk6 using the original parity now that 1 is whole? Thanks Quote Link to comment
JorgeB Posted April 4, 2016 Share Posted April 4, 2016 Is disk1 showing green or orange? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.