Article View: comp.sys.ibm.pc.hardware.storage
Article #458Re: Problem with Western Digital's WD6400AAKS
From: Rod Speed
Date: Sat, 06 Sep 2008 08:51
Date: Sat, 06 Sep 2008 08:51
94 lines
4917 bytes
4917 bytes
Penang <kalambong@gmail.com> wrote: > I need to to know if people with huge capacity SATA hard > drives (500GB and up) have the following problem : No they dont. > Bought a new hard drive, install it, formatted the disk, install the > OS, use it for 2 months, and then weird things start popping up. > The hard drive that I am using is Western Digital's WD6400AAKS -- a 640GB hard drive. > I bought it to replace my 250 GB drive, which is running out of capacity. I do a lot of video editing. Hard core porn eh ? > Bought the hard drive back in 2nd of July this year. Install the hard > drive into my PC, partitioned it into 2 logical volume (Drive C: and > Drive D:) and then install the OS onto it. The OS that I use is Win > XP. The HD is formatted under NTFS file system. > Drive C: has 30 GB and the rest, about 570GB, falls under drive D: > I ran chkdsk (check disk) on both partitions (chkdsk /f /r /x) and there wasn't > any error. So I thought I had bought a good drive and was feeling very happy. > It runs okay for 2 months, and then ... > Sometimes when I start my PC, the PC can't find the drive. Likely because the bad is first physical sector. > Other times, the PC can find the drive, but running extra ordinarily slow. Likely because its retrying on the bads. > I dropped down to the Command Prompt level, use "chkdsk" again to check what's wrong. > The command that I use is still the same "chkdsk /x /r /f" --- to > dismount the disk, and to "fix" the disk if there is anything wrong, > and to check (recover) bad sector. > Long and behold, there _ARE_ bad sectors !! > Drive C has 82KB of bad sectors, and Drive D has 288KB of bad sectors. Post the Everest SMART report on the drive. http://www.majorgeeks.com/download.php?det=4181 > This is a drive that I'd just used for 2 months !! And the > manufacturing date (the date stamped on the label of the drive) > indicated that it was made June, 2008. In all account, this is a > _NEW_ drive, and it is developing BAD SECTORS !!! > The 250GB drive that I used never gave me any problem. > This 640GB, however, worries me ! > I know that 400KB of bad sector, for a 640GB (actually it's 597GB > after formatted) hard drive, is insignificant. But still, bad sectors are > still BAD SECTORS, and I am afraid that the bad sectors would spread !! Not spread so much as that many bads do indicate the drive is likely dying or that the rest of the system does have a serious problem. > That is why I am posting this message, asking the people > who have more experience than me in using huge capacity > hard drive --- is the bad sectors common occurrance? Nope, the drive is likely dying or that the rest of the system does have a serious problem. > Or that I'm just too unlucky to get myself a lemon? Impossible to say yet until its clear if the drive is dying or if the system has a problem. > BTW, the hard drive is EXTREMELY HOT, not warm, but VERY HOT !!! Thats certainly bad and may well be the cause of the bads. > I do not have the actual temperature in it (I do not know if there is any > utility out there that would give me the drive's actual temperature) Yes, the Everest SMART report will show the drive internal temp. > but when I touch the drive, it was very HOT !!! > Please, please help. Post the Everest SMART report on the drive. http://www.majorgeeks.com/download.php?det=4181 And do something about the drive temperature. If its mounted adjacent to another drive, have a free slot between the drive and the other drive. If there is no way to have a free slot adjacent to the drive, add a fan blowing over the drive.
Technical Details
Message-ID:
<6ieuk4Fqc3afU1@mid.individual.net>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mailReferences:
<0be95232-1d86-4262-8806-9bfb0ed20e59@a3g2000prm.googlegroups.com>Show Full Headers
Complete Article Headers
X-Google-Thread: f4d7c,1d4e6eec42071101 X-Google-Thread: 10a2ed,1d4e6eec42071101 X-Google-Thread: 108f8f,1d4e6eec42071101 X-Google-Thread: f5f89,1d4e6eec42071101 X-Google-Thread: faa3c,1d4e6eec42071101 X-Google-Attributes: gidf4d7c,gid10a2ed,gid108f8f,gidf5f89,gidfaa3c,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Rod Speed" <rod.speed.aaa@gmail.com> Newsgroups: comp.sys.ibm.pc.hardware.storage,alt.comp.hardware.pc-homebuilt,microsoft.public.windowsxp.hardware,alt.comp.hardware,24hoursupport.helpdesk Subject: Re: Problem with Western Digital's WD6400AAKS Date: Sat, 6 Sep 2008 18:51:14 +1000 Lines: 96 Message-ID: <6ieuk4Fqc3afU1@mid.individual.net> References: <0be95232-1d86-4262-8806-9bfb0ed20e59@a3g2000prm.googlegroups.com> X-Trace: individual.net S8eA4iWvo1uCD8uw9KRcAgTidplNvYhHWtX2tINoLg54CGvCI= Cancel-Lock: sha1:p/SL2s/JESqdwCkSc6LQOZyLrAk= X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-RFC2646: Format=Flowed; Original