ST3500820AS - 7200.11 - BSY Problem

[zebong]

Hi,

Have this disk that the problem was BSY.

Afther resolve that with the udma, i could start copy sectors green.

But now i start to have this error in terminal

Code:

RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame
RequestResumeSaveSmartFrame

Anyone know what is this mean ?


Thanks
ZeBong

[Doomer]

zebong, that's normal information
100% working drive would have the same strings

[guru]

I only see that after spin up (maybe a soft/hard reset creates this output ?)... . Doomer could sure say what it means. However, he doesn't have access to everything ;o)

[Russwinters]

I can confirm there are 7200.11 drives that stay always BSY but report this instead of LED error.

Performing the same fix as for the LED error resolved this as well.


Regards,

[Doomer]

I can confirm there are 7200.11 drives that stay always BSY but report this instead of LED error.

I can confirm that this is BS
That message is not an error it's information message. When drive showing such message that means drive read and initialized all needed SA modules. And if your drive stays BSY after that message that would probably mean you computer doesn't work properly

[Russwinters]

Doomer, I did not say that this was an error message. As I have seen this message on working drives, but I had a 7200.11 w/ lacie firmware that was 0LBA always busy, but instead of giving LED: error it was just repeatedly saying this.

So I treated it just like a LED:error and it was repaired.

I just meant to say that it is worth looking into that this MAY in some select cases possibly be seen when the error should really be LED

I am using Atola Insight w/ provided RS232 for terminal access and have repaired many 7200.11 with it successfully so I don't believe it to be faulty.

I can not explain why the drive was giving this output instead of LED: error, that would be something I would expect you to be able to explain more then me =)

Regards,

[zebong]

I remenber this case, i have to use the ACE "BSY PROBLEM LED" repair in this drive 3 times, when i was copy the data.

[Doomer]

As I have seen this message on working drives, but I had a 7200.11 w/ lacie firmware that was 0LBA always busy

I need some clarification on this one
You are saying that the drive has LBA0 capacity (that means you read drive's ID)
But you also saying that the drive is in BSY (always)
It would be intersting to know how your read drive's ID if the drive didn't come ready and stayed busy all the time?

[Russwinters]

I apoligize for the confusion;

It had BOTH issues, but of course you have to resolve Always BSY issue first, and then resolve 0LBA (if present)

This drive had both issues, but instead of usual LED: output, was giving me this output in terminal. The reason that made me believe it was the same was that with LED: issue it just keeps posting the error in intervals. This behaviour was the same in this drive, only different output which prompted me to believe it was the same (or close to the same) issue.

have only seen this once, in this case. It was from a LaCie Big disk with 2 500GB 7200.11 drives, only the master had the issue.

Regards,

[Doomer]

How did you fix it?

PS: there is no Master or Slave on SATA drives. Are you making this up?

[prodata]

RequestResumeSaveSmartFrame

Request SmartFrame
Resume SmartFrame
Save SmartFrame

it is normal..
simple

[guru]

He said he had two drives inside Lacie Big Disk.. So I guess drive 1 (Master AKA First drive) Not Master as in Drive select

How did you fix it?

PS: there is no Master or Slave on SATA drives. Are you making this up?

[Russwinters]

Indeed I meant Master as in Disk 1 (or 0, if you want to be proper) in the array had this issue.

Why would I make this up? What do I gain?

[guru]

you gain a free UDMA with chocolate bar

[Russwinters]

Awesome! Depending on the chocolate.

American chocolate isn't worth eating; I only get the imported goods.

[StuKeR]

I'm interested to. I've got same issue but with seagate 7200.12 CC35....

[N.C.]

.12 is another story...
Don't try to repair it like .11
You will kill the drive instead.

Janos

[xsoliman]

I was going to contribute to this discussion
as have a Maxtor DiamondMax 22 STM3500320AS which is a 7200.12 type of drive with a NRG list
with some sort of busy / busy reallocating issue
and occasionally giving "RequestResumeSaveSmartFrame"

But others more knowledge than me say RequestResumeSaveSmartFrame is 'normal' or not to worry about

It would occasional come ready at the sata interface and could copy some raw sectors off
but then would go busy
No errors in terminal eg no reallocating type errors that you sometime see

Now full stuck busy

can be a bit slow to break in at terminal

Can read sectors from terminal ok

V40 NRG List empty

V4 has lots of reallocated sectors in a certain range
and some still pending

Didn't try disabling congen fully to see if that allowed it to come ready

Unfortunately I got carried away and did some m0, commands
including some that overwrote all data sectors with 77's

Which was a mistake as would have liked to get the data back

Sectors readable from terminal (but contain 77's)
V4 has lots of reallocated sectors in a certain range
and some still pending( maybe)
V80 empty ?

Still busy at sata interface
So not (yet) been able to refurbish this one
but will investigate further as part of my other 7200.12 experiments

Update - its giving occasional clicks now, like background reallocation
and still stuck Busy

[xsoliman]

addition to the above
V40 still empty

strange that V4 has lots of entries but V80 is empty
looks like it isn't reallocating properly