cannot boot from cloned disk
I am cloning from a sata ssd to a sata hdd. Used Windows Disk Management to remove all partitions from the hdd. Then moved the hhd to the disk 1 position and the ssd to the disk 2 position. Booted from the TI CD and cloned the drive. Power off and removed the ssd. When booting starts the Windows xp starts followed by blue screen flashes and reboot starts over. Tryed Safe Mode, same results. When I put the ssd in Disk 1 and the clone in disk 2 they look identical except for drive size. Toshiba Qosmio and xp media edition. I cannot find the build #
I tryed the same on my desktop xp professional all sata drives with the same results.
You might be aware of this but . .
are you leaving the two "boot" disks hooked up at the same time? If so, when you finally get one of then to boot, Windows will mark the other as nonboot; that's how Win deals with finding two boot disk on one machine. If you clone a boot disk and leave the clone in the machine and boot up, then one day try to boot with the clone, it will not boot.
Scott,
That hasn't been my experience using several cloning apps.
The reverse should be true. If you swap HDs immediately after cloning and boot from the new HD, subsequent removal of the old HD will render the new HD non bootable. This certainly applies to Ghost. But it doesn't apply to Acronis TI. TI breaks Rule #2.
Scott? is this a case of Windows not knowing stuff and basically ruining all the disks an partitions that wre connected.
Just for fun I cloned HD0 to HD1 and left both HDs in place. Using a boot manager, I could boot either HD whenever I desired.
If the boot manager inserts itself on the 1st system disk the BIOS looks for, it can "grab hold" before the system disk looks for a boot disk (they're usually th same disk but don't necessarily have to be). It's windows that ajudicates between disk if it finds two. A boot manager can tell it to stop finding two -- or elese temporarily marks one of the disk as not a boot disk.
Scott? is this a case of Windows not knowing stuff and basically ruining all the disks an partitions that wre connected.
It's a case of how MS decided to handle the situation where there are two system/boot disks. The OS on the first system disk recognized acepts one disk as the boot disk and then marks the other as not a boot disk. It's a little more complicated than that, and it can be confusing. Consider this:
The logical volume that contains the info to boot the OS, which is known as the bootstrap, is formerly called the system volume . There can be only one system volume but more than one boot volume -- well forget about boot volumes for a second. Back to System volumes, which are what contain the boot info -- there can only be one system volume and the system volume is the Active partiton so if you have a System volume, then you have an Active partiton. The reason for the redundant nomemclature is to fight against the everpresent threat of encroaching rationalism.
Okay, fine. So what about boot volume? Oh, well, the volume that contains the OS system files (the stuff that gets loaded after the bootstrap -- remember the system volume -- has done its work), the the thing that comes after the boot is the set of system files for the OS and these are stored on what's called the boot volume, since the name system volume has already been taken as the name of the bootstrap. The boot volume doesn't have to be the same volume as the system volume and often isn't. For example, if you clone a windows sys/boot volume from one harddisk to another and leave both attached when you reboot, Windows might assign one as the boot volume and the other as the system volume. Windows can be very democratic sometimes ;-) Of course, after such a democartic outburst, windows might then tend to treat each volume an an inferior unfit to operate and continually punish them with errors.
So to sum up, It's as easy as saying micorsoft -- the boot volume is called the system volume and the system file volume is called the boot volume. How could anyone go wrong? It all falls right out of the horses mouth:
[url]http://support.microsoft.com/kb/314470[/url]
Although, when it comes to ms programming genius, the mouth is actually the other end of the horse and for some reason the boot end is called the mouth.
Don,
The price of asking for help in a forum is a reply outlining how you have resolved your problem with the help offered by the members. Is it fixed?
To Brian K
No, I have not resolve my "Cannot Boot from cloned drive problem. None of the responses addressed my ptoblem as you know..
Thanks,
Don
Hi Don, I'm glad I stirred you up. So different software didn't work. I'm surprised. I know software that always works when the standard cloning apps fail.
Brian K
I think I will try the single issue pay approch at Acronis this week tosee if I can get this resolved. I did download the latest version TI 2009 home but have the same problem.
BACKGROUND: A few week ago I bought a Torax 128MB SSD for my laptop. I could not get TI to clone it with the same "connot boot from clone" issue, so I installed the SSD and rebuilt it for the XP cd. It works GREAT. Bootup went from over a min to 20 seconds and application load in a flash.
I wanted to test the SSD on my desktop thus I am trying to save the rebuilt SSD to a HDD for my laptop and use the HDD in the laptop while testing the dasktop.
So, the bottom line is this is not killing me but I would like to get it answered.
Thanks,
Don
Everything seems OK except "testing the SSD in the Desktop." You can't run the laptop SSD in the Desktop - unless you reclone it from the Desktop's own HDD. Anything else will produce a BSOD. You can't normally run a bootable OS drive in two different computers.
For best cloning results, use the Acronis ISO file for Rescue Media that you can download through your Acronis account. It gives you 8 different boot options.
Don,
As I mentioned in my first post, your cloning method is perfect. It's not your fault.
Could you expand on "When booting starts the Windows xp starts followed by blue screen flashes and reboot starts over"? How far into booting before the blue screens appear? Are they BSOD?
Brian K
About 2 seconds after the black screen with the Microsoft XP logo appears the screen that is blue with about 10 lines of text flashes for second then the booting process starts over like when you restart from the turn off screen.
CorkyG
I did not go into detail about booting from my desktop.
It has two sata raided drives so I had to create the new boot on a external USB SATA drive using TI cloning. Turn off the desktop. Remove the two raided SATA drives. Install the clone as Disk1. Turn on desktop and turn off the raid option then continue booting. Get the same resultes as trying to boot the laptop.
Thanks for the interest.