Discussion Locked

FAT problems on Hard drive

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have been experiencing problems on a Seagate hard drive. It is a 30.6 Gig Baracuda drive with ATA 66 capability. The Hard drive first ran on a PII system using ATA 33 and it worked fine with no problems. The computer was upgraded to a PIII system which uses the VIA chipsets on the motherboard. I have changed the IDE cable on the drive to use the ATA 66, but since then, even if I repartition the drive with this cable and reload Windows 98, I get problems on my FAT table, and scandisk truncatesthe files on the drive, it doesn't matter how many times in succesion you run scandisk, it gives the same problem. If I put the old cable back, under Windows the drive struggles to read the FAT table, but then there is no problems. Under Dos, using the new and the old cable, there is no problems with the FAT. Is there a problem on the drive itself, or is there a patch from Microsoft to correct this problem, because it only starts acting up after loading about 7 gig. I have installed the latest chipset drivers, but it still does the same if you use VIA's driver or if you just use the Windows standard driver. Can anyone hlp please?

7 replies

by geroxx

It sure sounds weird... Have you tried to use another ATA66 Cable? These cables have 80 conductors instead of the normal 40. I would be hard pressed to call the HD bad at this point. One good tip... If you have a 7200 RPM or higher HD it is a good idea to use some form of HD cooling or at the very least do not stack it next to the FD where the spindle gets not air flow. I have seen a couple of HDs go out due to lack of cooling.

I don't think that 7GB is a magic number unless you have some severe surface damage. When you reformat did you use the /u switch? This makes it record the bad sectors again (if I remember correctly).

I am assuming that this is a different Motherboard than the P2 system or did you just upgrade the Processor? Either way, I would say that you might have problem with Power Supply loading maybe. It sounds silly maybe but if have had flakey P.S. cause HD data problems. They checked good with a DVM but were noisy when checked with an O-scope. I have even had them look OK on the scope but still be a problem because when a new P.S. was used... all the problems went away. It would help if you had another system (with ATA66) to test the drive in.

Gary

by mike_wilson

Sounds like you need more than just the basic Windows diagnostic tools. Run Partition Magic 6 from Powerquest www.powerquest.com . Another suggestion would be Norton Utilities 2001. Good ol' Spinrite, version 5 wields a powerful hammer, too. Good luck and let us know. If all these fail to fix your wagon, be sure to obtain an RMA within the specified warranty period.

by themain

reading over your description i fail to find if you have just hooked up the drive to the new motherboard, or did you go to the trouble of breaking the partitions with fdisk. i have tried to switch drives from one bios manufacturer to another and found the drive unbootable in the "foreign machine". this will involve reinstalling everything of course. using a drive image utility will just recreate the error so i don't suggest that will solve anything. have you tried a newly fdisk'd / formatted drive as a test with the cable ? the analogy would be to a floppy drive with missaligned heads.

by destroyer

I have reformatted the drive, repartitioned, this weekend I even ran Seagate's Disc Manager program, thinking that it might be bios translation problems, but there is still no go. Reloading the machine again, when I checked the drive the first time,it had about 2 gig on it and there was no FAT problems. I loaded other things, bringing up the total space used to about 8 gig, andthe FAT problems started all over again. I replaced the cable, still the same error. There is also a 3.4 Gig HD in thesystem which I just hooked up to it and it works like a charm, the 30 gig drive i the only drive that gives me this hassle.

This discussion is closed to new replies.