Hi Guys,

I'm hoping that someone can help. I have the above drive that came to me in the usual "Busy" state. Applied the usual fix and the drive comes ready with 0 LBA. Normally fix this with partition regeneration command in terminail with no problems, but this one refuses to finish. It hangs for a long long time with no error. Tried the Fix capacity error command in seagate Doc but does the exactly the same (in excess of 7 mins). In Seagate Doc, it will eventually say it's completed, but when you restart, it's the same.

All modules can be read successfully without error as well as CP(ROM) and CP(RAM). The drive spins up healthily, no noises or knocks, and comes ready in about 3 seconds, but stuck with 0 LBA...

Can anyone help....please..

Drive details are:-
Mod:- ST3500620AS
f/w:- HP12 (which i'm beginning to think is the culprit)

Module 000C__64000 takes ages to read (in excess of 3 mins) but without error.

Thanks..

Steve..

_________________
East Anglian Data Recovery Services
http://www.eadr.co.uk

"If it's your only copy - then it's not a backup!"

Firmware HP12?
Is this a drive rebranded for Hewlett Packard or something?

F/W: HP12 it will take time you have to keep Trying again & again i had also same issue but it solved just keep trying it is just F/W issue.

seagate 7200.11 series are known for firmware issues... you need to update the firmware

Yes, but if the drive has already been hit by the firmware issue, it will need to be recovered first before the firmware can be upgraded, and the recovery is what is not working here. Please actually read posts before you reply to them.

that depends on the tools he has to do firmware update... please don't lecture about actually reading posts....

information is scarce about tools or methodes tried, on this topic

there are serial and usb programmers available for updating the firmware on this drives

best regards

I'm sure there are other ways to upgrade the firmware other than Seagate's software.

But will they work if the drive is in the BSY state?

To be honest I actually don't know.

Seagate's firmware update can be applied in the usual way to drives that report 0 LBAs. I've seen this done twice, once on Seagate's advice, to retail 7200.11 drives with SDxx firmware. However, the end result is that the drive still reports 0 LBAs, even when using the -w command line option (SMART Clear Logs) for SeaFlash.

See http://www.users.on.net/~fzabkar/sf_usage.txt

The drives were subsequently recovered using the standard DIY fix.

I don't know whether it would be safe to try a firmware upgrade on the subject drive, though.

_________________
A backup a day keeps DR away.

GALACTIC BULLSHIT. Multiple cause give same symptom, but reckless 'one fits all' solutions often make disasters (data loss etc.) . Then what ass to kick ?
Deep check everything before deciding what to do.

After all of the 10000000000000000+ threads about this topic here and on many other forums, people still don't even get the basics?

This is why we don't give out info. It doesn't matter how noob-friendly it is, or how easy the tutorial steps are, people still just don't get it. And then they screw things up because they don't know what they are doing.

_________________
You don't have to backup all of your files, just the ones you want to keep.

And when they screw up things, serves them right !

I think TouchClarity has PC3000 or SD as he mentioned reading the modules. I think his answer is actually solved in his question

_________________
If you can keep your head when all about you are losing theirs, you probably don't fully understand the situation. ... Mr Kipling

https://www.mjm.co.uk/

It was 'in general'.

I think the information should be given out freely, if people stuff their drives up, that's their problem.

My arse. When I need something for my job it's ALWAYS MY PROBLEM and I don't get stuff or info for free except between colleagues on mutual help basis. I can say it is the rule.
Moreover, it is not good to put data at risk - a lot of people wouldn't think twice to risk someone else data for few bucks if things go right. If not, 'it was something else' ...

Well I am glad that the information on how to fix this error was made available.

Sure I can build an RS232-TTL adapter and I know how to use it, but without someone posting the required commands needed to send to the HDD firmware... it would never have worked.

Are you saying I shouldn't have been told how to fix my friend's drive, that he should have had to pay someone loads of money (that he wouldn't have been able to justify?)

I don't think so, anyway.

What you find is a partial solution that doesn't work always and often make damage instead. Seems that a lot of people and what seem a lot of clones freshly made everyday are always in search of info for this. Oooooh... Sorry for their porn and warez , their ignorance and hungry, but at least for me I consider talking if and only if there's something to trade. Period.

Hi Guy's,

This problem has now been solved with some help from SD private forum pro's, if you have access there you can read the thread warts n all. Thanks to all here (as always) for your input...

Steve.

_________________
East Anglian Data Recovery Services
http://www.eadr.co.uk

"If it's your only copy - then it's not a backup!"