Ares selfscan problems

Hello ,
I have a hdd its model no was 2f040l0 vam51jj0 the hdd was full of badsectors i checked the firmware everything was ok . So i cleared Glist edit the module 1f and selfscan group module to start selfscan i pluged the hdd to separate powersupply with LED to monitor after 5 days hdd LED still blinking i took it out from that powersupply and plug to pc3k i saw that the ROM code changed to VBM51JW0 .
My question is how do i change its ROM code to its normal position ?

Thanks in advance

one more thing the code for selfscan written in the manual is VBM51J80 but my hdd shows VBM51JW0 what does this code mean or is it the same thing .

Thanks in advance.

How did u...
edit the module 1f and selfscan group module....?

using MRT .

mr rameez

u still need more training for pc3000 well go to ask mr muslim .. he can tell u.. he learned this 2 years back from me..

well before u do selfscan u need to make backup your all modules then run selfscan..

now problem is u have corrupted firmware code from selfscan..

rewrite all modules and group in safe mode and set jumper in standard mode problem will be solved.. from fresh drive or your bakcup module ..

also u have mrt u can fix this problem as well ..
well if this not solve also have other options for this to solve this issue

ur problem will be solve from this code VBM51JW0
if u do wat i said..

edit modules not good way for fix this problem drive will be unstable..

re write all modules and group in safe mode drive will be ok..

i did backup modules before running a selfscan , thats the primary thing , and even a kid could think of rewriting all the modules and group modules . That even i know . I started this post so i could get the PN of the modules that causes this .
And about Mr Muslim , he doesn't even know how to edit a module with a hex editor and so do u .
I don't know about u , but Mr Muslim has never even seen a hex editor .

U both can learn from me pm me or u can add me on msn , i will surely help u with ur problem and also with ur english .

rameez wrote: I started this post so i could get the PN of the modules that causes this.

You are a step from this you want, just put your effort for looking, not for nibble.
IMHO I does not belive that someone will share such info

BTW there are at least 3 different themes(posts) with such problems you wrote in and got some answers.
And for last - the manual(PCI) I suppose you use - hold the answer :wink:

P.S. After I reread all till my post - the answer already have been given.

fixed the problem thanks for all your help .

One more thing i have seen three codes in these hdd while selfscan can someone tell me what these codes mean . The codes are as follow :
VBM51J80
VBM51JS0
VBM51JW0

Thanks .

Does maxtor store result codes with the firmware change? anyone have any idea?

Shortscurcuits wrote:Does maxtor store result codes with the firmware change? anyone have any idea?

What you mean?

Shortscurcuits wrote:Does maxtor store result codes with the firmware change? anyone have any idea?

Yes it does but changes the ROM code with respective result .
After experimenting with many drives i have found that

When "VBM51J80" appears it means selfscan has failed .
When "VBM51JS0" appears it means selfscan is in progress.
When "VBM51JW0" appears it means selfscan completed succesfully .

If anyone has any usefull info please share .

Thanks Rameez, I'll look at the bunch of Diamondmax9 I have as some show YAR41BWO and some show as YAR41BVO. Most have bad modules or bads in SA. So this probably means selfscan failed for these drives. I'll fix a couple and run selfscan and post results when I have time.

maybe .