June 10, 201115 yr So I had a drive that was not part of my array fail. What, if any, tools are available within unRAID to diagnose and possibly fix the drive? Drive is recognized as present, but has no partitions. If possible, I would like to recover the data from the drive and then copy it to the array. Any help would be greatly appreciated. TIA, erik Smart status test of drive: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD10EAVS-00D7B1 Serial Number: WD-WCAU45203817 Firmware Version: 01.01A01 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Jun 9 19:21:26 2011 PDT 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: (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: (24000) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) 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 198 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 165 155 021 Pre-fail Always - 6741 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2949 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 3 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 078 078 000 Old_age Always - 16486 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 - 61 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 15 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2949 194 Temperature_Celsius 0x0022 118 090 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 197 197 000 Old_age Always - 3 197 Current_Pending_Sector 0x0032 192 192 000 Old_age Always - 1454 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 195 000 Old_age Offline - 0 SMART Error Log Version: 1 Warning: ATA error count 36940 inconsistent with error log pointer 1 ATA Error Count: 36940 (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 36940 occurred at disk power-on lifetime: 16486 hours (686 days + 22 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 08 00 10 00 e0 Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 08 00 10 00 00 00 2d+01:07:21.260 READ DMA ef 10 02 00 00 00 00 00 2d+01:07:21.260 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 00 00 2d+01:07:21.259 IDENTIFY DEVICE ef 03 42 00 00 00 00 00 2d+01:07:21.259 SET FEATURES [set transfer mode] Error 36939 occurred at disk power-on lifetime: 16486 hours (686 days + 22 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 08 00 10 00 e0 Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 08 00 10 00 00 00 2d+01:07:21.258 READ DMA ef 10 02 00 00 00 00 00 2d+01:07:21.258 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 00 00 2d+01:07:21.257 IDENTIFY DEVICE ef 03 42 00 00 00 00 00 2d+01:07:21.257 SET FEATURES [set transfer mode] Error 36938 occurred at disk power-on lifetime: 16486 hours (686 days + 22 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 08 00 10 00 e0 Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 08 00 10 00 00 00 2d+01:07:21.256 READ DMA ef 10 02 00 00 00 00 00 2d+01:07:21.256 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 00 00 2d+01:07:21.256 IDENTIFY DEVICE ef 03 42 00 00 00 00 00 2d+01:07:21.256 SET FEATURES [set transfer mode] Error 36937 occurred at disk power-on lifetime: 16486 hours (686 days + 22 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 08 00 10 00 e0 Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 08 00 10 00 00 00 2d+01:07:21.255 READ DMA ef 10 02 00 00 00 00 00 2d+01:07:21.255 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 00 00 2d+01:07:21.253 IDENTIFY DEVICE ef 03 42 00 00 00 00 00 2d+01:07:21.253 SET FEATURES [set transfer mode] Error 36936 occurred at disk power-on lifetime: 16486 hours (686 days + 22 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 08 00 10 00 e0 Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 08 00 10 00 00 00 2d+01:07:21.252 READ DMA ef 10 02 00 00 00 00 00 2d+01:07:21.252 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 00 00 2d+01:07:21.251 IDENTIFY DEVICE ef 03 42 00 00 00 00 00 2d+01:07:21.251 SET FEATURES [set transfer mode] 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.
June 10, 201115 yr So I had a drive that was not part of my array fail. What, if any, tools are available within unRAID to diagnose and possibly fix the drive? The entire point of a protected array is to prevent data loss when there is a drive failure. An orphaned drive sitting outside of the array is all alone, with no protection of any kind. unRAID is not a data recovery software, so beyond having the data mined from the drive at a huge cost by a recovery company, I don't think you have many options. Joe and some of the guys might have some thoughts related to the mechanics of the drive itself, but that won't be an unRAID tool or feature. Perhaps you meant what kind of Linux tools are available?
June 10, 201115 yr Author Yes, I realize that unRAID is not data recovery software. The drive in question failed while I was still acquiring parts to build my unRAID server (bad karma, I guess). I am a linux noob, and don't know much about data recovery either. Please excuse any semantics type errors in my posts. What I am asking the community is this: What might you recommend I try to see if some sort of data on this failed drive might be recoverable? I want to try using tools that are availabel/can be made to work with the unRAID box. The Mac and Windows boxes I connected this to did not properly recognize the drive (Mac sees a 0TB drive, Windows sees nothing). At least unRAID sees a WD 1TB drive, although no partitions are seen. Any help would be greatly appreciated. erik
June 10, 201115 yr Yes, I realize that unRAID is not data recovery software. The drive in question failed while I was still acquiring parts to build my unRAID server (bad karma, I guess). I am a linux noob, and don't know much about data recovery either. Please excuse any semantics type errors in my posts. What I am asking the community is this: What might you recommend I try to see if some sort of data on this failed drive might be recoverable? I want to try using tools that are availabel/can be made to work with the unRAID box. The Mac and Windows boxes I connected this to did not properly recognize the drive (Mac sees a 0TB drive, Windows sees nothing). At least unRAID sees a WD 1TB drive, although no partitions are seen. Any help would be greatly appreciated. erik What does this output? fdisk -lu /dev/sdX (where sdX = your drive) What kind of file system was on the disk? If it is at all readable you should be able to use any of the disk repair utilities... It all depends on what kind of file-system was on the disk.
June 10, 201115 yr Author fdisk -lu /dev/sdX returns nothing What kind of file system was on the disk? NTFS I had my IT guy at work look at it and he said he used some utilities on a HIRENS boot disk to check it out and came back with nothing. I am not sure how hard he tried, though. This is my last ditch effort before I try to RMA it, I believe it is still under WD warranty. I was able to recover many of the files that were on it (the files were on another disk that I had transferred them from a few months back, luckily), but I will lose about 4 months worth of recent pictures if I can't fix the drive. All other data was iTunes and is all recoverable by re-ripping the cds.
June 10, 201115 yr fdisk -lu /dev/sdX returns nothing What kind of file system was on the disk? NTFS I had my IT guy at work look at it and he said he used some utilities on a HIRENS boot disk to check it out and came back with nothing. I am not sure how hard he tried, though. This is my last ditch effort before I try to RMA it, I believe it is still under WD warranty. I was able to recover many of the files that were on it (the files were on another disk that I had transferred them from a few months back, luckily), but I will lose about 4 months worth of recent pictures if I can't fix the drive. All other data was iTunes and is all recoverable by re-ripping the cds. Something to try: http://geeksaresexy.blogspot.com/2006/01/freeze-your-hard-drive-to-recover-data.html and http://help.lockergnome.com/general/modules.php?name=Forums&file=viewtopic&t=43993
June 10, 201115 yr Something to try: http://geeksaresexy.blogspot.com/2006/01/freeze-your-hard-drive-to-recover-data.html This worked for me twice out of 4 drives. Granted not ALL data was available to me on the second drive, but enough of it was, or rather, the "stuff" I reallllly wanted to get from it. Though, I would recommend wrapping the hard drive in newspaper, then placing it in the freezer storage bag (don't go cheap, use the ziplocks). This also works for rejuvenating laptop batteries (somewhat).
June 10, 201115 yr I've actually had luck a couple of times with SpinRite: http://www.grc.com/sr/spinrite.htm I don't think this has seen a new version since 2004, but I don't think it needs it. In the past, I've used this to bring dead laptop drives back from the grave long enough to pull an image to restore onto a new drive. It worked like a charm. As long as your drive spins and is recognized by the BIOS when your PC posts, then it is worth a shot.
June 10, 201115 yr I've actually had luck a couple of times with SpinRite: http://www.grc.com/sr/spinrite.htm I don't think this has seen a new version since 2004, but I don't think it needs it. In the past, I've used this to bring dead laptop drives back from the grave long enough to pull an image to restore onto a new drive. It worked like a charm. As long as your drive spins and is recognized by the BIOS when your PC posts, then it is worth a shot. +1 for spinrite... I've used it several times as well with good results.
June 12, 201115 yr Author Well, I got SpinRite, but it says it can't access the entire drive. Not sure why, as BIOS recognizes it, just with no partitions. unMenu MyMain sees it as a new raw drive. Sent an email out to GRC to see if they have any recommendations before I give up and RMA it. At least after the RMA I will have another 1TB to add to my array!!
June 12, 201115 yr Hook up the drive as a slave in another Windows computer since it is NTFS. Try to access it. If you can't, then maybe the drive is just way too burned out to data recover anything unless done the professional way which costs lots of money.
Archived
This topic is now archived and is closed to further replies.