# Odd HDD failure scenario

**URL:** <https://boards.straightdope.com/t/odd-hdd-failure-scenario/359965>\
**Category:** Factual Questions\
**Created:** [June 8, 2006, 10:24pm UTC](https://boards.straightdope.com/t/odd-hdd-failure-scenario/359965 "2006-06-08T22:24:06Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![Harmonious\_Discord](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@Harmonious\_Discord](https://boards.straightdope.com/u/Harmonious_Discord)\
**Post date:** [June 9, 2006, 2:10pm UTC](https://boards.straightdope.com/t/odd-hdd-failure-scenario/359965/21 "2006-06-09T14:10:49Z")

</div>

> [@drachillix](#):
>
> but if I use recovery console in xp it can see files. I can run a dir, chkdsk, and nothing seems amiss. The only indication I can find of failure is the failure to boot the machine. It would seem to me that if it can find and display the contents of the C: drive then it can read at least to some degree.

It’s a bad boot sector if files can be read.

I don’t know which format you are using so I’ll refere to it as FAT File allocation table. The FAT starts on sector one and expands adding a sector as space is needed. The FAT keeps track of where the firist sector of the file is located. The end of a sector has the address of the next sector the file is on, and the file is read like that until an End of File charactor is found. $FF  
So a bad FAT would not show all the files being there.

A change in how the Bios interprets the stucture of the hard drive, can leave a readable FAT. Some of the files will be corrupted then or completely unusable.

---

<div class="post-metadata">

**Author:** ![GusNSpot](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/gusnspot/32/436_2.png) [@GusNSpot](https://boards.straightdope.com/u/GusNSpot)\
**Post date:** [June 10, 2006, 7:58am UTC](https://boards.straightdope.com/t/odd-hdd-failure-scenario/359965/22 "2006-06-10T07:58:20Z")

</div>

Find a working computer. Take the hard drive in question and after opening the case, install the broken Hard Drive as a slave drive or a master drive on IDE 2.  
Boot system.  
Format broken Hard Drive.  
Then, run scan disk on the broken Hard Drive.

If bad sectors are shown, either block them out, throw the Hard Drive away, or if it will store information and it is retrievable, use the drive as additional storage if the information is not critical.

Do not use the USB link for testing nor an external HD hook-up.

I don’t care what the books say, don’t do it.

YMMV

---

<div class="post-metadata">

**Author:** ![Alex\_Dubinsky](https://avatars.discourse-cdn.com/v4/letter/a/dbc845/32.png) [@Alex\_Dubinsky](https://boards.straightdope.com/u/Alex_Dubinsky)\
**Post date:** [June 11, 2006, 9:46am UTC](https://boards.straightdope.com/t/odd-hdd-failure-scenario/359965/23 "2006-06-11T09:46:12Z")

</div>

**Harmonious Discord** and **GusNSpot** give advice that is in general valid and good, but it’s clear they haven’t been paying attention to the thread at hand.

Nothing regarding what the OP said indicates that the problem is bad sectors! Nor is it the way the IDE controller chooses to format the disk. (harmoneous discord, welcome to the second half of the present decade…) The problem is the BIOS is not even detecting the hard drive, but windows is able to somehow reinitialize it and get it to work. This is probably due to a slightly broken HDD controller. (and no, it doesn’t have to be cracked. components can fail by themselves.)

There are two solutions. Randomly mess with bios settings to maybe get it to work. Or RMA the mofo.

[Previous page](https://boards.straightdope.com/t/odd-hdd-failure-scenario/359965.md?page=1)