Hitachi sector access Interruption

[shahij]

A Hitachi HDD shows UNC to full drive after few sectors.

Do you have solution regarding this issue?

HDP72502GLA380

[dmarques]

Hi,

Have you checked if PList is fine?

[shahij]

Hi,

Have you checked if PList is fine?

The drive had bad sectors initially.

Plist read was fine, Glist read was fine, to make things stable in imaging I transferred Glist records to Plist, after this, the problem raised. Still the Plist is fine.

Theoretically, this HDD has backup P-list module in SA-C, I am thinking for writing back the SA-C module to SA-A. Then the previous P-list records will be back, this might make the drive to last working state!

Any thought? Or is my idea practically applicable or does it have downgrade?

[dmarques]

I had that problem once and was related to Plist, that had some sectors outside of it's lba. Check that also.

[shahij]

I had that problem once and was related to Plist, that had some sectors outside of it's lba. Check that also.

RSVD. PSHT(Plist), RDMT(Glist) is corrupt on SA-C, but in SA-A - these 3 modules are fine.
So, I can't write SA-C to SA-A.

2ndly, The LBA is right.

In this situation, how to fix the P-list in SA-C? as well as G-list?

[shahij]

Update: I can see there are 3 records outside it's LBA under P-LIST.

Original LBA is - 488397168

3 Records that are outside -
1. 488397228
2. 488397229
3. 488397522

Total records into Plist - 547

In this situation, how to release these specific 3 records?

[dmarques]

Now you starting messing with it

[shahij]

Now you starting messing with it

All were thought, did nothing still yet. I was just updating the analysis.

Well, when the LBA is outside, is there any way to make the case fixable?

There is another thought in my sense - Release the P-list then adding back manually the P-list again.
But will it be applicable? or will be problematic for the case?

[BlackST]

The drive had bad sectors initially.
Plist read was fine, Glist read was fine, to make things stable in imaging I transferred Glist records to Plist, after this, the problem raised. Still the Plist is fine.

Bad idea on Hitachi, the problem was probably elsewhere.

The drive had bad sectors initially.
Theoretically, this HDD has backup P-list module in SA-C

In a far far away theory. Did you check the content of SA-C vs SA-A ?

Then the previous P-list records will be back, this might make the drive to last working state!

See above

[shahij]

The drive had bad sectors initially.
Plist read was fine, Glist read was fine, to make things stable in imaging I transferred Glist records to Plist, after this, the problem raised. Still the Plist is fine.

Bad idea on Hitachi, the problem was probably elsewhere.

The drive had bad sectors initially.
Theoretically, this HDD has backup P-list module in SA-C

In a far far away theory. Did you check the content of SA-C vs SA-A ?

Then the previous P-list records will be back, this might make the drive to last working state!

See above

yes, I checked the content of SA-C vs SA-A, in SA-C the Plist, Glist was error. But in SA-A, both are fine.

Last things were in account to Clearing the P-List and adding back all defects back except 3 wrong LBA value. But it didn't work, after clearing plist, message appears SUCCESSFUL but the plist records remain.
Only last idea based on theory I see is VIRTUAL TRANSLATOR what is so far practically not possible for me now.

[BlackST]

Quote :

"yes, I checked the content of SA-C vs SA-A, in SA-C the Plist, Glist was error. But in SA-A, both are fine."

SA-C is for another purpose, in fact.

Honestly, to me the problem was elsewhere right from the start, but I feel it is a lost battle with SD tool.
P.S. on Hitachi / IBM it is always a bad idea to fiddle with lists on live data, unless you have COMPLETE ACCESS to SA with a tool THAT WORK and you are able to reverse ANY change .

[shahij]

Quote :

"yes, I checked the content of SA-C vs SA-A, in SA-C the Plist, Glist was error. But in SA-A, both are fine."

SA-C is for another purpose, in fact.

Honestly, to me the problem was elsewhere right from the start, but I feel it is a lost battle with SD tool.
P.S. on Hitachi / IBM it is always a bad idea to fiddle with lists on live data, unless you have COMPLETE ACCESS to SA with a tool THAT WORK and you are able to reverse ANY change .

Yea, SA-C is for another purpose.

The drive could be imaged without transferring the G-list to Plist. Only because of this operation the problem raised, I agree. If there would be a P-list editing feature on that SD tool or at least what I calculated would work might make the case fixed. I don't know if PC3K offers such features for editing P-list on Hitachi or creating a virtual translator. On the other hand, DFL is offering such a feature for Sector Interruption fix on Hitachi, according to my understanding, DFL is doing the same job behind the scene.

After all, I don't have other option except SD tool so far. Considering for DFL tool in near future.