wgstarks Posted October 17, 2014 Share Posted October 17, 2014 I had a sata drive (disk2) appear as Not Installed. I've used cp to copy the data from that drive to another one before I try and get the drive back. I'm not sure the best way to proceed from here? I know I need to remove disk2 from parity. Would new config be the best way to do this? If I am able to get the drive back what's the best way to delete the data that's on the drive? Preclear? Appreciate any advice. Link to comment
Chris Pollard Posted October 17, 2014 Share Posted October 17, 2014 What does smart say about the drive? Anything in syslog as to why the drive went away? Link to comment
wgstarks Posted October 17, 2014 Author Share Posted October 17, 2014 I had the enclosure laying out on the floor for several days getting knocked and shoved while I setup a new rack. I couldn't get a smart report for the drive but wouldn't be too surprised if it comes back online when I open the enclosure and reseat the sata cables and disk. Wanted to do the copy first though, just to make sure I didn't lose anything. Seemed like the safest approach. Just not really sure what's next? Link to comment
dikkiedirk Posted October 17, 2014 Share Posted October 17, 2014 I had the enclosure laying out on the floor for several days getting knocked and shoved while I setup a new rack. I couldn't get a smart report for the drive but wouldn't be too surprised if it comes back online when I open the enclosure and reseat the sata cables and disk. Wanted to do the copy first though, just to make sure I didn't lose anything. Seemed like the safest approach. Just not really sure what's next? Learn from this. Never leave such sensitive equipment laying on the floor while working around it. Put it away safely. Just check the inside, reseat cables, check connections etc, etc. Big chance you might get away with it. Link to comment
wgstarks Posted October 17, 2014 Author Share Posted October 17, 2014 Thanks. Yes I wish that had been possible too. I guess I'm not being exact enough with my question. 1) How do I remove disk2 from parity now that I have copied all the data to another disk? 2) What is the best way to erase the data from disk2 if I am able to get it back online? Link to comment
Chris Pollard Posted October 17, 2014 Share Posted October 17, 2014 New config and don't add the broken drive back into the array. You are at risk of losing data if another drive fails during this process. Instructions are in the FAQ for this assuming you are running 5.x Once the broken drive is outside the array then you can preclear / test to your hearts content. Personally I would do this in a different machine. Link to comment
wgstarks Posted October 17, 2014 Author Share Posted October 17, 2014 Thanks Chris. A preclear will erase any data on the drive right? Link to comment
wgstarks Posted October 18, 2014 Author Share Posted October 18, 2014 Update: managed to get a smart report. To me it doesn't look good, but to be honest I don't really understand them that well. smartctl -a -d ata /dev/sdl (--) 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: Hitachi Deskstar 5K3000 Device Model: Hitachi HDS5C3030ALA630 Serial Number: MJ1311YNG47SPA LU WWN Device Id: 5 000cca 228c1eea1 Firmware Version: MEAOA5C0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5700 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Oct 17 20:26:06 2014 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: (35768) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 596) minutes. SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 129 129 054 Pre-fail Offline - 132 3 Spin_Up_Time 0x0007 126 126 024 Pre-fail Always - 552 (Average 551) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 721 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 051 051 067 Pre-fail Always FAILING_NOW 524 8 Seek_Time_Performance 0x0005 132 132 020 Pre-fail Offline - 32 9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 24495 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 104 192 Power-Off_Retract_Count 0x0032 046 046 000 Old_age Always - 65535 193 Load_Cycle_Count 0x0012 031 031 000 Old_age Always - 83702 194 Temperature_Celsius 0x0002 162 162 000 Old_age Always - 37 (Min/Max 21/43) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 29 SMART Error Log Version: 1 ATA Error Count: 29 (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 29 occurred at disk power-on lifetime: 21074 hours (878 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 -- -- -- -- -- -- -- 84 51 61 cf 80 df 0e Error: ICRC, ABRT 97 sectors at LBA = 0x0edf80cf = 249528527 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 30 7e df e0 00 1d+06:06:13.212 READ DMA EXT 25 00 00 30 7a df e0 00 1d+06:06:13.118 READ DMA EXT 25 00 00 30 76 df e0 00 1d+06:06:13.117 READ DMA EXT 25 00 48 e8 72 df e0 00 1d+06:06:13.094 READ DMA EXT 25 00 00 e8 6e df e0 00 1d+06:06:13.093 READ DMA EXT Error 28 occurred at disk power-on lifetime: 21074 hours (878 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 -- -- -- -- -- -- -- 84 51 81 1f 71 eb 0d Error: ICRC, ABRT 129 sectors at LBA = 0x0deb711f = 233533727 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 80 20 71 eb ed ff 1d+06:04:11.268 READ DMA EXT 25 00 00 a0 6e eb e0 00 1d+06:04:11.255 READ DMA EXT 25 00 00 a0 6a eb e0 00 1d+06:04:11.254 READ DMA EXT 25 00 60 38 69 eb e0 00 1d+06:04:11.253 READ DMA EXT 25 00 00 38 65 eb e0 00 1d+06:04:11.252 READ DMA EXT Error 27 occurred at disk power-on lifetime: 21074 hours (878 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 -- -- -- -- -- -- -- 84 51 81 57 c7 a0 0d Error: ICRC, ABRT 129 sectors at LBA = 0x0da0c757 = 228640599 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 80 58 c7 a0 ed ff 1d+06:03:30.433 READ DMA EXT 25 00 00 d8 c4 a0 e0 00 1d+06:03:30.420 READ DMA EXT 25 00 00 d8 c0 a0 e0 00 1d+06:03:30.419 READ DMA EXT 25 00 00 d8 bc a0 e0 00 1d+06:03:30.417 READ DMA EXT 25 00 d8 00 ba a0 e0 00 1d+06:03:30.405 READ DMA EXT Error 26 occurred at disk power-on lifetime: 21074 hours (878 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 -- -- -- -- -- -- -- 84 51 71 17 43 11 0d Error: ICRC, ABRT 113 sectors at LBA = 0x0d114317 = 219235095 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 70 18 43 11 ed ff 1d+06:02:20.101 READ DMA EXT 25 00 00 88 3f 11 e0 00 1d+06:02:20.087 READ DMA EXT 25 00 c8 c0 3d 11 e0 00 1d+06:02:20.059 READ DMA EXT 25 00 00 c0 39 11 e0 00 1d+06:02:20.058 READ DMA EXT 25 00 00 c0 35 11 e0 00 1d+06:02:20.057 READ DMA EXT Error 25 occurred at disk power-on lifetime: 20900 hours (870 days + 20 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 -- -- -- -- -- -- -- 84 51 b1 bf 9a 09 00 Error: ICRC, ABRT 177 sectors at LBA = 0x00099abf = 629439 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 70 98 09 e0 00 00:25:15.079 READ DMA EXT 25 00 00 70 94 09 e0 00 00:25:15.078 READ DMA EXT 25 00 00 70 90 09 e0 00 00:25:15.064 READ DMA EXT 25 00 00 70 8c 09 e0 00 00:25:15.061 READ DMA EXT 25 00 00 70 88 09 e0 00 00:25:15.053 READ DMA EXT 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. Should I still try and use this drive? Link to comment
RobJ Posted October 18, 2014 Share Posted October 18, 2014 Update: managed to get a smart report. To me it doesn't look good, but to be honest I don't really understand them that well. ...[snipped]... === 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. ...[snipped]... 7 Seek_Error_Rate 0x000b 051 051 067 Pre-fail Always FAILING_NOW 524 ...[snipped]... Should I still try and use this drive? Nope, it has failed, is not usable. You should have no problems with an RMA, just show this SMART report. Link to comment
wgstarks Posted October 18, 2014 Author Share Posted October 18, 2014 Thanks for the info. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.