Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

there is one particular file that my external hard drive always freezes on when I try to read. Since I know a bit about HDs and RAID, I would have thought it should try to automatically perform error recovery and rewrite the content to another working location on disk, or at least inform me of the error. I've tried to do it several times and the HD just freezes, nothing else. I've installed HDTune (Win7 user) and all it said was I have 13 bad sectors out of millions. I'm in the process of backing up important stuff, but is this a sign that the disk is soon to be junk?

share|improve this question

did you try to fix your bad sectors? please read this article : click here

also there are several commercial applications which perform this task. you can try them.

share|improve this answer

If you've been able to identify the hard drive that is causing the problem, I would say replace it right away and let your array rebuild. IF you're using Raid 5, maybe just add another spare and let it build up to Raid 6. Then the hard drive with the problems so your array doesn't suffer from down-time or much performance degradation, and run some low level diagnostics on it, including a surface scan to identify and mark the problem areas bad. It's better to have questionable areas permanently marked as BAD rather than to try to recover data from them and have them marked as GOOD, when those sectors will just immediately fail again.
The article referenced above is akin to running a CHKDSK /R which painstakingly reads and tests every sector of a drive, and hammers any bad spots to try to recover data from the bad spots and sometimes mark the sector as "good" again and does not even apply to a RAID array. In this case, you indeed do have a RAID array, so that should be completely unnecessary, and not something you would want to do. It would be a terrible strain on all your drives and would not fix your underlying problem.

In any case, I would not re-integrate that drive back into the array, as I'm assuming integrity is the paramount.

You could easily use it for an Un-Raid system without any real risk, however, which is sort of a mix between a JBOD and Raid 4. IT uses one drive for parity for all the other drives that it treats as one large drive. No striping, so if a drive is removed, the data on that drive is still usually usable, and can be replaced and rebuilt by another drive from the other drives and the parity drive, like Raid 4.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .