The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Getting atapi 11 errors.. How to tell if it's the HDD or the chip?

    Discussion in 'Sager and Clevo' started by X2Eliah, Apr 17, 2011.

  1. X2Eliah

    X2Eliah Notebook Guru

    Reputations:
    28
    Messages:
    52
    Likes Received:
    0
    Trophy Points:
    15
    Hey folks, I think I might have a problem with my Clevo W870CU.
    Lately, there's been quite noticeable issues with the system - for instance, opening an i-net browser is fast, loading any page for first time takes a ton of time (Chrome, for example, shows 'waiting for cache'), after that, it's plain sailing. During these hangouts, the system's nearly unusable, and any user activity will likely crash the process/prolong it.

    The event log shows that coinciding with these times, there are bursts of atapi errors (error code 11; "The driver detected a controller error on \Device\Ide\IdePort0."). That's the location of my C: drive. Usually these bursts are with 4-5 errors in row, in the same time-stamp. Sometimes, more, and a warning "Ntfs; The system failed to flush data to the transaction log. Corruption may occur."

    According to MS, this error can be thrown both when the hard drive is failing, or when there is a hardware problem with the controller itself - but there's no way to determine which one without disassembling the system.

    So, er, is there a sure-fire way to determine which of those two is at fault? If it's the HDD, then I could just get an SSD instead; if it's the controller, I'd rather not waste money on a new drive.
    I ran the chkdsk, that found no issues; hdtune finds two bad sectors (224MB size / block) reliably, so they are there..
    The kicker is, I got two disks in the system - identical - and the second one is not showing any problems or errors at all, it's only the system disk that does this.
     
  2. sarge_

    sarge_ Notebook Deity

    Reputations:
    288
    Messages:
    896
    Likes Received:
    1
    Trophy Points:
    31
    It's probably the HDD. Easy check: switch them places. :)
     
  3. X2Eliah

    X2Eliah Notebook Guru

    Reputations:
    28
    Messages:
    52
    Likes Received:
    0
    Trophy Points:
    15
    Hmm.. The boot order won't be ruined by that? Might be worth a shot..
     
  4. TechnoWhore

    TechnoWhore Notebook Evangelist

    Reputations:
    101
    Messages:
    310
    Likes Received:
    14
    Trophy Points:
    31
  5. X2Eliah

    X2Eliah Notebook Guru

    Reputations:
    28
    Messages:
    52
    Likes Received:
    0
    Trophy Points:
    15
    Well.. I did say this in the OP, you know. I appreciate the intention, at least.
     
  6. TechnoWhore

    TechnoWhore Notebook Evangelist

    Reputations:
    101
    Messages:
    310
    Likes Received:
    14
    Trophy Points:
    31
    Sorry, missed that last part.