Need HDD Imaging help

[ViperGTS]

In the process of building this computer, I've been running into very few snags and speed bumps. Yet, the one I have run into is a doozy.

I run my system partition on a 40GB ATA HDD (boot partition). This is the C: drive. An similar 80GB HDD, D:, is attatched as the slave on the same channel.

For speed and storage purposes, I picked up a 160GB SATA I HDD and attahced it to the SATA_0 port on the motherboard. Through Windows and the Storage Management tool, I initiallized and formatted the drive as S:.

I plugged in a copy of Norton Ghost 9.0 and made a backup image of the C: drive. (A thought just occured to me...see below.) I then used Ghost to "Restore" the backup to the S: drive. After it had to force a dismount of the drive, it successfully restored it. I also checked the little box that said it would designate the drive as the Active booting partition.

I rebooted the rig, pointed the BIOS to the S: drive, and let it do it's thing. Almost immediately, the motherboard reported "Disk Read Error, Ctrl + Alt + Del to reboot."

I thought, alright, perhaps the drive is bad. I plugged in a Windows Pro disc and it formatted, installed, and booted perfectly. The boot sector is in perfect shape.

Why might this be happening?

**Here's the thought that occured to me earlier. By formatting and labelling the SATA drive as S:, then trying to restore a Ghost image to the drive referred to as C:, might that be screwing up the boot process, since Windows is being told that the one drive is being called two different drive letters?

 

[TKpervert]

I haven't messed with hard drives in years (and boy am I glad).
I do remember that there's jumpers on the drives that have to be set right for the drive to perform as master or slave.
If that's not the problem with the 160 gigger then I'm pretty clueless.

However let me say that Norton does low-level sneaky shit under the covers and just might be outsmarting itself. Norton problem ?

 

[kurchatovium]

TK might be right. Certain drives like Western Digital also have a different way of recognizing which drives are slave or master. So the jumper cable settings might be different than for most other drives. I had this problem once and once the jumper settings were right for Western everything was fine. 😀

Also I think maybe the boot disk needs to be called C: I could be wrong about this. Never really tried any other letters, so you could be write about the drive letters but maybe in a different sort of way.