Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
August 16th, 2010, 13:23
Heya all. Got my hands on the above mentioned drive. Calibration sounds ok, comes ready. Full model number and all yet LBA 0. Terminal also gives a LED issue but the code is different from bricked SD15 type drives. Timing out on the terminal from time to time. The PC3k suggested LBA fix didnt work ( i was expecting that TBH since its not made for that CC1H FW i imagine )
Anyone got any info on this particular FW ? Is it prone to do that ? Looks like some sort of a translator issue... Due to media damage ? Heads ? Or like SD15 CC1H is not to be trusted ?
Thx
Alex.
August 16th, 2010, 14:50
Well, considering that the drive was not clients , i decided to work under assumption that the issue is pure logics. Cleared Smart. Terminal gave me an error. Soft reset. Rebuilt the translator. Terminal showed the command given , timed out , drive timed out , stuck on BUSY. Recycled power , drive came ready with full LBA and data intact. Funny little CC1H...
August 17th, 2010, 9:07
Is this one of the data recovery secrets i hit here ? Or noone had a CC1H with LBA 0 problem ?
August 20th, 2010, 9:23
lonely.... iam so lonelyyy... =(
August 20th, 2010, 9:25
So ronery
August 20th, 2010, 9:51
CCxx are not nice, and most I recieve have some sort of failure. The SA repair on these is very similar, but in cases where disk remains BSY is slightly more complicated than usual fix as SMART usually cannot be cleared (as is with most 7200.12 series)
I also see a lot of CCxx cases with physical issues.
CCxx with 0 LBA where terminal can be reached is not so difficult and not particularly a secret.
August 20th, 2010, 9:58
Thx hddguy. From ur experience the CC1H LBA 0 error is a random occurence? Or is it a time bomb like SD15 ?
Powered by phpBB © phpBB Group.