Reply
Byte
endeavor
Posts: 6
Registered: ‎01-23-2009
0

New Firmware bug causes HD head to engage/disengage clunking

[ Edited ]
There may be an undesired bug in this new firmware.
I've got a ST3750330AS drive and it flashed okay with its latest firmware MooseDT-SD1A-3D4D-16-32MB.ISO, and all seemed to work okay, then all the sudden I heard the drives head engage and disengage clunking back and forth a number of times. It disrupts everything I have running. 
What was done to this latest firmware that affected the heads tracking alignment? 
This head engage/disengage Never Ever did this before the firmware upgrade and I've had the drive for a year now.
This is very disconcerting and I don't feel safe with this new firmware, and I want to flash back to the same SD15 my
drive had on where it does not do this. Is Seagate aware of this problem and will fix it on a new firmware?
Where can we get the correct best working SD15 firmware in the meantime so that I can flash back?
Message Edited by endeavor on 01-27-2009 06:35 PM
Kilobyte
cowtub
Posts: 14
Registered: ‎01-23-2009
0

Re: New Firmware bug causes HD head to engage/disengage clunking

Could well be coincidence that your drive has discovered or has reallocated a block. Run a long offline test and check your SMART attributes before and after.
Byte
whatever09
Posts: 3
Registered: ‎01-26-2009

Re: New Firmware bug causes HD head to engage/disengage clunking

I did a successful update to my ST3500320AS to SD1A and after a day I heard weird noises on my HDD (clicking noises ), after that windows was beyond slow trying to access the files stored on that HDD and then this write delayed failure error message........

 

 

PLEASE !!!! If someone that can help (a moderator or someone that has the SD15 firmware or that knows where we can get it) is reading this.... I am literally begging you to help us cause apparently Seagate won't, or at least after they are cornered by the media,customers, oh yeah  and they got some free time then they might.....

 

And to SEAGATE, say something about this -ANYTHING- !!!! When the first problem occurred you where so slow and so stubborn to admit that there was a problem, it was until lthe blogs, customer complains, and the media pushed you to.... And then you are so false saying:  yes yes we are sorry, we shoulded acted faster... YOU ARE REPEATING THE SAME MISTAKE AGAIN.... I mean sorry is a very convenient word for you isn't it?,you might say that you are offering to pay... But what about the other people that lost their files in an attempt to get them because you choose to remain silent?.  For the people that lost 6 months of work or more "sorry" is just not enough...

 

And maybe you are repeating the same mistake again, But believe me, I won't, this is the last of your products that I buy (that's a shame they are really good products) and I am not the only one you know?..

Kilobyte
Woodee
Posts: 20
Registered: ‎01-23-2009

Re: New Firmware bug causes HD head to engage/disengage clunking

6 months? Try more than 2 years!
Byte
Laza
Posts: 4
Registered: ‎02-04-2009

Re: New Firmware bug causes HD head to engage/disengage clunking

Same problem here :smileysad:

 

I'm going crazy, I don't want a drive that will do this..before upgrading to SD1A it worked perfectly.

 

I will try to adjust settings with hdparm tomorrow, that's the last thing I can think of trying. The problem seems to be simply that the drive goes into power saving / standby mode every 5 minutes or so. 

Byte
Finalnight
Posts: 12
Registered: ‎11-17-2008
0

Re: New Firmware bug causes HD head to engage/disengage clunking

I have been having the same issue with my ST3640323AS after I upgraded it to SD1B.
Byte
KaLin
Posts: 5
Registered: ‎02-03-2009
0

Re: New Firmware bug causes HD head to engage/disengage clunking

Hello:

 

To consolidate the discussion regarding the Seagate Barracuda 7200.11 Firmware issues, please post all related messages in the new thread that we have begun for the purpose of centering a....  Please do not post firmware-related content in another thread.  We are closing this thread to redirect.

Thank you for your understanding!

 

-The Moderator Team