weird SATA/ATI9 problem

Running ATI 9 (build 3694) on an Asus A8N32-SLI Deluxe and am having a weird problem. NForce 4 chipset sets the SATA ports up as 3M through 6M. OS drive is connected to port 5M, SCRAM drive on 6M, Clone target is on 3M, and 2M is vacant.

ATI first has problems identifing the drives correctly. It believes SATA drives are IDE primary and slaves; and thinks that the Silicon Image SATA port is a SCSI port.

I then set up ATI to do manual (or automatic, it does not help problem) clone with 5M as source and 3M as target, clear partitions on target before cloning and now the serious problem begins. Once I reboot to begin image creation, ATI9 loads and within 3 seconds, returns the message that it is finished (yer a$$ you are) and press any key to shut down. ATI9 does nothing at all, and on reboot tells me that it must sychronize the source drive with the OS (are you crazy! leave the source alone).

I know that the NForce 4 chipset's SATA ports are twitchy to say the least, But at least ATI could ID SATA ports correctly.

I also know this issue is probably due mainly to the ASUS Mobo, but is anyone else having this problem? Is there a way around it? Maybe move the SATA connectors around to get them where ATI thinks it cloning primary(or master?) IDE to secondary(or slave?) IDE

Lost in the mountains with a Pyrenees puppy

 

Hello Jeff,

Thank you for choosing Acronis Disk Backup Software.

Please accept our apologies for the delay with the response.

First of all, please check both the source and destination hard drives by Windows utility: use Windows menu Start\Run, then enter the command "chkdsk c: /r" "chkdsk d: /r" for every partition of your hard drive.

Note that you will need to reboot your computer in order to scan the system partition.

Please also download the latest version of Acronis drivers, install it with disabled logging, try to perform the disk cloning once more and see if the problem still persists.

If the problem still persists after checking the hard drives and updating the drivers, please also try to perform the disk cloning process when your computer is booted from the Bootable Rescue CD created using the latest build (3677) of Acronis True Image 9.0 Home and see the result. In such a way you will be able to exclude the possibility of any third party software interfering with Acronis True Image 9.0 not allowing it to clone the hard drive, as no operating system or any other applications are running when your computer is booted from the Bootable Rescue CD.

Note that, as it is mentioned in section 6.1 of Acronis True Image 9.0 Home User's Guide, "disk letters in standalone Acronis True Image Home might sometimes differ from the way Windows identifies drives. For example, the D: drive identified in the standalone Acronis True Image Home might correspond to the E: drive in Windows". We therefore recommend that you assign a meaningful labels to the partitions of your hard drives so that you can easily identify them when Acronis True Image 9.0 Home is operating in Acronis Rescue Environment, i.e. when your computer is booted from the Bootable Rescue CD or Acronis Startup Recovery Manager is used.

Also, note that after the disk cloning is finished you should unplug one of the hard drives prior to booting into Windows for the first time. The point is that keeping two identical hard drives (hard drives having identical digital signatures) connected at the same time is "unpleasant" for Windows and might cause a number of boot and\or drive letter assignment problems. After you boot into Windows from one of the hard drives at least once, please feel free to turn off the computer and connect another disk.

If the problem still persists then please create Acronis Report and Windows System Information as it is described in Acronis Help Post. Please keep both the source and destination hard drives connected while creating Acronis Report.

Then please submit a request for technical support. Provide the files and information collected in your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will investigate the problem and try to provide you with a solution.

Thank you.
--
Alexey Popov