PC-3000 Forum

Hi all,

I have an ST1000LM035 giving me a bit of trouble.
I get Full ID, and have copied many sectors but it randomly stops prematurely with the drive coming DRD and DSC making me have to continue the imaging again for another short time.
The drive also becomes BSY for a while outputting lots of terminal messages.

i.e
"Starting LBA of RW request=002A51275 Length= 00000BB0
ProcessRWerror -Read- at LBA 002A5194F Sense Code=43110081Out: [PRA]!
[ScrubRemove]!
[ScrubRemove]!
[ScrubRemove]!
[ScrubRemove]!


These errors repeat for about a minute with [ScrubRemove]! part repeating many times quickly, then the drive eventually comes ready and I can imagine a little bit more before it all happens again.

When I try to write the changes to 93 (copy 0) to remove unneeded flags I get: Wr SysF 3:93:0 (0/2000) err = 0x00000005
I've tried ATA direct and ATA indirect without any success.

I have attempted writing random changes to 181 as a head test but the changes were not saved there either.

In my case, would the drive's inability to modify 93 simply mean that the heads on this rosewood can read but they cannot write?
Is there an alternate way to attempt modifying 93 other than a head swap?

You can edit 93 in RAM.

Also I had several donors that were compatible for reading but not for writing.

Just need to try some more donors to find one that can write in your patient.

MasterT, Thanks for that. I have forgotten about the RAM option.

happy new year all!


I've tried to modify 93 in RAM on this drive but that doesn't work either. The 93 file just comes up blank in RAM.
When the drive is not pumping terminal output (looks like reallocation data) it does seem to read quick but the output is almost constant so i only get to read short burst of data.

Is it typical for this family to need a head swap because it can't write to 93 even though the head itself is capable of reading when it's not outputting terminal data?
I'm trying to avoid a head swap here as my customer won't pay for it but I don't think there is another option.

Surprisingly it started reading slightly more steadily today after setting it to a high read timeout and forgetting it....Maybe all the questionable sectors have been reallocated at this point?

ok...now after weeks! it's reading everything.... like a champ.... no idea why.

It finished the background work and now decided to serve you as a master. )