Hy for everyone!

I need some help for selfscan a calypso drive. It can start only from SA-C, and cant start from SA-A (i tried many loaders with nothing succes). I dont have a similar assembled drive (KMGA), so the hot swap is not possible. So for last chance i tryed to start selfscan, but the drive hang by step 1Ch - 3Ah (Ext Servo calibration) with big strange seek noise. My problem is: I cant edit the SS script mod (1F59). When i change this mod with a good edited one (i have only for 080L0, not for P0), the drive passes this 1Ch test without noise, or problems, but hangs on the next one (38h). So my question/request is: Have somebody got a good SAC 1F59 mod for 6Y080P0 (yar41bw0) drive, or a good edited one from a successfull SAC selfscan.

Thanks!

You are a little confused : SA-C and SA-A/B selfscan modules are different and intended for different purpose. According to the symptoms I think you have mixed up something. The parameters for each test step are important.If the SA has errors, you have to correct it and hide the defects BEFORE starting SS (the fact it starts only from SA-C most probably is caused by errors on SA, especially on mod. PN #18). You have to find the CORRECT loader with CORRECT rom, and maybe the suitable RAM, then check the SA / mods. Only after you have a "decent" SA, you can try SS.
Maybe you have also problems with ONE head, or the drive is already refurbished. These drives are pain in the ass. Alternative : start SS from SA-C to rebuild the SA, then normal SS. If you have such problems, expect drive do be downgraded to 60 or even 40 GB after selfscan ends.

Nothing good will come out of this drive.
Don't waste your time.

_________________
www.datarecoveryne.com

I think the same, and I wrote it, but... well, it's worth a try...

If he tried many loaders and it would not work SA must be really bad.

_________________
www.datarecoveryne.com

Probably not. I had 100% success in many case , the last resort was starting SS from ram, but I had already remapped the SA defects, otherwise SS can't do nothing for it. And the drive was fixed perfectly.

I'm not so much interested in recertifying Maxtors as in fixing the SA so that I can use them for smart hot swaps. I haven't figured out the arcane peculiarities of SS yet. I am under the impression that the next release of PC 3000 UDMA firmware will have some improvements in that area.

_________________
http://www.datasaversllc.com

Why rely on pc3000? SS is easy to understand, with a little workout you can discover the great world inside it, mostly without tools.

I would have to say that Maxtor SS is very nice :O)

Start SS from ALT area, it's easier and faster than fixing the system/code area

_________________
All went well until I plugged the drive in.

BTW, guru, can you PM me with MSN/IM contact ? If you are really deep into maxtor ss I have two things to ask...

Hy!

Thank you for the help. The original SA was totaly bad (every starts the drive attempted a head mask error).
It had got a ,,new" SAA from a similar donor drive, than an edited script. After this i had run a selfscan, and now everything is ok, and the drive works fine.

Now i had an other drive, a Calypso 120L0 with 3 heads. The problem is: i cant edit this 1f59 script, and i need a good script to start SS from SAC. The SAC is good (original), but i have only SAA edited scripts, not for SAC selfscan.
Can anybody help to me with an edited 1F59 mod from a similar drives SAC, what successfull had a SAC selfscan?

The parameters: 6Y120L0 032611
NMBD Y35HQJBE AAA

And an other question: What is the difference between M6FYA and M6FYA PCB??? The ROM (only masked, no ext.rom) is totaly match. But only one of these can load a 6Y160P0 drive.

Maxtor usually starts the SA from H3.
But some drive, with bad media on the H3's side in the SA, starts the SA from another head.
This is configured in the PCB.

Regards,
Janos

hi ,
You Uploaded The Entire SA-A From a Donor To Patient Or some Modules

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com

Let's put some order :

The selfscan scripts are written according to disk specification i.e. material mixing and other things, so editing or using different scripts lead generally to unsuccessful SS or unpredictable results. Use the drive's SS script.
Why the need for editing ? If the purpose is removing some "unnecessary" steps for increasing speed of the process, the idea is good, but generally there is a meaning on every step.
About SA-C selfscan, if it is unsuccessful, you could have a really bad surface, circular scratch or notch near/inside the SA, or some other corrupted module, or unstable reading/heads (common with highly used drives).
My suggestion , if applicable according to the tools you have : manually relocate the SA defects, use the normal selfscan and if the drive gets downgraded, live with it.

What do you want to know?

_________________
All went well until I plugged the drive in.

Wait, busy now... I'll pm you.

An example, why i try this ,,solution"....

I had a totaly bad drive (lot of checksum error in SAA, lot of bad-sectors/reallocations in G list, and the tranlator was unrepairable to.... the drive wont start only with loader)
The drive:6Y080L0 NMCA Y2DW9Q3E
It has got a new SAA and everything was good and happy (i mean, the drive could load without any loader, but the bads were still there).
The donor: 6Y080L0 NMCA Y2M58EGE
This drive was the first drive, what has got a new script before selfscan. (the script was from a self scanned 6Y080L2 drive)
After the ,,successfull" selfscan, the drive was only 60GB !!!!! (but i have got a new, fast, and error-free drive) So the drive is now : 6Y060L2 Y2M58EGE .....

Yes I love the fact that you can enable downsize option in script. Very clever to get maximum yield from process

_________________
All went well until I plugged the drive in.