Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[Ray-in-CA]

I used Disk Wizard to clone a Maxtor STM3320620A which was my ATA master to a new Seagate ST310005N1A1AS-RK. The process screens looked fine and the final message was a successful clone. I pulled the Maxtor and reassigned the boot drive to SATA in bios, after the ASUS splash screen went away everything halted and "system failed to load" was displayed. Plugged the old drive back in, switched boot sequence back and all is well. System recognizes the new drive and its' structure sure looks like a clone to me.

Any suggestions? I'm willing to jump through a lot of hoops before resigning to re-install XP on this drive.

[Cantbecanit]

Hi Ray

I've a suggestion, I don't think it will cure it but it's worth a try.

Can you boot in safe mode?

If you can do that, and then restart, it could be that simple.

If it does the same again after a reboot, safe mode again and see if you can reinstall the MB chipset drivers from the MB disk, if this won't work go to control panel *assuming you got into Windows* and uninstall the following in Device Manager, ide/ata controllers and SCSI/Raid controllers, then rebbot, this time Windows should if it works find new drivers for what you've uninstalled and written them for the 1TB drive this time rather than cloning the 320 drives settings, hth.

[Ray-in-CA]

Thanks, didn't work, but I tried it. I don't think I'm getting deep enough into the OS to even allow a safe mode startup. I found a couple of tryable (free) clone utilities on cnet, wish me luck. sure do miss format c:\s. ray

[Cantbecanit]

ATA to SATA, I think this could be why, the O/S you've cloned is set up for an ATA drive, the new one is probably trying to load as an ATA drive and this is why it won't load, the only way I can think of is if you can somehow get into it and remove the drivers as I said earlier, does it show up and read as a slave drive?

Message Edited by Cantbecanit on 06-05-2009 01:14 PM

[Ray-in-CA · Accepted solution]

Thanks Cantbecanit, I also came to the conclusion it was the ATA / SATA swap that caused my problem. I guess bios handles them differently, I had to play with the drive and partition calls in boot.ini before system could locate \windows.

Thanks again for the input -Ray