no boot, vista partition to partition
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Currently am running windows vista off a 60GB SSD that i want to erase and use as a cache drive for a z68 build.
Using gparted, created a partition of identical size starting at identical 2048 on a WD 500GB. Using clonzezilla-20110530-natty running from a cd. Ran clonezilla with device-device, expert mode, part_to_local_part, source SSD, target 500GB, parameters -j2 and -k. Clone seems to work okay but will not boot from cloned drive. Just blank screen with no messages, after usual bios messages.
Also tried with parameters -e1 auto -e2 -j2 and -k but same result. Read about -t1 parameter on another post but that option not listed when i run clonezilla.
I read the -j2 clones hidden data between the MBR and the 1st partition. Is there an option to clone the MBR and make it boot or am i missing something else? Thanks in advance for your help.
Preferably, i don't want to destroy the partition table on the target drive.
Not sure if it's the same issue as
https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/4589758
Maybe you can give Clonezilla live 1.2.9-19 or 20110721-natty a try.
//NOTE// Backup important data before you use Clonezilla. Just in case.
Steven.
Just tried 1.2.9-19-amd64.iso and clonezilla hangs at "Calculating bitmap… Please wait…"
Target drive is a 500GB Western Digital model WD5000AAKX
Which file system did you save? How about giving i686-pae version a try?
Does anybody on this forum has same issue?
Steven.
Finally had a chance to try again. Used version clonezilla-live-1.2.10-5-i686-pae.iso with options -e1 -e2 -j2 -k
Clonezilla executed okay but target drive will not boot.
Windows boot manager screen with windows failed to start message.
A recent hardware or software change might be the cause.
windows\system32\winload.exe status 0xc000000e selected entry missing or corrupt.
Both target and source are NTFS
"A recent hardware or software change might be the cause." -> Did you restore the image to the same hardware?
Steven.
Identical hardware, same pc. Just cloning to a new drive to free up the SSD. After the clone, the ssd is disconnected but the cloned drive won't boot. Absolutely no, none, nada changes to anything else in the pc.
MS Windows detects the hardware has been changed, and maybe the new hardware need some specific drivers which do not exist in the OS you have cloned.
You can try to have sysprep installed before you cloned. Maybe that will help.
Steven.
Nothing to do with hardware drivers or hardware change! Connected new drive as secondary and it uses the same drivers: disk.sys and partmgr.sys date 2006-06-21 version 6.0.6002.18005
With same source and target drives, did a disk to disk clone with options -e1 auto -e2 -j2 and use partition from source.
Target drive boots and works perfectly! Used 1.2.10-5i686-pae.iso
So the local partition to local partition clone likely still requires further improvements.
"With same source and target drives, did a disk to disk clone with options -e1 auto -e2 -j2 and use partition from source." -> By default, if you do disk-to-disk clone in Clonezilla live, yes, the options are "-e1 auto -e2 -j2"… Did you mean you have to tune something more? Or?
Steven.