Seagate 1.5TB drive on the fritz?

Discussion in 'PC hardware help' started by rubixcube, Feb 3, 2011.

  1. rubixcube

    rubixcube Regular member

    Joined:
    Oct 31, 2004
    Messages:
    285
    Likes Received:
    0
    Trophy Points:
    26
    Hey all,

    having a REALLY annoying time with my 6 month old seagate 1.5TB hard drive. Apparently it's the latest firmware model (CCxx) that isn't supposed to have the issues that some of the old ones were seemingly plagued with. Currently running it in AHCI mode on the Intel ports alongside a RAID0 array on the JMB363 controller. I have Intel rapid storage manager and all appropriate drivers installed in windows 7 pro x64. Every now and then (sometimes days inbetween), for no reason whatsoever, intel storage manager will pop up with a message "Disk on port 0: removed". After this point I cannot access the disk, as it says the device is disconnected. All I do to fix it is hit the 'refresh' button in intel storage manager, it says "Disk on port 0: detected" and bob's-your-uncle everything is fine until it decides to do it again. The SATA cable is fine, I have checked that.. and I ran SeaTools Short DST and SMART check which both passed. Long DST check got stuck, so now I'm going through a grooling chkdsk /x /r, which is scanning at less than a file a second with 4000 files to go. Interestingly, I think a couple of bad clusters must've been hit. See this image. Sequence of events on each of those bad cluster lines was

    1. disk craps out, says it's disconnected.
    2. I hit refresh in intel storage manager, reports it as reconnected.
    3. chkdsk then says it has found bad clusters.

    I'm unsure if chkdsk is reporting bad clusters because it has been interrupted, or if there actually *are* bad clusters...?

    The folder in question "External" is from my old 500GB FAT32 formatted Seagate freeagent pro drive which used to be plugged into my PS3. It *definitely* had bad sectors on it, as windows wanted me to run a chkdsk every time I plugged it in. That possibly explains chkdsk taking so long, but the 'disk removed' error is a different kettle of fish entirely.

    Has anyone here had the same/similar problems, and if so, what solved them?

    Thanks


    EDIT: Didn't realise Long DST check takes up to 4 hours, and progress is only displayed in 10% increments. Must've been me just getting impatient.
     
    Last edited: Feb 3, 2011
  2. KillerBug

    KillerBug Active member

    Joined:
    May 21, 2006
    Messages:
    3,802
    Likes Received:
    0
    Trophy Points:
    66
    There might be an issue with the connections; those SATA power connectors need to be nice and tight or they will do something like this...I spent about 10 hours diagnosing a system with symptoms like you are describing...changed the drive twice, changed the sata port, changed the cable twice, finally switched the sata power connector from the dvd drive and the HDD started working fine...it wasn't even very loose; it just wasn't tight enough I guess. There is an easy (but a bit stressful) test for this...just wiggle the connector up and down with the system running and see if that causes the symptom. It probably wouldn't hurt to do this with the sata data cable as well; just to be 100% sure that your replacement cable isn't defective.
     

Share This Page