Clonezilla Download 32bit |BEST|
Alfonsa Pan
To download Clonezilla live, select the following CPU architecture and file type, then click the download button:
Release branch: stable,Clonezilla live version: 3.1.1-271. Select CPU architecture:amd64i686-paei686
2. Select file type:zipiso
.clonezilla_footer width: 320px; height: 100px; @media(min-width: 500px) .clonezilla_footer width: 468px; height: 60px; @media(min-width: 800px) .clonezilla_footer width: 728px; height: 90px; (adsbygoogle = window.adsbygoogle []).push();
Notes
- Ubuntu 19.10 (Eoan Ermine) has dropped the support for i386 architecture. Therefore we do not release i386 Ubuntu-based Clonezilla live for Ubuntu >= 19.10, only amd64 (x86-64) arch is available.
- Once you have the Clonezilla live iso or zip file, please follow this Live CD/USB doc to put it on the boot media, and follow this Live Docs to use it.
- For Ubuntu-based branch, i.e. alternative stable and alternative testing ones, 2 CPU architectures are available:
- amd64, for use on PCs with AMD64 or Intel 64 processors. It supports multi-core processor, and multiprocessor.
- i686, general purpose for 386 CPU. It supports multi-core processor, and multiprocessor. PAE (Physical Address Extension) is supported.
- For Debian-based branch, i.e. stable and testing ones, 3 CPU architectures are available:
- amd64, for use on PCs with AMD64 or Intel 64 processors. It supports multi-core precessor, and multiprocessor.
- i686-pae, optimized for i686 CPU supporting PAE. It supports multi-core processor, and multiprocessor.
- i686, general purpose for 686 CPU. It supports one or more processors not supporting PAE.
For more info, please check this Q&A.
[Back to download top]
- ISO file is for CD/DVD.
- Zip file is for USB flash drive or USB hard drive Check here for how to put on the boot media.
[Back to download top]
Hi
I've only just started to use Clonezilla and I've run into this error:"/home/partimag is full"
I've had a search of other related posts but none seem very close to my environment, which is:
- Windows 7 32bit Versa Pro laptop (Japanese)
- Virtualbox Version 5.1.8 r111374 (Qt5.5.1) with a CentOS 7 VM running in it (HDD 20GB)
- clonezilla-live-20170905-zesty-i386.iso
- backup method: device-image
- Mount clonezilla image directory: samba-server (local win share)
I'm trying to backup the CentOS VM into a shared windows folder.
Clonezilla manages to write 110MB into the shared folder before the error appears.
Checking df -a inside the VM running Clonezilla shows that %use is 39%, and that there is 278GB available.
Any pointers to what I'm doing wrong would be gratefully received.
Thanks
lowerhash
I want to clone both OS with clonezilla live, but in the Clonezilla-live page appears me different download options, and I dont know what of all options are correct and make a right choice for optimal cloning of these operating systems, the options to appears me in the download clonezilla-live page, are these:
Since you have a system that supports 64 Bit you can use the clonezilla-live-2.1.1-7-amd64.iso version. You can also use the i686-pae but it is better to use a 64 Bit version of a 64 Bit supported hardware.
Thanks for the reply - just got back to this now.
on the original drive, both shown kernels boot: on the cloned drive neither work.
2.6.32-504.8.1.e16.i686 and 2.6.32-642.6.2.e16.i686. I did use the 32 bit clonezilla live.
any thoughts?
I do not see those options listed on the page ( =stable ). I see "i686-pae", "amd64", and "i586". Browsing the files directory on the download site ( _live_stable/2.3.1-18/ ) I do not see an i386 iso available for the stable release, but there is one under the alternative release ( _live_alternative/20141208-utopic/ ). Far as I can tell any of these ISOs should work, but because some are designed for single cores they will be potentially slower. AMD64 sounds like the best option for your computer because you have a 64bit cpu. i386, i586, and i686 are all 32bit. If you wish to go 32bit in case you ever need the iso for use on other computers then i386 would be the best because it provides the widest range of cpu compatibility.
1. In terminal type "cd /home/YOURUSERNAMEGOESHERE/Downloads". You will need to adjust this path to that of where you saved the ISO file.
2. In terminal type "md5sum *.iso". This will calculate md5sums for all isos in that directory. Alternatively you can type "md5sum theexactfilename.iso". Replace "theexactfilename" with the filename. This will just calculate the md5sum of the specified file.
3. Compare the md5sum of the clonezilla ISO to that of the one listed on the clonezilla website ( ).
I read some on this at that site, and looked at the table which shows the differences: -print.php?path=./2_System/57_why_ubuntu_based_clonezilla_live.faq#57_why_ubuntu_based_clonezilla_live.faq
I tried Clonezilla Live clonezilla-live-2.8.0-27-i686.iso, a Linux Live CD that images hard drives to a network location (kind of a Linux version of Norton Ghost). But it kept locking up in the middle of the transfer. Felt very unreliable.
i've built z16 lite with some customization and i used clonezilla to clone that to a usb drive so i can copy to my fleet of computers. i'm having no trouble doing this. it's been smooth cloning from the computer to the usb drive and from the usb drive to the computer. i've tested on a handful of computers and no issues with this part of the process. but i ran into a problem when i tried to boot into my live usb clone of z16 lite to run updates and make a few changes on one of the computers i had upgraded to z16 lite from z15.3 lite. and i've been running this process with 15.3 lite for a few years and never had this issue.
i've been doing the clone process with clonezilla on zorin 15 lite for many years, but also a few different versions of ubuntu and other versions for years before that. i've never had this problem of not being able to boot into my live cloned os from the computer boot menu... unless it was a bad drive or bad usb port or a bad .iso. and all of those things i have verified are working fine in these tests. i've completely isolated this issue to be related to z16 lite installed on my computers, whether it's my cloned z16 or a clean copy of z16 installed.
os-prober is probing:
/dev/sda2:Zorin OS 16 (16)linux
so the os is readable on the usb stick. but i have really gotten into the weeds in this one. i adjusted a setting in the grub file so i would get time to hit the option to go into the uefi on the grub menu on my xubuntu 20 test live os usb and and when i hit sudo update-grub now that doesn't let me see my live usb os anymore. still can boot into clonezilla and the os installer usb, but not the live os that i made in clonezilla. and i thought clonezilla might be an issue. so i tried the newest version. same thing. then i tried the version that i use without fail in the z15 lite system and nothing was able to bring back booting to live usb. i've been all through the bios/uefi menu, resetting to defaults and trying it. making a few changes that i had before and trying it. nothing. i don't know if once i hit update grub if it went from something more stable i was using to the v2.04, which z16 lite uses. i checked the version on xubuntu and it was v2.04 but i just don't know if that's what it started at when it was working. i have to go back and do a clean install and see what version it starts with. same with z15 lite. after doing the same to my z16 lite grub - changing to show the menu - once i hit update grub, now the computer with z16 on it can't see any live os usb drive. but will see the clonezilla and the usb installer. i've totally made things worse.
5 sticks. 2 usb ports. 4 different computers. probably 20 wipes and start overs from the usb installer. i haven't tried ventoy. but i'll look into that. clonezilla has been reliable for years. and the usb that i'm making in clonezilla can be cloned on to the computer. the problem is if i want to just boot into the live usb os (to do updates or make a tweak), which i've done for years - that's what it's not letting me do anymore. it's not showing up in the bios/uefi menu. so what ventoy does, i'm able to do with clonezilla - make the bootable drive. it's just that drive isn't being seen in bios/uefi anymore but all other usb drives are - clonezilla, usb installer. i'll try ventoy as a test is and see if that makes a difference.
looking at ventoy - i don't make iso clone. i clone the computer to the usb with clonezilla in the middle, so the usb stick is ready to go right after the clone. based on the ventoy documentation, that's what it looks like ventoy does. it's more like balena etcher than clonezilla. i use balena etcher to make the usb installer from the zorin iso. but i take my best computer build and then boot into the live clonezilla usb drive and then clone computer to usb. then on the other side, i clone usb to computer to make the cloned computer. all of this is working. it's just not being recognized
f5d0e4f075