Hard disk problems

So the other day, my 3rd Hard Disk suddenly lost connection to the OS. It can still be detected by the system as it's being listed on the device manager, but it can't seem to be read. I tried deleting the volume and reformatting. However, quick format would fail and long format would just end up being stuck.

Taking a look into event viewer, I found relevant warnings that I think might point to the problem. There are warnings that is sourced from "storahci" and it would say "Reset to device, \Device\RaidPort0, was issued" and another sourced from "disk" warning saying "The IO operation at logical block address 2c88 for disk 2 was retried". Im getting a lot of these warnings and I'm guessing it's a hardware malfunction. Could it be the SATA port or the hard disk itself?

Further tests with SeaTools show that the drive is healthy however. I performed S.M.A.R.T, short DST, and short generic tests and they all passed.

What could be the problem and how can I solve this?

EDIT: Looking back further into event viewer, I'm getting an error sourced from "Ntfs" saying "a corruption was discovered in the file system structure on volume E: The master file table (MFT) contains a corrupted file record. The file references number is 0xa0000000000a. The name of the file is "<unable to determine file name>".
12 answers Last reply
More about hard disk problems
  1. If you are using RAID, try testing the drive outside of a RAID array (turn off RAID in bios or use a different computer or USB cradle).

    It could still be a drive issue. Test it outside of a RAID environment with SeaTools with a LONG test (not short), and see if it confirms good or bad. Beyond this, it COULD be your motherboard's RAID/SATA controller. They occasionally fail.

    Lastly, is your computer by chance a Intel Core iSomething computer ? If so, check to make sure your BCLK is not overclocked, as many devices are highly sensitive to this BCLK clock (nominally set at 100Mhz).
  2. If you're not using the drive in RAID, open a command prompt and do a "CHKDSK X: /f", where "X" is the drive letter of the drive.
  3. Maxx_Power said:
    If you are using RAID, try testing the drive outside of a RAID array (turn off RAID in bios or use a different computer or USB cradle).

    It could still be a drive issue. Test it outside of a RAID environment with SeaTools with a LONG test (not short), and see if it confirms good or bad. Beyond this, it COULD be your motherboard's RAID/SATA controller. They occasionally fail.

    Lastly, is your computer by chance a Intel Core iSomething computer ? If so, check to make sure your BCLK is not overclocked, as many devices are highly sensitive to this BCLK clock (nominally set at 100Mhz).


    Anonymous said:
    If you're not using the drive in RAID, open a command prompt and do a "CHKDSK X: /f", where "X" is the drive letter of the drive.


    The thing is I am not using a RAID setup, I'm using SATA AHCI. Other disks on other SATA ports are working properly. It's just the disk I'm trying to fix is not accessible. A chkdsk would not work since it is currently a RAW drive because I deleted the volume. I don't think I'm overclocking anything.

    It might be useful to add that I left my computer shut off for a little more than a week and when I started it again, that is when the errors from the disk started coming in. Another useful information may be that I am running windows 8 x64
  4. kotsumu said:
    Maxx_Power said:
    If you are using RAID, try testing the drive outside of a RAID array (turn off RAID in bios or use a different computer or USB cradle).

    It could still be a drive issue. Test it outside of a RAID environment with SeaTools with a LONG test (not short), and see if it confirms good or bad. Beyond this, it COULD be your motherboard's RAID/SATA controller. They occasionally fail.

    Lastly, is your computer by chance a Intel Core iSomething computer ? If so, check to make sure your BCLK is not overclocked, as many devices are highly sensitive to this BCLK clock (nominally set at 100Mhz).


    Anonymous said:
    If you're not using the drive in RAID, open a command prompt and do a "CHKDSK X: /f", where "X" is the drive letter of the drive.


    The thing is I am not using a RAID setup, I'm using SATA AHCI. Other disks on other SATA ports are working properly. It's just the disk I'm trying to fix is not accessible. A chkdsk would not work since it is currently a RAW drive because I deleted the volume. I don't think I'm overclocking anything.

    It might be useful to add that I left my computer shut off for a little more than a week and when I started it again, that is when the errors from the disk started coming in.


    Okay, the best bet would be to try it on a different computer. If you don't have a different computer, do you have a USB-sata cradle or adapter ? If you don't have that either, try the HDD on a known-good SATA port. Try and isolate to see if it is indeed a HDD issue (to eliminate the SATA ports and controllers).
  5. Change the cable too, just to eliminate that as a potential source of problems.
  6. Thanks for the help guys, so I was able to format disk by switching it to a red sata port which according to my mobo manual is a jmicro controller. So what was the problem with the specific sata port? Did it kinda just die?
  7. I've had one die once, but in my experience it is rare.
  8. kotsumu said:
    Thanks for the help guys, so I was able to format disk by switching it to a red sata port which according to my mobo manual is a jmicro controller. So what was the problem with the specific sata port? Did it kinda just die?


    It very well COULD be. Double check your BCLK clock. Win8 is particularly sensitive to BCLK clock for device stability. Can you try another working drive on the suspect SATA port ?
  9. Maxx_Power said:
    kotsumu said:
    Thanks for the help guys, so I was able to format disk by switching it to a red sata port which according to my mobo manual is a jmicro controller. So what was the problem with the specific sata port? Did it kinda just die?


    It very well COULD be. Double check your BCLK clock. Win8 is particularly sensitive to BCLK clock for device stability. Can you try another working drive on the suspect SATA port ?


    I could try another drive on that SATA port. The funny thing is if it was the SATA port's problem, why would it even still detect the device? In theory it shouldn't be able to. I'll take a look at overclock settings, but I'm pretty sure I did not overclock anything.
  10. kotsumu said:
    Maxx_Power said:
    kotsumu said:
    Thanks for the help guys, so I was able to format disk by switching it to a red sata port which according to my mobo manual is a jmicro controller. So what was the problem with the specific sata port? Did it kinda just die?


    It very well COULD be. Double check your BCLK clock. Win8 is particularly sensitive to BCLK clock for device stability. Can you try another working drive on the suspect SATA port ?


    I could try another drive on that SATA port. The funny thing is if it was the SATA port's problem, why would it even still detect the device? In theory it shouldn't be able to. I'll take a look at overclock settings, but I'm pretty sure I did not overclock anything.


    Some times by default (ASUS, Gigabyte, MSI all do this), the BCLK clock is bumped up a notch (to say 103 Mhz) to improve benchmark performance by the manufacturers.

    Perhaps the SATA port isn't fully broken ? It might enumerate devices okay but have data integrity issues...
  11. Oh ok, thanks for your help. I believe I'll be able to troubleshoot this myself from now on.
  12. kotsumu said:
    Oh ok, thanks for your help. I believe I'll be able to troubleshoot this myself from now on.


    Glad to be of help. Good luck!
Ask a new question

Read More

Device Manager Connection Storage Hard Drives