I'm leaning towards not returning it... HD Sentinel says it is 100% fine though I realize it cannot predict the future and that noise might be slowly wearing it down. It's only going to be used for Fraps recording so it won't be the end of the world if it dies and it is making the noise only on rare occasions now (I don't know if that has anything to do with moving it to the intel Sata 6 port or if its just coincidental and it just makes more noise on the first day of activity Edit: LOL it just did it 4 times in a few minutes just now, weird how random it is!). I'll wait to see what happens with Seagate's investigation into it.
Chaos I agree with your comment, its the uncertainty of not knowing whether or not this is actually a fault that is most annoying, it would have been simpler if it was just DAO and I could have immediately returned it. Xenon I see where you're coming from but lets not put him off posting any updates in this thread, he is aware this is a real issue now and he's got them looking into it seriously (I hope) so all we can do now is wait.
Thanks Cant, I appreciate this drive is much cheaper (and possibly better performing) than the rest but its still quite an investment so I hope Seagate resolve the matter asap. Thanks for your efforts 
@ Xenon, if I'm a cheeleader you should read some more of my posts, I don't know of any cheerleader that recommends ppl send the drive back for a refund if they are still in the qualifying period, nor a cheerleader who openly has stated he feels a certain product line isn't that good (not this one btw) and, the company allows this, I've never been told not to be honest about things, not once,
You have every right to not be happy, but starting that old deflame against the company because it hasn't established whether the drive is at fault or the user yet, they can only issue an update once the fault has been replicated in the lab and some new parameters written for it, I've seen one that is suffering from this that it's possible the dock it's in is helping cause it, infact as I use a dock myself and at times have slotted the 3TB into it it may well be that was the times when mine made the noise, can't say for sure though,
All the other users seem to be happy to hope for a fix and willing to wait for one without the dissent that's now coming from you, if you can get your money back I suggest you do so, that way nobody owes you anything do they, but should you be willing to wait for a fix then you are quite welcome and I will try to assist you and others if I can by suggesting you check the silly things first, if you look in my 3TB sticky set up thread you will see I had a sata lead come loose myself and this caused me problems, but I hadn't checked it and assumed when I fitted things they were right first time, sadly in a case with no cable management one had come loose and until I did a full check I could've gone route one and blamed the HDD,
Anyway, this is being looked into but you will have to be patient for any fixes as there is no point issuing one that next week ppl are back saying there is now another problem,
Rah Rah Kid.
I'll chirp in again ,
might be useful for Mac people....
hdapm OSX LaunchDeamon gets this drive in the line...
No more chirps, Load Cycle Count attribute steady.... Dead silent.
And conveniently gets run every startup or login.
Before hdapm, LCC was climbing almost by a minute.. Over 3K in 10 days.... Compare that to 3K for an old Hitachi in 3 years.
Drive is actually phenomenal, before hdapm and after... (2TB Barracuda, that is)
best,
D
Cantbecanit wrote:@ Xenon, if I'm a cheeleader you should read some more of my posts, I don't know of any cheerleader that recommends ppl send the drive back for a refund if they are still in the qualifying period, nor a cheerleader who openly has stated he feels a certain product line isn't that good (not this one btw) and, the company allows this, I've never been told not to be honest about things, not once,
You have every right to not be happy, but starting that old deflame against the company because it hasn't established whether the drive is at fault or the user yet, they can only issue an update once the fault has been replicated in the lab and some new parameters written for it, I've seen one that is suffering from this that it's possible the dock it's in is helping cause it, infact as I use a dock myself and at times have slotted the 3TB into it it may well be that was the times when mine made the noise, can't say for sure though,
All the other users seem to be happy to hope for a fix and willing to wait for one without the dissent that's now coming from you, if you can get your money back I suggest you do so, that way nobody owes you anything do they, but should you be willing to wait for a fix then you are quite welcome and I will try to assist you and others if I can by suggesting you check the silly things first, if you look in my 3TB sticky set up thread you will see I had a sata lead come loose myself and this caused me problems, but I hadn't checked it and assumed when I fitted things they were right first time, sadly in a case with no cable management one had come loose and until I did a full check I could've gone route one and blamed the HDD,
Anyway, this is being looked into but you will have to be patient for any fixes as there is no point issuing one that next week ppl are back saying there is now another problem,
Rah Rah Kid.
I agree that you do seem like a nice person and want to be helpful and you have been helpful passing this info along to the right people. However, I feel like you have been unhelpful in some ways such as how you consistently try to shift blame onto everything EXCEPT the drive itself. It's almost as if you're so caught up with the Seagate name that you can't allow yourself to think that there couldn't possibly be something wrong with the drive itself. Another thing is that it seems like you don't really read peoples posts before you reply as a lot of the suggestions that you make have already been discussed and proven false. Some examples are...
- You tried to say that it might be a Windows issue yet there are users who have posted that they are using MAC.
- You tired to say that it might be a case issue yet there are enough people posting here and clearly we don't all have the same case.
- You tried saying that it might be caused by the drive being in a dock yet I'm not using a dock and neither are several other people in this thread as well.
You suggested all of these things without actually taking into account all the facts that are all laid out in this thread. Like I said though it seems like you simply pick and choose what you want to read and then you make comments that don't really flow with the conversation. Another good example is right there in your last post, you suggested that I return my drives and get my money back yet in my POST #47 I already explained my situation on that topic. So clearly this proves that you do not read everything before replying.
As for saying that I am trying to defame Seagate, once again you clearly do not read my posts as I have stated NUMEROUS TIMES that I am not here to bash however I am a little upset off by the whole situation so yeah I probably take cheap shots here and there. But when it comes down to it I am just here for answers and resolutions. Lest we forget who started this thread! Furthermore, I don't think that Seagate needs my help when it comes to "defaming" as judging from the threads that I have been reading over the course of the last week, with all the silly issues that people have with their Seagate drives and their infamous 7200.11 issue. Clearly Seagate does a good enough job creating a bad name for themselves all on their own without help from me. And like I said numerous times as well, in my opinion there is no excuse for these kinda silly issues especially from a company who has been making hard drives since 1978! It's not like hard drives have changed that much in the last 34 years to justify stupid issues like this.
