April 3, 201115 yr Alright here it goes wife was cleaning the office and knocked over the unRAID server. It landed upside down, but appeared everything was still running. Shortly their after i was unable to connect. Restarted the machine, unraid began a parity check, and the parity drive was labeled as a new drive. I have enclosed the syslog, but it appears that soothing has severely gone wrong with either the mobo or parity drive. I let unraid run a parity check but syslog is returning numerous errors. I have ordered a new mobo and will see if that will correct the problem. Any help would be appreciated thanks in advance. PS im unable to attach the sys log for the parity check because of the filesize. I have enclosed one of the subsequent restarts. This is the error that kept showing up during the parity check: Apr 3 00:11:23 Tower kernel: ata6.01: status: { DRDY } Apr 3 00:11:28 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Apr 3 00:11:33 Tower kernel: ata6: device not ready (errno=-16), forcing hardreset Apr 3 00:11:33 Tower kernel: ata6: soft resetting link Apr 3 00:11:33 Tower kernel: ata6.01: configured for UDMA/33 Apr 3 00:11:33 Tower kernel: ata6.01: device reported invalid CHS sector 0 Apr 3 00:11:33 Tower kernel: ata6: EH complete Apr 3 01:19:13 Tower kernel: md: sync done. time=37802sec rate=51677K/sec Apr 3 01:19:13 Tower kernel: md: recovery thread sync completion status: 0 Apr 3 01:38:19 Tower kernel: ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 3 01:38:19 Tower kernel: ata6.01: failed command: CHECK POWER MODE Apr 3 01:38:19 Tower kernel: ata6.01: cmd e5/00:00:00:00:00/00:00:00:00:00/10 tag 0 Apr 3 01:38:19 Tower kernel: res 40/00:ff:00:00:00/84:01:06:00:00/10 Emask 0x4 (timeout) Apr 3 01:38:19 Tower kernel: ata6.01: status: { DRDY } Apr 3 01:38:24 Tower kernel: ata6: link is slow to respond, please be patient (ready=0) Apr 3 01:38:29 Tower kernel: ata6: device not ready (errno=-16), forcing hardreset Apr 3 01:38:29 Tower kernel: ata6: soft resetting link Apr 3 01:38:30 Tower kernel: ata6.01: both IDENTIFYs aborted, assuming NODEV Apr 3 01:38:30 Tower kernel: ata6.01: revalidation failed (errno=-2) Apr 3 01:38:34 Tower kernel: ata6: soft resetting link Apr 3 01:38:35 Tower kernel: ata6.01: both IDENTIFYs aborted, assuming NODEV Apr 3 01:38:35 Tower kernel: ata6.01: revalidation failed (errno=-2) Apr 3 01:38:40 Tower kernel: ata6: soft resetting link Apr 3 01:38:40 Tower kernel: ata6.01: both IDENTIFYs aborted, assuming NODEV Apr 3 01:38:40 Tower kernel: ata6.01: revalidation failed (errno=-2) Apr 3 01:38:40 Tower kernel: ata6.01: disabled Apr 3 01:38:40 Tower kernel: ata6: EH complete 3 01:50:54 Tower emhttp: mdcmd: write: Input/output error Apr 3 01:50:54 Tower kernel: mdcmd (23): spindown 0 Apr 3 01:50:54 Tower kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -5 Apr 3 01:51:04 Tower emhttp: mdcmd: write: Input/output error Apr 3 01:51:04 Tower kernel: mdcmd (24): spindown 0 Apr 3 01:51:04 Tower kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -5 Apr 3 01:51:14 Tower emhttp: mdcmd: write: Input/output error Apr 3 01:51:14 Tower kernel: mdcmd (25): spindown 0 Apr 3 01:51:14 Tower kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -5 Apr 3 01:51:24 Tower emhttp: mdcmd: write: Input/output error Apr 3 01:51:24 Tower kernel: mdcmd (26): spindown 0 Apr 3 01:51:24 Tower kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -5 Apr 3 01:51:34 Tower emhttp: mdcmd: write: Input/output error Apr 3 01:51:34 Tower kernel: mdcmd (27): spindown 0 syslog-20110403-072357.txt
April 3, 201115 yr Please check that all the SATA cables are in place (could have been jostled loose in the fall), and then post a SMART report for parity.
April 3, 201115 yr Did you open the box and ensure that all of the cabling was secure? You should also check that the controller cards are securely plugged into the motherboard. If the thing boots and runs a parity check, your motherboard is likely okay. I'd be more worried about the drives. Were you writing to the disks at the time? Were they spun up or down? You should be able to zip and post even a large syslog.
April 3, 201115 yr Step 1 would be to power down, open up the server, and re-seat all the boards and cables. A sudden upside down "stop" would tend to un-plug things. Then, a post of the syslog after the system reboots. Odds are very high there is nothing wrong with the motherboard. Joe L.
April 3, 201115 yr Author Please check that all the SATA cables are in place (could have been jostled loose in the fall), and then post a SMART report for parity. cables are all secure Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD204UI Serial Number: S2H7J1BZA28925 Firmware Version: 1AQ10001 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Sun Apr 3 10:20:34 2011 EDT ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (19680) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003f) 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 100 100 051 Pre-fail Always - 11 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 064 025 Pre-fail Always - 10295 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 413 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 744 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 62 181 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 14258524 191 G-Sense_Error_Rate 0x0022 001 001 000 Old_age Always - 1925512 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 059 000 Old_age Always - 23 (Lifetime Min/Max 17/41) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 086 086 000 Old_age Always - 7670 200 Multi_Zone_Error_Rate 0x002a 001 001 000 Old_age Always - 61935 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 423 SMART Error Log Version: 1 ATA Error Count: 194 (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 194 occurred at disk power-on lifetime: 738 hours (30 days + 18 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 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 0a 00:06:20.163 IDENTIFY DEVICE 00 00 01 01 00 00 00 0a 00:06:20.163 NOP [Abort queued commands] a1 00 00 00 00 00 a0 0a 00:06:20.158 IDENTIFY PACKET DEVICE ec 00 00 00 00 00 a0 0a 00:06:20.158 IDENTIFY DEVICE 00 00 01 01 00 00 00 0a 00:06:20.158 NOP [Abort queued commands] Error 193 occurred at disk power-on lifetime: 738 hours (30 days + 18 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 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 0a 00:06:20.158 IDENTIFY DEVICE 00 00 01 01 00 00 00 0a 00:06:20.158 NOP [Abort queued commands] a1 00 00 00 00 00 a0 0a 00:06:20.153 IDENTIFY PACKET DEVICE ec 00 00 00 00 00 a0 0a 00:06:20.153 IDENTIFY DEVICE 00 00 00 a0 5e e0 e0 0a 00:06:20.153 NOP [Abort queued commands] Error 192 occurred at disk power-on lifetime: 738 hours (30 days + 18 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 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 0a 00:06:20.153 IDENTIFY DEVICE 00 00 00 a0 5e e0 e0 0a 00:06:20.153 NOP [Abort queued commands] e5 00 00 00 00 00 00 0a 00:06:20.112 CHECK POWER MODE e5 00 00 00 00 00 00 0a 00:06:20.102 CHECK POWER MODE e5 00 00 00 00 00 00 0a 00:06:20.092 CHECK POWER MODE Error 191 occurred at disk power-on lifetime: 728 hours (30 days + 8 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 c1 d7 2f a3 e1 Error: ICRC, ABRT at LBA = 0x01a32fd7 = 27471831 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ca 00 00 98 2f a3 e1 0a 00:05:41.510 WRITE DMA 35 00 00 98 2b a3 e0 0a 00:05:41.510 WRITE DMA EXT 35 00 00 98 27 a3 e0 0a 00:05:41.510 WRITE DMA EXT ca 00 00 98 26 a3 e1 0a 00:05:41.510 WRITE DMA 35 00 00 98 22 a3 e0 0a 00:05:41.510 WRITE DMA EXT Error 190 occurred at disk power-on lifetime: 728 hours (30 days + 8 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 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 0a 00:05:41.238 IDENTIFY DEVICE ef 03 42 00 00 00 a0 0a 00:05:41.238 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 0a 00:05:41.238 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 0a 00:05:41.238 IDENTIFY DEVICE 00 00 01 01 00 00 40 0a 00:05:41.238 NOP [Abort queued commands] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 389 - # 2 Short offline Completed without error 00% 380 - # 3 Short offline Completed without error 00% 325 - # 4 Short offline Aborted by host 60% 325 - # 5 Short offline Interrupted (host reset) 80% 311 - # 6 Short offline Completed without error 00% 307 - # 7 Short offline Completed without error 00% 238 - SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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.
April 3, 201115 yr Author Did you open the box and ensure that all of the cabling was secure? You should also check that the controller cards are securely plugged into the motherboard. If the thing boots and runs a parity check, your motherboard is likely okay. I'd be more worried about the drives. Were you writing to the disks at the time? Were they spun up or down? You should be able to zip and post even a large syslog. everything appears to be secure, drives were streaming music to my htpc. syslog-20110403-070310.zip
April 3, 201115 yr Author Step 1 would be to power down, open up the server, and re-seat all the boards and cables. A sudden upside down "stop" would tend to un-plug things. Then, a post of the syslog after the system reboots. Odds are very high there is nothing wrong with the motherboard. Joe L. followed your steps and here is the sys log syslog.txt
April 3, 201115 yr Your smart report looks ok. It may know you dropped it. 191 G-Sense_Error_Rate 0x0022 001 001 000 Old_age Always - 1925512 It still looks to me like you have a cabling problem to this drive. I would recommend replacing the cable with a known good one. It could certainly be that the drive is broken as well. This is one time that the lightning fast WD LCC might have been an advantage.
April 3, 201115 yr Author Your smart report looks ok. It may know you dropped it. 191 G-Sense_Error_Rate 0x0022 001 001 000 Old_age Always - 1925512 It still looks to me like you have a cabling problem to this drive. I would recommend replacing the cable with a known good one. It could certainly be that the drive is broken as well. This is one time that the lightning fast WD LCC might have been an advantage. I will let the drive check parity first and see what happens. If I still get errors I will replace the cable. Hopefully its not the drive. I was planning on upgrading to a new server any how, but obviously I dont want to lose a drive. As I am typing no errors are showing.
April 3, 201115 yr I thought you were getting tons of errors running a parity check? Maybe I missed a step. If the parity check is running, you are not getting sync errors, and your syslog is not indicating disk errors, you should be okay. BTW, this is the first dropped server story in my time on the forums.
April 3, 201115 yr Author When I ran parity yesterday was getting the errors. Today I disconnected all the drives and then reconnected as Joe suggested. So far so good. Hopefully the drive is still good, not fun losing money on a new hard disk.
April 3, 201115 yr if you don't have any parity errors anymore, they miht have been corrected in the first parity check. Were all of your HDs spinning or just the one that you were streaming content to ? HDs can survive large G forces when they're off... and fairly large when they're on too... a drop while writing is bad, drop while reading isn't as bad... i'd run a SMART test on the drive that had your music on it just to be sure.
April 3, 201115 yr m(9.8)h = potential energy in Joules, when mass is in kg and height is in meters. (22.7)(9.(1.82) = 405 Joules ^^ That's my server's potential energy.
April 4, 201115 yr m(9.8)h = potential energy in Joules, when mass is in kg and height is in meters. (22.7)(9.(1.82) = 405 Joules ^^ That's my server's potential energy. More than that if the drives are spinning at the time, apparently... For a disk of mass, M, and radius, R, the moment of inertia, I, is I=MR^2/2. If the disk is spinning with angular speed, ?, its rotational kinetic energy is K.E. = I?^2/2. The angular speed of a disk is related to the speed (VD) of its outer edge by, ? =VD/R. Combing the above equations, the kinetic energy of the disk can be written as, K.E. = MV^2/4. The kinetic energy of a falling mass (m) with speed, v, is, K.E. = mv^2/2 The total kinetic energy of the disk and falling mass is the sum of the individual kinetic energies. The statement of the conservation of energy now reads, mgh = MV^2/4 + mv^2/2 ...with condolences to the OP and his wife.
April 4, 201115 yr Author Well last night the parity checked out well and I spun down the drives for the night. I come home today from work and start to stream music. Server becomes unresponsive and I restart. No my disk 1 is red: Apr 4 18:37:01 Tower kernel: scsi5 : ata_piix (Drive related) Apr 4 18:37:01 Tower kernel: ata5: SATA max UDMA/133 cmd 0x9800 ctl 0x9400 bmdma 0x8400 irq 19 (Drive related) Apr 4 18:37:01 Tower kernel: ata5.00: ATA-8: WDC WD10EACS-00ZJB0, 01.01B01, max UDMA/133 (Drive related) Apr 4 18:37:01 Tower kernel: ata5.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) (Drive related) Apr 4 18:37:01 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Apr 4 18:37:01 Tower kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD10EACS-00Z 01.0 PQ: 0 ANSI: 5 (Drive related) Apr 4 18:37:01 Tower kernel: sd 5:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) (Drive related) Apr 4 18:37:01 Tower kernel: sd 5:0:0:0: [sda] Write Protect is off (Drive related) Apr 4 18:37:01 Tower kernel: sd 5:0:0:0: [sda] Mode Sense: 00 3a 00 00 (Drive related) Apr 4 18:37:01 Tower kernel: sd 5:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related) Apr 4 18:37:01 Tower kernel: sda: sdb1 (Drive related) Apr 4 18:37:01 Tower kernel: sda1 (Drive related) Apr 4 18:37:01 Tower kernel: sd 5:0:0:0: [sda] Attached SCSI disk (Drive related) Apr 4 18:37:01 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host5 (sda) WDC_WD10EACS-00ZJB0_WD-WCASJ0320391 (Drive related) Apr 4 18:37:01 Tower kernel: md: import disk1: [8,0] (sda) WDC WD10EACS-00Z WD-WCASJ0320391 size: 976762552 (Drive related) Apr 4 18:37:02 Tower emhttp: shcmd (5): /usr/local/sbin/set_ncq sda 1 >/dev/null (Drive related) Apr 4 18:37:02 Tower kernel: md1: running, size: 976762552 blocks (Drive related) Apr 4 18:37:03 Tower emhttp: shcmd (10): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>$stuff$1 | logger (Other emhttp) Apr 4 18:39:41 Tower emhttp: shcmd (23): umount /mnt/disk1 >/dev/null 2>$stuff$1 (Other emhttp) Apr 4 18:39:41 Tower emhttp: shcmd (24): rmdir /mnt/disk1 >/dev/null 2>$stuff$1 (Other emhttp) Apr 4 18:39:41 Tower kernel: md1: stopping (Drive related) Apr 4 18:39:52 Tower kernel: md: disk1 removed (unRAID engine) Apr 4 18:39:58 Tower kernel: md1: running, size: 976762552 blocks (Drive related) Apr 4 18:39:58 Tower emhttp: shcmd (37): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>$stuff$1 | logger (Other emhttp) Apr 4 18:40:09 Tower emhttp: shcmd (51): umount /mnt/disk1 >/dev/null 2>$stuff$1 (Other emhttp) Apr 4 18:40:09 Tower emhttp: shcmd (52): rmdir /mnt/disk1 >/dev/null 2>$stuff$1 (Other emhttp) Apr 4 18:40:09 Tower kernel: md1: stopping (Drive related) Apr 4 18:40:16 Tower kernel: md: import disk1: [8,0] (sda) WDC WD10EACS-00Z WD-WCASJ0320391 size: 976762552 (Drive related) Apr 4 18:40:16 Tower kernel: md: disk1 replaced (unRAID engine) Apr 4 18:40:27 Tower emhttp: shcmd (62): /usr/local/sbin/set_ncq sda 1 >/dev/null (Drive related) Apr 4 18:40:27 Tower kernel: md1: running, size: 976762552 blocks (Drive related) Apr 4 18:40:28 Tower emhttp: shcmd (66): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>$stuff$1 | logger (Other emhttp) Apr 4 18:40:28 Tower kernel: md: recovery thread rebuilding disk1 ... (unRAID engine) My disk were reading not writing because I was streaming music. I have ordered a new mobo and we will see what happens.
April 5, 201115 yr I have to say that I'm puzzled - you have a syslog with several error messages all indicating the same drive (it is the drives/mechanical items which are most likely to suffer from impact), yet you decide to replace the mobo? I have to believe that you have another motivation for purchasing a new mother board ... and, of course, the wife can't complain - she was the one who caused the problem in the first place ... mmmm, I like your thinking!
April 5, 201115 yr While responding in another thread about local computer stores, I had an idea for you. Not trying to get your hopes up, but ... Try taking to drives to a local computer store. Obviously they range in experience, but these guys repair computers day in, day out. They've likely seen it all - from falling over, Pepsi syndromes, overeheating, exploding PSUs. things shorting out, maybe even a shorted out molex - and probably stranger things than any of us can imagine. If anyone short of the high dollar data recovery service is going to be able to get your drive running again, it would be a good local computer repair shop. Make a free USB stick for them to boot unRAID, and they may just perform a miracle and recover your data. I had a neighbor that had a failing disk with all his data. He invited me over and 2 1/2 hours later I had made no progress. I tried all my tricks including a different computer, various controllers, different PSU, different cables - even put it in the freezer as per instructions on the internet. Nada. He said he'd take it to the local computer store and let them try. I told him the odds were against him, thinking he didn't have a chance in hell. Next day he had the drive completely restored to a new disk, didn't even need to reinstall the OS. Still have no idea what they did. If you are going to recover your data, they may likely be your best bet. Might cost you $50 to try, but likely a worthwhile gamble. You should post area where you live to see if people have recommendations of local shops they've used and had good experiences with.
April 6, 201115 yr Author Thanks brother for the advice. I just received the new mobo and the drives are up and running with no errors. I'm going to purchase a spare 2 tb drive just in case the drive is damaged. Mobo was a planned upgrade anyway. Blame her and I get a new board went with the 880gma-e45 with a sargas 2.7 processor 45 watt runs super quiet.
Archived
This topic is now archived and is closed to further replies.