[aod]

Hi All,

I've just joined, hope you can help as other forums I've found are unresponsive, and my post gets lost after a couple of hours! :(

I have a problem with my new hard disk. I’ve replaced my 120gb one with a new 320gb disk. So far I’ve:

1) Installed the disk, flashed my BIOS to enable it to read the full capacity
2) Copied the data from the old drive to the new
3) Removed the old drive and placed the new one it’s IDE channel

My PC has two hard drives, one for the system (60gb), and one for all my data/documents (the old 120gb/new 320gb).

This is how my IDE channels are set up normally:

IDE Pri – Master 60gb System HD
IDE Pri – Slave 120gb Data HD

IDE Sec – Master DVD-R/W
IDE Sec – Slave DVD-ROM

For the purpose of transferring files from the 120gb HD to the new 320gb HD, I removed the slave DVD-ROM and plugged in the 320gb HD as a slave. After the BIOS update it detected, and worked fine (jumpers set accordingly)

When I moved the new 320gig drive to the slave Primaray IDE channel, the BIOS stopped detecting the disk, and at times even the system disk. After a lot of messing about, changing jumpers, checking cables, other disks etc, I finally decided to use the cable select configuration to boot the disks. So both HD’s have the cable select jumper setting, and master cable goes in the system disk, the slave cable goes in the data 320gb disk.

It worked fine, once, maybe twice, a couple of times it didn’t detect either, but after a reboot, more often than not, it will detect the system disk and not the data disk.

For the time being, i've removed the slave DVD-ROM on the secondary IDE, and put the new HD there, It works fine.

Any ideas why it's not working properly on the primary IDE as a slave?

Thanks

[mattyra1912]

I have also had this problem before. How i solved it was to seperate the HDDs and put them on seperate IDE cables. Although i also ran into the problem that the IDE cables werent designed correctly to do this and had to purchase other cables. Im not to sure how this error is occuring but this is a quick fix and works perfectly fine for me. I decided to upgrade my machine to SATA 2 a much better solution ;) but can be costly lol