Anyone offers fix for Seagate ST3750630AS BSY issue?

[Anon]

I am loving this forum, so I'll just continue asking stuff

This time it's about a 750GB Seagate that is spinning up but not seen/recognized. Firmware is HP24 and according to Seagate serial checker it's one of the affected drives. Unfortunately, the people at HP don't seem to provide data recovery.

I have seen the guides on how to DIY fix it but as I have never done it and don't want this particular drive to be the guinea pig, I wanted to ask if anyone here offers unbricking for a reasonable price.
I am located in Sweden so Europe-based would be ideal.

Alternatively, I can try the DIY fix but in that case I wanted to ask if there are any risks involved in it. I mean, it really seems simple enough but I haven't seen any warnings (just the usual "I dont take responsibility....), which is a warning in itself, because nothing can be so simple that doesn't involve risks.

Soo, if done in the wrong way (examples of this also appreciated), can it lead to data loss or the likes?

[Nick_CT]

I've heard lots of success stories when using the published DIY solution on 7200.11 drives with the BSY problem. There is most definitely a risk of bricking the drive if you type the wrong thing in the terminal. Do it right and you've got a good chance of it working if the symptoms match the solution.

Search the forum and just plain google and you'll find a wealth of info.

[dobrevjetser]

There is the member Bosse in Sweden.
He could easily do this.

Dobre

[pcimage]

There is the member Bosse in Sweden.
He could easily do this.

Dobre

Agree.

He is "mr_spokk" on here

[fzabkar]

I can try the DIY fix but in that case I wanted to ask if there are any risks involved in it.

Be aware that the terminal commands are case sensitive. Don't get this wrong.

[BlackST]

The risk is not only related to command case, it is that if there is 'another' problem where the outcome is the same symptom, it is easy to get in deep shit, where at lab it would be safe, like it or not.