ST1000DM003 with possible pending bug seems to keep coming back

[osity]

ST1000DM003

I've already disabled all items in sys93 except extended log and that solved the BSY issue for a few minutes as I was able to image some sectors and backup resources but now it's back to staying BSY again.
I noticed there are many sys93 files listed. Are they all the same?

I've discovered that the only way to read/write sys files at this point is to turn of/on the drive and i have a 1-2 second time frame to send a command.

Any ideas what I can try next to keep this going?

[AJ2008]

Did you try it over Terminal?

[osity]

Try what over terminal?

[DataMedics]

Reading/writing the system file. My guess would be that the disabled file 93 was never actually written back. If you have to read it within a few seconds of powering on, then you'll have to write it back the same way. Power cycle, then quickly write back. Or, do it all over terminal if that's stable.

[osity]

Yes, I'm able to write/read it by powering off/on. I've done it several times. I checked it and the items are still unchecked.... Should I try through terminal instead?

[DataMedics]

No, if it's showing as unchecked after you read it back then the changes must have taken. Are you sure the drive isn't just really unstable when you read sectors? Try reading in PIO mode with a really low timeout like 200ms or less. I've seen some that are just really unstable like that when they hit bad sectors. Also might want to try clearing S.M.A.R.T.

[osity]

That's a good idea. To set the PC3K to PIO is that just "use hardware retries?"

This allows me see data with sector edit but when I try with DE it stays BSY and gives me readienss loss errors...I'll try errasing smart as you suggested.

[DataMedics]

Yes.

[osity]

Genius suggestion for the PIO mode.
I still have to wait a while for the drive to become unbusy ( maybe 5 minutes each time) but then afterwards it is able to image. It seems that I have to keep waiting as it doesnt last.

[osity]

It only lasts for a bit. I'm unable to erase s.m.a.r.t . I get an Drive not ready error.

[DataMedics]

Try lowering the timeouts even more, to say 150 or 100ms, and drop the block size it's reading down to just one or two sectors as well. Usually if you do that you can keep it from getting stuck busy again. Also pay attention to what's making it go busy. Is it the soft reset, hard reset, etc. Sometimes you can figure out what's triggering it going busy, and just configure it to not do that.

[DataMedics]

Source of the post I'm unable to erase s.m.a.r.t . I get an Drive not ready error.

Did you try just doing it in terminal? E.G.

T>/1
1>N1

[osity]

It seems that lowering the timeouts to 100 with a lower block size (1-10) and everything unchecked now allows me to copy sectors for a decent period of time...The job is almost finished.. If it locks up, I just hard reset and wait about 5 minutes to for it to come ready.

I've used timeouts as low as 60 on the DDI but I didn't think the PC3K did well with low timeouts but I guess it depends on the situation.

Thanks for the great advice!!

[Amarbir[CDR-Labs]]

Source of the post ST1000DM003

I've already disabled all items in sys93 except extended log and that solved the BSY issue for a few minutes as I was able to image some sectors and backup resources but now it's back to staying BSY again.
I noticed there are many sys93 files listed. Are they all the same?

I've discovered that the only way to read/write sys files at this point is to turn of/on the drive and i have a 1-2 second time frame to send a command.

Any ideas what I can try next to keep this going?

Well,
i had this same issue with one recent case ,Even after disabling everything in 93 sys File

[AJ2008]

Write changes to SMP at copy0 then reload it, check if changes are saved. If not, write changes to copy1 and check if changes are kept.

Source of the post The job is almost finished.. If it locks up, I just hard reset and wait about 5 minutes to for it to come ready.

Great job