3TB Seagate Barracuda Dead!! Desperate to recover data

[upmg]

Hi All,
I had this drive in a Synology NAS and since updating the NAS to DSM5 I've had issues (separate story).

The NAS reported around 2000 bad sectors upon a reboot and S.M.A.R.T test and a day later when backing up the drive it failed all together. NAS volume crashed but was still visible. I made the fatal mistake of shutting down the NAS and rebooting and after that the drive stopped getting recognised at all.

What I have done:

[*]Put the drive in to a Windows PC and it hangs the PC on bootup/bios a little but eventually loads and Windows doesn't even recognise the hardware is there.

[*]Put the drive in a SATA to USB enclosure and Windows/OS X wont recognise its existence.

[*]Loaded ubuntu and tried to read it there as the drive is formatted with a SHR (Synology Hybrid Raid) config in hope Windows/OS X couldnt see it because of its formatting but alas NO.

It all points to a hardware fault but its sounds smooth, it spins up and there are no loud noises.

Could anyone please give me some options there is data on it I need

Drive Info:

Seagate Barracuda
MODEL: ST3000DM001
PN: 9YN166-500
FW: CC4B
WWN: 5000C50052CB095D
Site: WU

Not sure if I need to provide anymore info.

But any options or help would be much appreciated please

[northwind]

it spins up and there are no loud noises.

Any quiet noises?
These drives can be very quiet when they click (but also noisy too).

Does it stay spinning up, or it spins down eventually?

If there is mechanical failure, then I'm afraid there is nothing you can do, these drives are bitches even for a pro.

But if drive spins up, stays up and makes no weird noises, then maybe there is a firmware issue. Terminal output could help.

[upmg]

There are a few quiet noises after the initial spool but its just sounds like normal initialisation to me, not that i'd know better as I don't listen to HDD's boot up much.

However I have the same Model, different firmware drive in my NAS and I've listen to both and there is not much in it difference.

It stays Spinning by the way.

Thank you for replying, I have been refreshing this page for hours in hope someone can help

[northwind]

You're welcome, and I hope you will get this sorted.

OK the fact that both drives sound the same, is a good thing.

You have two options:
1) Stop messing with drive with important data and consult a good professional who can safely diagnose and recover your data. I suggest Sean @pcimage or Mike @MJM. They can both do it for you.
2) Decide to risk and go DIY. In that case you need to get terminal output of the drive's boot up. Get the terminal output and post it here. This will help us figure out what's wrong with the drive.

A healthy Grenada (your drive) terminal output should be like this:

Code:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset


[upmg]

I think i'd like to go the DIY route as thankfully since posting the Original Post I have found 90% of the Required Files on a very old backup.

I was reading about the 7200.11 BSY fix and have learnt a lot reading and reading and reading these forums since posting and I am willing to learn but need a little more help please.

Firstly I dont have a cable or know fully how to get a Terminal output from the drive. I am willing to purchase a cable seems to be a few to choose from not sure which is best to get for my drive if you could further explain the process of grabbing a terminal output please.

Will a RS232 do? or these..

http://www.ebay.co.uk/itm/FT232BM-BL-Se ... 3f32fc64ef

http://www.hdd-parts.com/seonelithseb.html (This one specifies 7200.11 and mine is a 7200.14 is it not?

Thanks again

[pcimage]

Happy to take a look

[upmg]

My last post has been moderated guessing because I put eBay links in it. So expect a post to come through which is out of date.

pcimage you will be my first port of call if it comes to it but I am not exactly flush with cash at the moment so hoping I can try some DIY first your ears must of been burning to jump in so fast 24/7 working pal

My moderated post went something like this...

I think i'd like to go the DIY route as thankfully since posting the Original Post I have found 90% of the Required Files on a very old backup.

I was reading about the 7200.11 BSY fix and have learnt a lot reading and reading and reading these forums since posting and I am willing to learn but need a little more help please.

Firstly I dont have a cable or know fully how to get a Terminal output from the drive. I am willing to purchase a cable seems to be a few to choose from not sure which is best to get for my drive if you could further explain the process of grabbing a terminal output please.

Will a RS232 do? or these..

*links removed*

Thanks again

[northwind]

There are a lot of guides how to get a terminal output and most of the cables that are for sale, will work.

[scratchy]

If you do go the terminal route you have to consider that this may not be just a firmware issue. Safest thing is to copy and paste terminal output here where people that know what code means can advise of what to do.

It is also important not to follow the instruction for 7200.11 drives as there are other considerations to take into account.

[upmg]

Yeah

If you do go the terminal route you have to consider that this may not be just a firmware issue. Safest thing is to copy and paste terminal output here where people that know what code means can advise of what to do.

It is also important not to follow the instruction for 7200.11 drives as there are other considerations to take into account.

Yup. I understand the 7200.11 fix is not fit for purpose with my drive, the tutorials for it though gave me an insight to setting up a terminal window and what it entails for me to feel confident enough to explore or post the log here.

I just want to ensure I use the right cable. I am/was going to post this one.. Can someone give me the nod that im right in thinking this will work for me.

http://www.ebay.co.uk/itm/FT232BM-BL-Se ... 233915e011

[scratchy]

They are advertising as for 7200.11 .. most of us here use ones supplied with other hardware, so unless someone has used this actual one, we could'nt say for certain.
Most of these are pretty much the same and ones I have seen are based on the same chip. So for 10 quid, you should be ok - if it doesn't work you could probably claim through eBay as unfit for purpose.

Careful with the manual though, it does say for 7200.11 - terminal for 7200.12 and most other F3 based seagates use the same terminal parameters but commands may be different depending on what is in the current defects lists.

Also, remember that the original fault seems to me to be bad sectors, so fixing fw/translator probably wont help (much) ..

[upmg]

Hi All,
Finally managed to get a cable and boot it up in PuTTy.

This is what I get...

Code:

(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR:  MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 00B5E555
[RSRS] 0343
ProcessRWError -Read-   at LBA 000000000002A32D  Sense Code=40000087
ProcessRWError -Read-   at LBA 000000000002A39A  Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000002A39A!

Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Continuing after error
Reconstruction: Completed 1:
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001A
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE

Boot 0x40M
Spin Up
TCC-001B[0x000065B4][0x00006A20][0x00006E8C]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001B
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR:  MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 00B5E555
[RSRS] 0343
ProcessRWError -Read-   at LBA 000000000002A32D  Sense Code=40000087
ProcessRWError -Read-   at LBA 000000000002A39A  Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000002A39A!

Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Continuing after error
Reconstruction: Completed 1:
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001B
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE


Much appreciate any help please

i did cycle the power during this output btw to ensure I got all terminal messages as PuTTy wasnt connected straight away on first power up.

LED:00000047 FAddr:FFFFFFFE continues forever btw no option to enter commands.

ALSO
Not sure if I should but I haven't took the PCB off to grab this terminal output, I see some tutorials show to take the PCB off and insert some card or non conductive bag under neath.

Thank you

[upmg]

more logs:
In Case required or helps.

Code:

Boot 0x40M
Spin Up
TCC-0023[0x000065B4][0x00006A20][0x00006E8C]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-0023
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR:  MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 00B5E555
[RSRS] 0343
ProcessRWError -Read-   at LBA 000000000002A32D  Sense Code=40000087
ProcessRWError -Read-   at LBA 000000000002A39A  Sense Code=40000087[RA]!

ProcessRWError -Read-   at LBA 000000000002A39B  Sense Code=40000087
Starting LBA of RW Request=000000000002A32D  Length=00000747
ProcessRWError -Read-   at LBA 000000000002A39E  Sense Code=43110081[RA]!

ProcessRWError -Read-   at LBA 000000000002A39F  Sense Code=40000087
ProcessRWError -Read-   at LBA 000000000002A3A0  Sense Code=40000087[RA]!

Starting LBA of RW Request=000000000002A32D  Length=00000747
ProcessRWError -Read-   at LBA 000000000002A3A1  Sense Code=43110081[RA]!

Starting LBA of RW Request=000000000002A32D  Length=00000747
ProcessRWError -Read-   at LBA 000000000002A3A2  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 000000000002A3A2!

Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Continuing after error
Reconstruction: Completed 1:
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-0023
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE


[lcoughey]

pcimage you will be my first port of call if it comes to it but I am not exactly flush with cash at the moment so hoping I can try some DIY first your ears must of been burning to jump in so fast 24/7 working pal

As long as you are happy with paying more for your recovery, assuming you don't totally kill it first.

[upmg]

As long as you are happy with paying more for your recovery, assuming you don't totally kill it first.

All I have done is boot it up twice for a terminal output thus far, which I am guessing any repair agent would need to do anyway.

Can anyone please advise on the terminal output I managed to get please.

[DataPlanet]

Hi All,
I had this drive in a Synology NAS and since updating the NAS to DSM5 I've had issues (separate story).

The NAS reported around 2000 bad sectors upon a reboot and S.M.A.R.T test and a day later when backing up the drive it failed all together. NAS volume crashed but was still visible. I made the fatal mistake of shutting down the NAS and rebooting and after that the drive stopped getting recognised at all.

What I have done:

[*]Put the drive in to a Windows PC and it hangs the PC on bootup/bios a little but eventually loads and Windows doesn't even recognise the hardware is there.

[*]Put the drive in a SATA to USB enclosure and Windows/OS X wont recognise its existence.

[*]Loaded ubuntu and tried to read it there as the drive is formatted with a SHR (Synology Hybrid Raid) config in hope Windows/OS X couldnt see it because of its formatting but alas NO.

It all points to a hardware fault but its sounds smooth, it spins up and there are no loud noises.

Could anyone please give me some options there is data on it I need

Drive Info:

Seagate Barracuda
MODEL: ST3000DM001
PN: 9YN166-500
FW: CC4B
WWN: 5000C50052CB095D
Site: WU

Not sure if I need to provide anymore info.

But any options or help would be much appreciated please

Your hdd is on Sync hdd shows you busy status unless it complete the sync but with bad sector sync can not be completed because this is NAS storage do nothing with the terminal may be you lost your data forever.

Now get my help online skype: ontrack86

[lcoughey]

Your hdd is on Sync hdd shows you busy status unless it complete the sync but with bad sector sync can not be completed because this is NAS storage do nothing with the terminal may be you lost your data forever.

Now get my help online skype: ontrack86

What ???

I'm glad I'm not the only one confused by this.

[labtech]

Maybe #therealontrack is providing him remote service

[DataPlanet]

I think you people have 0 knowledge in RAID & NAS if you don't know what is Sync...

In electrical engineering terms, for digital logic and data transfer, a synchronous circuit requires a clock signal. Timekeeping technologies such as the GPS satellites and Network time protocol (NTP) provide real-time access to a close approximation to the UTC timescale, and are used for many terrestrial synchronization applications.

Client is using Synology NAS network drive and i don't think it is one must be 3 or more to share file to many users so synchronous must be completed to transfer data to the requested user on time.

However I have some successful cases with NAS storage so I can help him but it look like he can't give a good price.

$1000 and a original Flag of Great Britain to my address will work.

I only advice keep this drive alive or you lost your all data from other drives as well if this is Synology NAS with RAID.

[northwind]