Rosewood strange sector

[saltwater]

Hi there!

I had multiple Seagate Rosewood drives, with this kind of problem, and i don't have any idea what could cause this.

So the drives has good working heads, but always with some (or many) slow sectors, with the same pattern from every single drive. (picture attached)

While reading these slow sectors, there are error messages in terminal:

Starting LBA of RW Request=00024ADF8F Length=FFFFFFFF
ProcessRWError -Read- at LBA 00024ADF8F Sense Code=43110081ProcessRC: 00000001,00000000[Host]ReadContinuous: 024ADE53,00000197UnrecovSectorCount:0197,0196,0197NumUDEs: 00000197,00000000,00000196Passed(Host): 00000080,00000145Out: Adjust to DiscEndLba:
PrgFSkipLBA: 024ADF8F,024ADF8F
Starting LBA of RW Request=00024ADF90 Length=FFFFFFFF
ProcessRWError -Read- at LBA 00024ADF90 Sense Code=43110081ProcessRC: 00000001,00000000[Host]ReadContinuous: 024ADE53,00000197UnrecovSectorCount:0197,0196,0197NumUDEs: 00000197,00000000,00000196Passed(Host): 00000080,00000145Out: Adjust to DiscEndLba:
PrgFSkipLBA: 024ADF90,024ADF90
Starting LBA of RW Request=00024ADF91 Length=FFFFFFFF
ProcessRWError -Read- at LBA 00024ADF91 Sense Code=43110081ProcessRC: 00000001,00000000[Host]ReadContinuous: 024ADE53,00000197UnrecovSectorCount:0197,0196,0197NumUDEs: 00000197,00000000,00000196Passed(Host): 00000080,00000145Out: Adjust to DiscEndLba:
PrgFSkipLBA: 024ADF91,024ADF91
Starting LBA of RW Request=00024ADF92 Length=FFFFFFFF
ProcessRWError -Read- at LBA 00024ADF93 Sense Code=43110081ProcessRC: 00000001,00000000[Host]ReadContinuous: 024ADE53,00000197UnrecovSectorCount:0197,0196,0197NumUDEs: 00000197,00000000,00000196Passed(Host): 00000080,00000145Out: Adjust to DiscEndLba:
PrgFSkipLBA: 024ADF93,024ADFB2

These drives always had some problems with MC, maybe this can help.

Please light me up!

Thank you!

[lcoughey]

I posted about this here

https://www.recoveryforce.com/forums/vi ... f=12&t=595

[pepe]

This is a generated pattern that the drive returns uppon uncorrectable errors under certain circumstances.

pepe

[saltwater]

Okay, but what cause these read errors? Corrupt MC, or translator, or adaptives, or geometrics or or......?

[colanco]

Rosewood.......

The problem is not so much related to heads/sectors as to the degradation of the SA (the origin of all the problems of these units).... In my humble opinion this could have been solved (SEAGATE) by implementing a RAM according to the firmware requirements and not depending on continuous and repeated SA readings....

I am more concerned that this same problem is being experienced by Toshiba SLIM drives........

[colanco]

Okay, but what cause these read errors? Corrupt MC, or translator,

Both of them. If you could somehow get a good copy of those modules (2nd translator/MC) loaded into RAM it is possible (I don't know) that these "garbage" sectors would not appear in the copy...

I don't know if PC3K in the new update has something in this sense, I haven't installed it yet, but from what I've seen it only mentions it in the WD module that has infinitely less problems in this sense than SEAGATE.

[lcoughey]

I've had several cases where a head changes fixes it. It depends on whether the error is localized or virtually every sector read by the head.

[colanco]

I've had several cases where a head changes fixes it. It depends on whether the error is localized or virtually every sector read by the head.

of course... better heads .... better reading of SA, although if you follow this line, you may need many donors, I do not think it is an acceptable solution.

One question.... that I don't know the real answer to (I have my assumptions), how does rosewood manage the defective sectors in MC?

[colanco]

how does rosewood manage the defective sectors in MC?

I am referring to physical MC.

There are many questions that I do not have answers to, perhaps some members of this forum who say they know these units well, have them, I do not. As the other "mortals" I try to recover the customer data without doing processes that could compromise their data, if the thing gets complicated or I can't understand what happens, I stamp and return to the customer....

Some of those questions that I don't have accurate answers, I have my "theories" but only that......

Where is the physical disk space for the cache?

Does it have the SPT of SA or UA?

Does SMR apply to this zone?

If a damaged/slow sector appears in this zone how is it handled?

Is this zone covered by the primary translator?

.... etc.....etc....etc....

[pepe]

Where is the physical disk space for the cache?

Does it have the SPT of SA or UA?

Does SMR apply to this zone?

If a damaged/slow sector appears in this zone how is it handled?

Is this zone covered by the primary translator?

all these can be discovered relatively easily. Just use the thing in your skull.

pepe

[colanco]

all these can be discovered relatively easily. Just use the thing in your skull.pepe

I already use it, to the extent of its possibilities, and as I said I have my answers and which help me to be able to correctly diagnose many of the cases (and in their case solve), but not all of them. So I think I may be wrong about something or I have partial answers that do not solve all the problems.

[colanco]

This is a generated pattern that the drive returns uppon uncorrectable errors under certain circumstances.pepe

In my humble opinion this would not be exactly so....

[saltwater]

Hello!
HSA change solved the problem.