Page 1 of 1

CE log errcode

Posted: 30.10.09, 11:08
by ft1bh
Hi fellow PC3k users,

I just had a case with an ST3320820AS 7200.10 with a bad bearing and a lot of spots on the surfaces from a drop on the ground.
I managed it to read quite fast (in the good areas) until this morning it read very slowly (i.e a maybe 10 sectors per second)
My UDMA machine showed a CE Log error.
In this forum I only found a way around it with DataExtractor - which I don't have unfortunately. So I googled a bit and found that you can fix it with
in T mode with <CTRL-R> to load the cert code followed by a T4E to fix the CE Log error or the "pending bug".
After a few seconds the test result came back ok and I repowered the drive.
Now it's fast again. :D

I thought I should share it here because I could not find it here yet.

Boe

Re: CE log errcode

Posted: 30.10.09, 13:35
by dobrevjetser
Interesting. Thanks for sharing.

dobre

Re: CE log errcode

Posted: 06.11.09, 03:51
by steven
nice to know... THANKS A lot

Re: CE log errcode

Posted: 09.11.09, 14:34
by AJ2008
This is usually not recommended though, because if rewriting of CERt code fails because of error or bad sector, it can make the HDD much worse.

Re: CE log errcode

Posted: 01.12.09, 16:32
by patroclo
It worked for me too!!!

Re: CE log errcode

Posted: 02.12.09, 09:21
by AJ2008
This is good to know, but I always try to secure at least the more important data for customer first. If there is problem writing to surface when T4E is performed, this will completely damage CERT tables and recovery will be very difficult for you and any other DR firm that try and then we have unhappy customer who cannot get back his data.

Re: CE log errcode

Posted: 02.12.09, 11:32
by patroclo
Yes I know there coul be problems,

but I can't find an alternative method so instead of not getting the data back, i tried.

Do you know a different way to solve this issue?

It happens quite often to have seagate drives with this problem.

Re: CE log errcode

Posted: 02.12.09, 11:43
by AJ2008
You can get access to data via app modification in RAM. Is not permanent repair, but repair is made in RAM and data becomes accessible. I am sure there is information on this in for forum here, but if not you can ask Igor or Roustam for help.

you need modify APP code in RAM by Utility Actions option.

Re: CE log errcode

Posted: 02.12.09, 12:22
by patroclo
Thank you,

i will search better in the forum.

Greetings

Re: CE log errcode

Posted: 02.12.09, 19:03
by ft1bh
As I said I do not have Data Extractor but I *think* DE is doing exactly what AJ2008 is telling us.
Can anybody confirm this?

Re: CE log errcode

Posted: 03.12.09, 09:30
by AJ2008
ft1bh wrote:As I said I do not have Data Extractor but I *think* DE is doing exactly what AJ2008 is telling us.
Can anybody confirm this?


Personally I think owning Data Extractor is just as essential as PC3000. Maybe it is a good idea to invest in one. :)

Re: CE log errcode

Posted: 11.12.09, 14:47
by ft1bh
I'll forward that to my employer ;-)