I've been attempting a disk to disk clone using Clonezilla live off a usb thumb drive to copy my 80GB dual-boot PATA HDD to a new unformatted 115GB SATA SDD. I've carefully followed the basic step-by-step instructions, but the backup never starts. I get to the screen that says "Calculating Bitmap… Please Wait…" I've waited 8hrs, stopped it, ran it again, and waited 32 hours, but it never progresses. Am I doing something wrong? Is there some combination here that is not supported?
My plan is to try the advanced options. I'd like to use the -r -k1 options to try to ("proportionally"?) increase the partition size anyways.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there,
i have the exact same problem… I need to clone a windows 7 partition, disk to local disk, 250 GB to 500 GB. I am stuck at calculating bitmap, the remaining time keeps switching randomly between 0:0:0 and 30:00:00 or so…
i have tried beginner and expert settings, no difference… those are SATA disks…
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i now did it quick and dirty, i copied the partition using gparted and then rebuild the bootmanger using the repair environment provided by windows 7 setup…
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to eliminate potential issues in my setup, so it would be nice to compare systems. You said both of your drives are SATA, right? Is your target drive a SSD? Are you trying to clone a dual boot system? I have GRUB as the bootloader for the source drive with a Windows XP partition and an old Fedora Core 3 (or 4?) partition.
I don't know if clonezilla is actually doing anything, but last time I ran it, it looked like the target device had been written to from a previous attempt. I think it had the partitions set up properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes both drives are SATA, both are normal, good old HDD… The system I was attempting to clone was a Windows 7 Professional, without any other OS installed. The boot manager was the one from windows (standard windows installation, nothing added or modified, one partition). It is a 64 Bit System, don't know if that matters.
Clonezilla did something to the target drive. There where 2 100 MB partitions located on the target drive (GParted told me so)… i did several attempts, so i guess the second one was from one of those attempts. But, as I understand it, this Bootpartition gets written before the bitmap gets calculated. At least the questions that are being asked sound like that…
in short:
from 250 GB SATA HDD with windows 7 prof x64 (one partition + the 100MB "windows Boot partiton")
to 500 GB SATA HDD empty (no partition)
-> disk to local disk
-> stuck at calculating bitmap
I was using the latest live CD bootet to RAM, the machine is some cheap Asrock Mainboard with an old Core2duo (i think an E6400@2,13 GHz)
i hope you can get some information out of this :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran into this problem just today on a similar system. I was using the 64-bit build of the latest Clonezilla live cd. I ended up downloading the i686 version and it worked with no problem. Hope that works for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can confirm that I encountered the same problem using the 1.2.8-23 AMD64 iso. The copying process stalled at calculating bitmap. I only waited about 15 minutes, however.
Switching to the i686 version blew right through the calculating bitmap stage in a second or so.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
160GB SATA Hitachi Drive
to
320GB USB Generic Drive
I'm also booting CloneZilla from GRUB2 ISO Loading. I moved back one version and this problem disappeared. This seems to be an issue with the 1.2.8-23 release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran into the same issue with 1.2.8-42 on a Win7-64 host using vbox with the clonezilla set mounted. I attempted to clone an xp32bit harddrive from 15gb disk to a new 35gb disk - retrying with older copy of 686
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-05-17
Same issue trying to clone from a 128Gb SSD to 250Gb HD on a brand new HP notebook
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried this too last night. OCZ Vertex to OCZ revodrive. I gave up after a couple hours and hit CTRL+ALT+DLT
After it reboot I decided to just copy my boot drive as an image to another hdd I had. It finished and restarted and not windows won't boot. Startup repair wizard fails to fix the issue and it's in a restart loop now. This is pretty fucking shitty. Why the fuck would a software like this WRITE anything to the goddamn source drive?
(both formatted ntfs, using amd64 version on a 4 core phenom 2 with an msi motherboard)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
you can not just clone the win7 partition, you have to setup the boot manager too….
insert win7 disk, instead of "install now" klick on repair system or smth like that…
get the console open and type
bootrec /mbr
bootrec /fixboot
bootrec /rebuildBcd
then reboot and use the automatic repair function…. the automatic repair function needs 2-3 reboots. should work then… for more info just search the internet for rebuild win7 bootmanager..
Or just use the x86 version of clonezilla. i do not think clonezille has written to the source disk o0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the source drive is the one that will not boot now. It booted before. It seems impossible to me that this would occur if NOTHING had been written to it. I will try what you suggest. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've manually cloned about 30 out of 60 hard disks now and have had no issues like this. Is it possible you did not shut down Clonezilla properly after the cloning? There's a warning about disks not booting properly if you don't do that. Also, please don't complain about free/open source software. Clonezilla really is an awesome cloning tool and has saved me and my company lots of time and money.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I did the 3 steps above, the 3rd step said "number of windows installations identified: 0" and then terminated.
startup repair still says "startup repair cannot repair this computer automatically." I really don't think it has anything to do with the MBR because when attempting normal startup the windows logo appears as normal with the 4 colored blobs flying in and making the windows logo, but after that it goes to the blue screen with white letters for a split second before rebooting.
And yes, this software isn't Beta, so I'll complain about it fucking over my system all I want thank you very much.
It's very poor that software that is only supposed to read data on one end somehow corrupted my boot (source) disc.
And, yes again, the usual kill processes and such that linux does on restart did happen each time I restarted.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I might also add that the startup repair tools log says that there are 1 root causes : "unspecified changes to system configuration might have caused the problem." there are also a lot of error code 0x0 s
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been attempting a disk to disk clone using Clonezilla live off a usb thumb drive to copy my 80GB dual-boot PATA HDD to a new unformatted 115GB SATA SDD. I've carefully followed the basic step-by-step instructions, but the backup never starts. I get to the screen that says "Calculating Bitmap… Please Wait…" I've waited 8hrs, stopped it, ran it again, and waited 32 hours, but it never progresses. Am I doing something wrong? Is there some combination here that is not supported?
My plan is to try the advanced options. I'd like to use the -r -k1 options to try to ("proportionally"?) increase the partition size anyways.
I've also tried it with a dvd, but I have the same problem.
Hi there,
i have the exact same problem… I need to clone a windows 7 partition, disk to local disk, 250 GB to 500 GB. I am stuck at calculating bitmap, the remaining time keeps switching randomly between 0:0:0 and 30:00:00 or so…
i have tried beginner and expert settings, no difference… those are SATA disks…
can' find the edit button:
i now did it quick and dirty, i copied the partition using gparted and then rebuild the bootmanger using the repair environment provided by windows 7 setup…
Hey mrxls,
I'm trying to eliminate potential issues in my setup, so it would be nice to compare systems. You said both of your drives are SATA, right? Is your target drive a SSD? Are you trying to clone a dual boot system? I have GRUB as the bootloader for the source drive with a Windows XP partition and an old Fedora Core 3 (or 4?) partition.
I don't know if clonezilla is actually doing anything, but last time I ran it, it looked like the target device had been written to from a previous attempt. I think it had the partitions set up properly.
hello thalley,
yes both drives are SATA, both are normal, good old HDD… The system I was attempting to clone was a Windows 7 Professional, without any other OS installed. The boot manager was the one from windows (standard windows installation, nothing added or modified, one partition). It is a 64 Bit System, don't know if that matters.
Clonezilla did something to the target drive. There where 2 100 MB partitions located on the target drive (GParted told me so)… i did several attempts, so i guess the second one was from one of those attempts. But, as I understand it, this Bootpartition gets written before the bitmap gets calculated. At least the questions that are being asked sound like that…
in short:
from 250 GB SATA HDD with windows 7 prof x64 (one partition + the 100MB "windows Boot partiton")
to 500 GB SATA HDD empty (no partition)
-> disk to local disk
-> stuck at calculating bitmap
I was using the latest live CD bootet to RAM, the machine is some cheap Asrock Mainboard with an old Core2duo (i think an E6400@2,13 GHz)
i hope you can get some information out of this :)
Hiya mrxls,
I ran into this problem just today on a similar system. I was using the 64-bit build of the latest Clonezilla live cd. I ended up downloading the i686 version and it worked with no problem. Hope that works for you.
hi rob,
good to know…. the next time i have to clone a drive i will keep this in mind! Thanks for the info!
Thalley,
Could you please confirm that the issue exists on amd64 version of Clonezilla live?
Thanks.
Steven.
I can confirm that I encountered the same problem using the 1.2.8-23 AMD64 iso. The copying process stalled at calculating bitmap. I only waited about 15 minutes, however.
Switching to the i686 version blew right through the calculating bitmap stage in a second or so.
I am having the same problem as I am typing this. Just wanted to confirm.
I am reporting the same issue here
160GB SATA Hitachi Drive
to
320GB USB Generic Drive
I'm also booting CloneZilla from GRUB2 ISO Loading. I moved back one version and this problem disappeared. This seems to be an issue with the 1.2.8-23 release.
…also:
I am dual booting Ubuntu 10.10 and Windows 7 x64.
The ISO was the AMD64 version.
Is there anything different for Clonezilla live 1.2.8-42 amd64 version?
Could you please give that a try?
Thanks.
Steven.
I ran into the same issue with 1.2.8-42 on a Win7-64 host using vbox with the clonezilla set mounted. I attempted to clone an xp32bit harddrive from 15gb disk to a new 35gb disk - retrying with older copy of 686
Same issue trying to clone from a 128Gb SSD to 250Gb HD on a brand new HP notebook
Guys,
Could you please confirm that the file system you have problem is NTFS? Or any other file system?
Thanks.
Steven.
My problem was with ntfs
Please give Clonezilla live 1.2.8-43 amd64 version a try. It has been uploaded to testing branch.
Please let us know the results.
Thanks.
Steven.t
I tried this too last night. OCZ Vertex to OCZ revodrive. I gave up after a couple hours and hit CTRL+ALT+DLT
After it reboot I decided to just copy my boot drive as an image to another hdd I had. It finished and restarted and not windows won't boot. Startup repair wizard fails to fix the issue and it's in a restart loop now. This is pretty fucking shitty. Why the fuck would a software like this WRITE anything to the goddamn source drive?
(both formatted ntfs, using amd64 version on a 4 core phenom 2 with an msi motherboard)
you can not just clone the win7 partition, you have to setup the boot manager too….
insert win7 disk, instead of "install now" klick on repair system or smth like that…
get the console open and type
bootrec /mbr
bootrec /fixboot
bootrec /rebuildBcd
then reboot and use the automatic repair function…. the automatic repair function needs 2-3 reboots. should work then… for more info just search the internet for rebuild win7 bootmanager..
Or just use the x86 version of clonezilla. i do not think clonezille has written to the source disk o0
the source drive is the one that will not boot now. It booted before. It seems impossible to me that this would occur if NOTHING had been written to it. I will try what you suggest. Thanks.
I've manually cloned about 30 out of 60 hard disks now and have had no issues like this. Is it possible you did not shut down Clonezilla properly after the cloning? There's a warning about disks not booting properly if you don't do that. Also, please don't complain about free/open source software. Clonezilla really is an awesome cloning tool and has saved me and my company lots of time and money.
So I did the 3 steps above, the 3rd step said "number of windows installations identified: 0" and then terminated.
startup repair still says "startup repair cannot repair this computer automatically." I really don't think it has anything to do with the MBR because when attempting normal startup the windows logo appears as normal with the 4 colored blobs flying in and making the windows logo, but after that it goes to the blue screen with white letters for a split second before rebooting.
And yes, this software isn't Beta, so I'll complain about it fucking over my system all I want thank you very much.
It's very poor that software that is only supposed to read data on one end somehow corrupted my boot (source) disc.
And, yes again, the usual kill processes and such that linux does on restart did happen each time I restarted.
I might also add that the startup repair tools log says that there are 1 root causes : "unspecified changes to system configuration might have caused the problem." there are also a lot of error code 0x0 s