How long does it take the selfscan of Mx740/QUANTUM Fireball AS 20 and 40 Gb? At last I have solved the puzzle and it started... Don't know when it stops. In Lct the led on the drive also flashes in 'code' showing the current step... COOL !!

I have tested on a Quantum AS20 and it last for about 2 hours.....Of course it was terminated with an error(and spin down, if I remember properly)...I run it 3 times after that and the result was the same....

Rgds

_________________
www.datasave.ro

I don't get "of course it terminated with an error" ... and 2 hours. Maybe wrong flow or drive with problems? Even a 4,3 GB LCT took more than 3 hrs...
Up today I have solved the issues and successfully selfscanned TM, LCT8,10,20 , SE . On these drives selfscan run smoothly and end with LED on the pcb quickly flashing with motor off. The selfscan status is 000000 = PASS = DEADBEEF (success )
On the AS / Maxtor MX740 (same platform different fw/structure) I have some 40GB and 20GB to experiment with, at last now I can make it start. Not bad

Let's see (and want to hear from you) if this behaviour is correct

After writing the CORRECT modules, power off then on. After about 1 minute, led flashes like : *--*---*--*---------*--*---*--* for about 1-2 min. then spin down . After 1 min. led turn on, wait, spin up, then selfscan starts with led flashing like above (* = blink, - = off). I can say the process is going on because sometimes I hear the drive performing some recalibration, HSA moving, some "beeping" from inside when probably doing servo recalibration / adaptives recalculation. The led doesn't change frequency or behaviour.
Just curious if the overall process takes more than 12 Hr. for a 40GB.

On one drive the process ended "abnormally" after some hours, with motor off and led slowly flashing. The selfscan process was not completed because the status was FAIL. In any case the major part of the process like adaptives recalculation was done, because the drive was not accessible, but the BLOCK ERASE commands worked, giving a perfect surface and no hiccups. Of course, errors had to be manually reallocated, but I'm half way. Maybe clearing the error lists and re-performing SS will complete.

Any opinion ?

Best regards.

Hi

As I have allready told you on another forum ,these drives suffer from bad selfscan modules...It is written even in acelab manuals...I only tested on a Quantum AS 20Gb so far because I don't have another one...But , when I will have the time maybe I'll search for more drives of this type and do some experiments..

Anyway, the start procedure is correct...the same was happend on this drive I tested...And I have cleared error lists and restart SS but it was the same....Maybe my drive was a very bad one....

Maybe other guru's on this forum have done more testing...

Rgds

Have A Happy New Year!!!

_________________
www.datasave.ro

BlackST If I'm not wrong those drives have terminal. Did you try to monitor selfscan process trough terminal?
Actually I never tried to monitor selfscan via terminal, but if I find drive working enough will invoke it to see...

_________________
DataRecovery.bg