My E: drive (primary slave) keeps crashing. I use it as a backup drive, so I try to transfer tons of data to it. It gets about 90% of the way through, and then I start getting the "Directory E:\ is corrupt and unreadable, please run CHKDSK". I reboot, reformat the drive and try again, same thing. I have swapped out the drive and the new drive does the exact same thing. I wiped the system, reinstalled completely, tried again, and got the same thing. I swapped out the drive cable (both master and slave are UATA/133 on the special blue/black/grey UATA/133 cable) with a brand new one, same thing.

Any ideas? Is it possible the motehrboard will just hate wahtever drive is set as a slave on that cable? Should I think about getting a PCI HDD controller and hooking the backup drive to that? Any help is much appreciated!

Jon

http://computing.net/hardware/wwwboard/forum/42259.html
Run the diagnostics diskette from the manufacturer to find errors and correct them.A bad drive creates random data errors and the errors come back even if the drive is recertified by the manufacturer's diskette(or cdrom).It is just a matter of time before it is impossible to repair and the program says so.Crosslinked files may happen with a corrupted FAT(file allocation table).Using NTFS based partitions may help if the hard drive is found as being in good working condition.The above reply to a similar Post referring to PCI IDE RAID controller card explains how to setup the IDE RAID Ultra ATA 133 pci controller card for IDE data drives or cdrom drives.Such a card can also be used on slower bus(66 MHz or 100 MHz vs 133 MHz)without problems.Good luck.

That is somewhat helpful... I can correct the errors that are there with no problems, the question is why does this keep happening? Keep in mind that I put in a brand new HDD and the SAME thing happened. Right now I'm trying copying the info to the backup drive in segments (copy for an hour, turn off the PC for a half hour, reboot, scan and defragment the disc, then proceed). So far it's working, but I'm afraid the disk is just going to crash again.

I'm worried it may be something on the motherboard, as the new drive (installed on a freshly installed OS) did the SAME THING as the old one.

Any more advice is GREATLY appreciated (I'm at my wit's end).

a similar thing happened to me and i assumed that the original bad hard drive had over time corrupted the IDE interface/bus on the motherboard. I'm not sure if this is theoretically possible, but it seemed to be the most likely conclusion.

"If we don't succeed, we run the risk of failure." - BILL CLINTON

Check the mfg. website of your Motherboard, and see if there's a BIOS Update for your prb. Have you tried different IDE cables?

I believe in the Big Bang. God said it, and BANG it happened!

Check the mfg. website of your Motherboard, and see if there's a BIOS Update for your prb. Have you tried different IDE cables?

I believe in the Big Bang. God said it, and BANG it happened!