One of the drives in my NAS just failed and because I was too lazy to set up RAID, I am now in a desperate state of trying to recover data ! Costly lesson this might be. Anyways, I connected a serial terminal with the PCB attached and received the following errors. The drive spins up spits out these errors and just stops responding after that. Here's the dump:

Boot 0x40M
Spin Up
FAIL Servo Op=0100 Resp=0003
ResponseFrame 0880 00FF 06CC 3300 0008 0000 0000 0000 0E8A 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0010
FAIL Servo Op=0100 Resp=0003
ResponseFrame 0100 0074 06CC 3300 0008 0000 0000 0000 0E8A 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 0080 0075 06CC 3340 0008 0000 0000 0000 0E7D 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001C 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 0000 0075 06CC 3380 0008 0000 0000 0000 0E6F 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001C 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 0000 0075 06CC 32C0 0008 0000 0000 0000 0E98 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 0000 0075 06CC 3200 0008 0000 0000 0000 0EC2 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame FFC0 0075 06CC 3280 0008 0000 0000 0000 0EA6 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame FFC0 0075 06CC 3280 0008 0000 0000 0000 0EA6 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame FF80 0075 06CC 32C0 0008 0000 0000 0000 0E98 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame FF40 0075 06CC 3280 0008 0000 0000 0000 0EA6 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame FEC0 0076 06CC 3280 0008 0000 0000 0000 0EA6 0000 0000 0000 0000 0000 0000 0000 4EA5 D8FB A300 46CA 720B 899B F7B9 BCD5 FD3A 1CF9 FFFF 007F 0000 0000 001D 0004 0000

Any advice from the gurus out there ?

95% game over for DIY.
Complete diagnose needed, not with terminal only.

Hi! There was the exact same problem with the hard drive. Tell me, what can it be? Attach 2 files, the sound of the disc and a screenshot of the terminal.
Sound: https://www.dropbox.com/s/ijwen8pbo8fn2ax/audio.mp3

Same diagnose.
No DIY solution.

Thanks for the advice.

I am going to give it one last ditch effort as I am not going to spend a large amount of cash on data recovery services. So I am going to ask a couple of newbie questions, so please be patient. I am not adept at understanding HDDs and all their ins and outs but am adept with electronics.

I would like to do a controller board swap as I have another identical hard disk that I purchased around on the same time with the same firmware and has the same build months. I have read online that a firmware transfer is needed. On inspection on the board I found a 25FS406 serial flash memory which I presume holds all of the drive specific information. I can either remove the chip or read it in-circuit and transfer the data contents to a a working controller board.

So before I go through all that effort, I would like to know if it's worth the trouble ? Even if it has a small chance of working I would like to give it a go and would like an expert opinion.

Reasearch the words in the terminal output, especially "servo". It will help you understand better what the problem is related to, as oppose to trying something just to try.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

I understand that and agree with what you are saying.

So let me ask a question on that front to help to understand if it's indeed a servo problem on the physical hardware vs. an issue with the driver circuitry on the controller board. If I was to isolate the hard disk using a card stock or completely remove the controller from the hard disk and look at the terminal output, should be expecting different outputs in each of these cases ?

I understand that it would depend on the specific problem the hard disk has, but just wondering what would an expected output from the deep level of experience and understanding of the contributors to this forum.

Your drive is a 2TB. This one here is a 1TB, but basically the same thing, just lower capacity.
viewtopic.php?t=22217&start=

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

Ok thanks.. Exactly the same symptoms I am seeing.

Opened the hard drive, here's the link to the video. Who can tell?
http://www.youtube.com/watch?v=wDH6QQE4 ... e=youtu.be

Hi Alex - Yep.. that's exactly what I am seeing on my hard drive as well, although I open mine up in a clean room I have kinda given up. Would love to know if there a way to just get some use out of this drive even if all the data is gone.

If data is important, what exactly do you think you will achieve by opening it?

Then you can make sure it is dead and don't have to wonder anymore Curiosity is a curse for me too, so don't worry, you are not alone

Looks like dead heads (maybe accompanied with MD) on both drives
Can be PCB but very unlikely

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

sooo, I'm having exactly the same error... Wanna smack the drive with a hammer

Strange thing is that I also had it in the nas server: QNAT, the disk broke maybe 3 days ago...

http://youtu.be/xx6GNejwjn4