Slow sectors

[areus]

Hy to all!

I have two simple question!
I repaired a bad Maxtor Calipso (6Y080L0) drive with rewrite some mods. The mods are from Salvationdata. Now it works fine, writes very fast. I have cleared the p-list, and after i regenerated them with Victoria. But the drive have some very slow sectors (not bad, just slover than 300ms, the read speed is just 4MB/s...) in the first 50.000.000 sector. Can i lock or remap this sectors, like the bads? Or can i add them to P-list?

I have an other 6Y080L0 drive. It has a serial flash on the PCB, but with wrong flash. The ROM is for a YAR51EW0 drive. How can i reflash the ROM, when i cant set it to safe mode? (the yar41vw0, and the yar51ew0 SAFE sets doesnt work...the drive spins up...). I soldered them out, and try to load the drive without it. The new firmware is NAR..... (ARDENT C8-C1 cpu ). I must get a new ROM chip from a bad PCB?

Thanks!

[pepe]

Hi Areus,

Nice to meet U!
I think it's not neccessay to clear Plist before erasing the drive. I don't use Victoria, but I suppose it cannot move defects to Plist, only to Glist which gets full easily.

For the ROM problem u can reprogram those chips with eprom programmers externally.

pepe

[areus]

Thank You, Pepe!
(and where are you in Hungary? Im in Miskolc.)

My problem was with the first drive, i cant find the bad mods. Something was wrong. So i got a whole mod pack (maybe is from a good donor drive, no Err mods..), and i tried to rewrite all. It seems good, reset->recalibrate, and wow it works! (the SN is now absolutley different, at the top of the drive is Y2DW9Q3E, but the drive is Y2039SAC.., but SMART,AAM,.. works good)
Dont ask me, what tool i have... just a simple program, and IDE port.

ROM: i belived, the SAFE sets are just a logical input for the PCB's CPU (like TTL-NAND, what have 1,0,-1 logical inputs). For a YAR41BW0 drive the SAFE set is in the lower jumper row the first and the second pin is [;;:.:]. For a YAR51EW0 drive is the upper row first, and the single in the lower row. ['::,:] But with this drive ... I tried every combination, and do nothing.

[Amarbir[CDR-Labs]]

Thank You, Pepe!
(and where are you in Hungary? Im in Miskolc.)

My problem was with the first drive, i cant find the bad mods. Something was wrong. So i got a whole mod pack (maybe is from a good donor drive, no Err mods..), and i tried to rewrite all. It seems good, reset->recalibrate, and wow it works! (the SN is now absolutley different, at the top of the drive is Y2DW9Q3E, but the drive is Y2039SAC.., but SMART,AAM,.. works good)
Dont ask me, what tool i have... just a simple program, and IDE port.

ROM: i belived, the SAFE sets are just a logical input for the PCB's CPU (like TTL-NAND, what have 1,0,-1 logical inputs). For a YAR41BW0 drive the SAFE set is in the lower jumper row the first and the second pin is [;;:.:]. For a YAR51EW0 drive is the upper row first, and the single in the lower row. ['::,:] But with this drive ... I tried every combination, and do nothing.

Hi ,
pepe sir is definately gonna ask you of that tool

[BlackST]

@areus...

Why not selfscan ? It will solve definitively the bads/slow

[areus]

OK! It works fine! Yesterday i had some free time, and a free (quiet) PSU... I never belived, selfscan needs a whole day..

I learn for mechanical engineer (i do my thesis from rapid prototyping). SO HDD repairing is just a hobby for me. Till now i repaired just 9 drives (only Maxtor, and 1 Samsung) with HRT 1.0 & 2.0 and with a home maded util .This noname prog was my friend's homework in a hungarian university, so it has many bugs, and very unstable. Very good tools, but it supports only old P-ATA, and some SATA drives (with a P ata-sata converter).

[BlackST]

Safe mode is always the same, regardless of code. SN changed because you rewrote fw from another disk. So my suggestion was the solution... Keep learning! Rgds.

[areus]

Dear BlackST!

Have you repaired Maxtor Grizzly drive? I have one bad drive, but i have no idea, how can i repair or just set to safe mode (7H500F0). The problem is: i have got this drive in this state, it spins up, but the BIOS recognize it as Grizzly. Firmware problem, ok. 3 months ago i had do something (i dont know what, i had just connect them to the PC...), the drive normaly booted up, but the firmware number was 6H500F0 . (somebody sad, there is no big structural differences between this two series...). So the drive worked for a half day good, i had some files open. Now the drive cant work, just in alias. I belive, the first owner had a firmware update (that was a big solution, when the MB was older than the drive....), what taked the drive to bad.

What can i do? Simply throow it into trash? I have got a loader for this drive, and i maded some copy from mods, ram and loader of workin donors.

rgds

[BlackST]

@areus

Not here, please PM me ! Thanks