05-04-2009 06:31 PM
I have also clicking HDD. Now its not recognized in BIOS. Apparently it had the false firmware (manufacturing fault, you know...). Double problem - need to revive HDD so its recognized in BIOS, update firmware. And then copy all data to new HDD. And that clicking ask Seagate to replace.
Actually I sent the faulty HDD to Seagate, asked them to do recovery or update firmware. They are still discussing internally what to do. Of course they would like not to do anything, but I will not give in. Seagate promised to do free data recovery for firmware affected HDDs - so I expect to get my data back.
05-06-2009 03:25 AM - edited 05-17-2009 05:30 AM
Today marks two months plus two days of owning and using a Seagate 7200.11 1.5Tb harddisk.
Yesterday in the evening the disk started to make mechanical clicking everytime it was accessed and performance dropped to zero during these clicks. Some hours later while checking the seagate forums suddenly I noticed the disk disappeared from windows. So I turned the computer off and later right before going to bed I turned the computer on and the disk appeared but the mechanical clicks are still present.
This drive is among those that according to seagate isn't faulty and there are no firmware upgrades. The drive has worked fine during these two months.
Now I bought the drive cause I needed space and I don't have any other to backup the data it contains. I can still get a new one from the place of purchase and perhaps even change it for another brand, say WD.
But the problem is how do I transfer the data to the new drive? Do I really have to buy yet another drive I don't need?
I returned the drive and got the money back; which I then used to buy a WD of the same size.
Of some interest was that whether the hdd was horisontal or vertical seem to affect the reoccuring mechanical clicks. Also that the faulty sectors seem to mainly be around a certain "size" ie around 300gb full.
05-07-2009 02:52 PM
I have a Seagate 7200.11 , ST31000333AS w/ CC1H 29days old, (retailer will not take it back)
I not have the clicking sounds, but starting 1 week ago the drive drops out of site. And since it's the drive which the OS is installed on it's a show stopper.
There is alot of data on this drive i needed to recover, so this is now i did it... (may work for you?)
1) My bios really didn't like this drive dropping in and out (it is the main boot device), so it got to the point were the bios wouldn't post, even with all drives removed, so i reset it my removing and then replacing the battery. (Asus turbo MB).
2) the bios startup is slow with the drive connected now, most times it will not be able to find the drive and will just go to a black screen. But every say 20th restart the drive will post correctly? and boot my OS. Once the OS is loaded and running, it can be unstable and freeze up.... but last night i got luckly (with the drive that is) and the OS/drive seemed stable, i was able to copy all my important data of the drive to a number of smaller drives, all WD by the way.
The drive may not be readable on the next restart so for now i'm not going to turn the system off.... today i'm running the seatool on the drive again. The tool saids the drive is okay, and will not report the serial number?
one thing, when i was copying my data, i had about 3 files that where unreadable. but i just kept going!
the pc has been up for 20hours now, but the end seems near.... with no site of a CC1H fix? i will start the warrent chicken dance asap, if i get a replacement i will sell it on ebay asap, if i don't it will go out with the rest of the trash.
05-07-2009 05:55 PM - edited 05-07-2009 06:05 PM
05-11-2009 10:32 PM
I just wanted to post that I'm having issues with an ST31000333AS drive (1TB) running CC1F. I see updated CC** firmware's being mentioned all over, but no downloads for them provided. Possibly in part because the official Seagate line is the CC** firmwares are fine? Whatever the case, the drive is detected in BIOS most of the time, shows briefly in the Device Manager in Windows, but never shows up as either a drive letter or in the Disk Management tool.
I have a 2nd identical drive also running CC1F that seems fine for now, but lets just say I don't trust it anymore.
05-15-2009 08:28 AM
05-16-2009 07:52 PM - edited 05-17-2009 09:30 PM
My unaffected drive just became affected and died. It is no longer detected upon bootup. It was the storage drive for my HTPC, containing my movie collection, and it took nearly 200 hours to copy everything onto it from my stacks of DVDs. I talked to Seagate chat support, and because my drive is not "affected" (meaning it doesn't have an early version of the firmware, one that seagate was actually willing to fix), he said that seagate is unwilling to offer free data recovery. Thanks a lot Seagate. Why do other people with the exact same issue and the exact same part get free data recovery while I get jack diddily squat?
Seagate 7200.11 1.5TB
Today my hard drive is detected by the BIOS, and starts to load into Vista before getting the blue screen of death and automatically restarting before I can copy down the error code. Trying to start up Vista in safe mode results in the system hanging on crcdisk.sys. Seagate tech support has me running SeaTools for DOS, the long test. They are strongly insistent that it's not a firmware problem. I don't know what to think anymore. Why wasn't it showing up in the BIOS and why is it showing up again now? It's a mystery.
The Seatools for DOS long test passed. Unable to read the error code on the blue screen during Vista startup because it would quickly restart, I pulled out my digital camera and turned it on video mode and took a video of the monitor as the blue screen came up. Then I analyzed the video frame by frame, and discovered that the error code which appeared on the monitor for 1/60th of a second was 0x0000007B. Upon googling for "vista 0x0000007B hang", I suspected that the cause of my blue screen could be the lack of a particular SATA driver, namely the one for ACHI, which I had enabled yesterday in order to see if I could get my BIOS to detect my hard drive. I went back into the BIOS and selected IDE mode for the SATA ports rather than ACHI, which allowed Vista to boot up normally. I did another S.M.A.R.T. check with Speedfan, and the drive still seems alright. But why was the drive unable to be detected by the BIOS yesterday? It's a mystery.
My HTPC works again.
05-16-2009 07:58 PM - edited 05-16-2009 07:59 PM
i'd suggest going to bbb.org, searching nationwide and opening a case, it's free and it works. i haven't used it on seagate yet because first i googled their bbb people and contacted them through there.. the (higher powered) people.. but they said as long as seatools passes, it's ok. call us when it fails. seatools consistently crashes on any chipset/sata controller during zero fill...
is ANYTHING happening as far as a class action lawsuit?
i implore everybody who is having this issue with BBB to report it, they do not deserve the A+ they have.
i wouldn't be surprised if they delete this post.
also, leave them a review, looks like someone already mentioned it.
05-17-2009 04:36 AM