Samsung ST1000LM024 hangs with continuous terminal output

[osity]

I have a couple drives in the lab both doing this continuously in the terminal when I try to read using DE.
During this output the drive stays BSY. It will come ready after a power cycle and read a few sectors but then just goes BSY again.
Below is the continuous terminal output while the drive is in BSY state.
I know that a heads 1,2 are bad out of 0,1,2,3. Perhaps its getting stuck in BSY when reading a with a bad head.
Both get full id and come ready easily.
Any suggestions other than the obvious swap?



[GL][TP:001B49B9D0][E:1140]
[GL][ADD:01B49B9D0][C:0005][E:1140]
[GL][RS:05 01B49B9D0 9097A000]
.
[GL][TP:001B49B9D0][E:1140]
[GL][ADD:01B49B9D0][C:0005][E:1140]
[GL][RS:05 01B49B9D0 9097A000]
.
[GL][TP:001B49B9D0][E:1140]
[GL][ADD:01B49B9D0][C:0005][E:1140]
[GL][RS:05 01B49B9D0 9097A000]
.
[GL][TP:001B49B9D0][E:1140]
[GL][ADD:01B49B9D0][C:0005][E:1140]
[GL][RS:05 01B49B9D0 9097A000]

[Filipp_TS]

Hello,

Try to build a Heads map in Data Extractor and read a data via HEads 2 and 3 firstly.
Then need to read a data from Heads 0 and 1 and decide: read as is with repowering or set the donor heads.

[osity]

Yes, Heads 2,3 have all been imaged fully.
It would take too long to finish by repowering the drive so I will have to consider donor.

Thanks!

[osity]

Filipp_TS:

The heads seem to read. It just seems that the drive gets stuck. Here is a video.

https://youtu.be/jACXahq2xtY

Does this still look like a head issue? This is using donor heads.

[DataMedics]

Have you tried just playing with your read settings to see if you can optimize it? For example you might try switching to PIO with read block size of 1 or 2 and a really low timeout like 100 or 150ms. From the pattern of the red boxes I'd say there is some media damage (probably also weak heads). You also might play around with disabling things like read look ahead. It won't be a fast read no matter what unless you swap heads, but you may be able to get it fast enough to finish over a weekend.

[osity]

I've tried all that. From Max timeouts to minimum with all modes and read ahead options. . If it doesn't lock up it will actually read up to 90 MB/s. I've got about 30,000 sectors left. These are the new heads

I'm starting to think media damage also.
But what's odd is it was doing this five days ago as well. And then I just got lucky and it started reading extremely fast then the problem came back. When it does read fast it just wipes out those red sectors instantly.

The client only wants one folder but the folder that he wants is missing one sector in the MFT and it's the only folder that won't expand in DE, so I'm trying to image used sectors by bitmap, then I'll do a logical scan.

[Amarbir[CDR-Labs]]

Source of the post I've tried all that. From Max timeouts to minimum with all modes and read ahead options. . If it doesn't lock up it will actually read up to 90 MB/s. I've got about 30,000 sectors left. These are the new heads

I'm starting to think media damage also.
But what's odd is it was doing this five days ago as well. And then I just got lucky and it started reading extremely fast then the problem came back. When it does read fast it just wipes out those red sectors instantly.

The client only wants one folder but the folder that he wants is missing one sector in the MFT and it's the only folder that won't expand in DE, so I'm trying to image used sectors by bitmap, then I'll do a logical scan.

Well,
You are doing good carry on i am sure you will nail it in a few hours or days

[gameboybin]

Wow. I am having same exact issue. The drive hangs. And goes BSY light. I need to repower the drive. And the drive goes reading fast again