The background: Have built many PC's over the years, installed numerous HDD's, have changed from using Fdisk to using manufacturer Software.
The Problem: Have recently added a SATA drive to my system, the first one I added was a WD2500KS, installed it using WD software, transferred my OS from my old IDE to new SATA. On cold boots the drive fails to be recognised (sometimes), "disk read error press ctrl+alt+del" on screen just after the bios information had come up. Occassionally it freezes during the Bios information. Once Ctrl+alt+del'd it works fine, i.e. a warm boot is ok.
I exchanged the drive for another one, the supplier found fault with the first, I followed same procedure same thing happened. Returned it, they found fault, I got another drive, tried the same thing got the same result, returned this drive they found fault. So three WD2500KS's were all faulty (although SMART showed nothing on any of them, and they all worked fine) All were jumpered down to 150, although they worked just as well/badly without the jumper.
So I tried again with a 7200.10 320Gb from Seagate, this worked better, but is now doing the same thing, Used Seagate tools this time, had been in the machine for 1-2 weeks before symptoms. I can't believe that I've had 4 bad disks, although they claim to have found fault with 3 of them.
The Question: am I doing something wrong, I shouldn't need sata disks as windows recognises it, and its a virtual 3rd IDE port, and I'm not raid. Should I use Fdisk, although can Fdisk see this big a drive? Is not using Fdisk causing the problem, I thought the software should work though, as thats what it is there for, to migrate from current drive to bare empty drive. Was copying from IDE to SATA a bad idea, the IDE install was fresh to this mobo and general setup.
I'm re-organising my storage at the moment so that I can attempt to reformat this drive, or can I just reformat the MBR. I'll get myself to a safe position first before I do anything.
Only other symptom I had was that the first WD would be cool (32) whilst in use, and get warm (44) when idle, like it was doing something in background (formatting perhaps). But the formatting in the software isn't that quick , so I doubt it was quick format.
Any thoughts from anyone? mobo details in sig.
Sorry for the long post.
The Problem: Have recently added a SATA drive to my system, the first one I added was a WD2500KS, installed it using WD software, transferred my OS from my old IDE to new SATA. On cold boots the drive fails to be recognised (sometimes), "disk read error press ctrl+alt+del" on screen just after the bios information had come up. Occassionally it freezes during the Bios information. Once Ctrl+alt+del'd it works fine, i.e. a warm boot is ok.
I exchanged the drive for another one, the supplier found fault with the first, I followed same procedure same thing happened. Returned it, they found fault, I got another drive, tried the same thing got the same result, returned this drive they found fault. So three WD2500KS's were all faulty (although SMART showed nothing on any of them, and they all worked fine) All were jumpered down to 150, although they worked just as well/badly without the jumper.
So I tried again with a 7200.10 320Gb from Seagate, this worked better, but is now doing the same thing, Used Seagate tools this time, had been in the machine for 1-2 weeks before symptoms. I can't believe that I've had 4 bad disks, although they claim to have found fault with 3 of them.
The Question: am I doing something wrong, I shouldn't need sata disks as windows recognises it, and its a virtual 3rd IDE port, and I'm not raid. Should I use Fdisk, although can Fdisk see this big a drive? Is not using Fdisk causing the problem, I thought the software should work though, as thats what it is there for, to migrate from current drive to bare empty drive. Was copying from IDE to SATA a bad idea, the IDE install was fresh to this mobo and general setup.
I'm re-organising my storage at the moment so that I can attempt to reformat this drive, or can I just reformat the MBR. I'll get myself to a safe position first before I do anything.
Only other symptom I had was that the first WD would be cool (32) whilst in use, and get warm (44) when idle, like it was doing something in background (formatting perhaps). But the formatting in the software isn't that quick , so I doubt it was quick format.
Any thoughts from anyone? mobo details in sig.
Sorry for the long post.