Clonezilla Live Cd Iso Download
Olegario Benford
I have been working on a way of allowing us to image new PCs, to avoid having individually remove all the bundled software and install the Windows Updates. I have it all working and now I want to try and make it as usable as possible.
Currently I am using two USB drives when imaging a PC. I have bootable Clonezilla on one USB drive which the PC boots to and runs Clonezilla. Then when I run Clonezilla Live, I connect a second USB drive which stores the image.
When I created the bootable Clonezilla USB drive, I noticed that it did not wipe the files I had stored on the drive. I was wondering is it possible to create the bootable clonezilla USB drive, and then copy the image file on to the same USB drive.. Then use this single drive for imaging? Is there any reason why I should not do this?
Okay, I've bought a 64Gb USB drive with the hope of putting both the image and the bootable Clonezilla software on the same drive. I used Rufus (ISO to USB tool) to put the Bootable DRBL Live / Clonezilla on this USB drive... this process completed successfully, and I then created an images folder on the USB drive, and copied my image to this drive.
With my new PC, I booted to the USB drive and successfully loaded the DRBL Live. When I got to the desktop graphical interface, I double clicked on Clonezilla Live. Everything goes fine until the point at which you have to Mount CloneZilla Image Directory.. I choose "local_dev use local device (E.g.: hard drive, USB drive)"... It then says:
"If you want to use USB device as a Clonezilla image repository, please
Insert USB device into this machine now
Wait about 5 secs
* Press Enter Key
so that the OS can detect the USB device and later we can mount it as /home/partimage."
I click Enter and it then proceeds to list ONLY the partitions on the hard drive (that I am re-imaging) but NOT the USB drive partition.. When I open GParted, the USB Drive is listed as /dev/sdb but has a locked symbol beside it... It seems as if the partition that I am booting from is locked, making it unavailable as the partition which houses the Clonezilla image. Is there any way that I can get around this?
Clonezilla Live is a small bootable GNU/Linux distribution for x86/amd64 (x86-64) based computers. Clonezilla SE (Server Edition) has been developed from 2004, and it is used to deploy many computers simultaneously. It is an extremely useful tool, however, it does have several limitations. In order to use it, you must first prepare a DRBL server AND the machine to be deployed must boot from a network (e.g. PXE/iPXE).
To address these limitations, we have combined Debian Live with Clonezilla as "Clonezilla Live," a software that can be used to easily image and clone individual machines. The primary benefit of Clonezilla Live is that it eliminates the need to set up a DRBL server ahead of time and the need for the computer being deployed to boot from a network. Clonezilla Live can be used to image or clone individual computers using a CD/DVD or USB flash drive. Though the image size is limited by the boot media's storage capacity, this problem can be eliminated by using a network filesystem such as sshfs or samba.
2. How to install Clonezilla Live ? To install Clonezilla live, the basic steps are to download pre-build Clonezilla Live then put it in a boot media (CD, USB flash drive or USB hard drive). Two types of files are available, iso and zip. The former one is for CD, the latter is for USB flash drive. Besides, you can put Clonezilla live on hard drive or PXE server, too.
- For CD/DVD:
- Download an ISO file for CD/DVD. Then you can burn the iso file to a CD/DVD with any burnning program, such K3b on GNU/Linux or cdrtfe on MS Windows, and remeber to choose "Burn Image" to burn the ISO file on the CD. The CD can then be used to boot the machine you want to image or clone. The step-by-step doc about using InfraRecorder to create Clonezilla live CD could be found here.
- For USB flash drive or USB hard drive:
- To put Clonezilla live on a USB flash drive or USB hard drive, check this doc.
- For hard drive:
- To put Clonezilla live on a harddrive with OS installed already, check this doc.
- For PXE server:
- To put Clonezilla live on a PXE server and boot your client via PXE, check this doc.
For better security, it is recommended to change the passwords of user and root by command "passwd" before you allow remote access. When Clonezilla live boots, the ssh service is NOT automatically started, and the setting in /etc/hosts.deny does NOT block any connection. If you want to remotely ssh login into your Clonezilla live, you have to start ssh service by "service ssh start".
5. Advanced modes Some advanced modes are available:
- Create your own recovery CD or USB flash drive.
- Use your own script and run it on clonezilla live.
- Use boot parameters to pre-set some selections
- The reserved image and device names for the command ocs-sr
If you want to customize the Clonezilla live by assigning the boot parameters and make it automatically configure for you, you can check:
-live-doc-content.php?topic=clonezilla-live/doc/05_Preseed_options_to_do_job_after_booting
I assume thats done within a terminal when it says "Enter_shell". So my friend has to do that on her laptop.
As for dealing with ssh I have to admit Ive never had used that in the past and consequently know next to nothing about it.
So Ill have to do some reading up on that topic first.
After you login, you can run:
sudo clonezilla
Then it will enter the TUI mode. Just like you boot Clonezilla live in the local machine.
I suggest you use screen or tmux before you run the "sudo clonezilla". If you are not familiar with that, please google how to use it. It's very important when you remotely login a machine and run the job in a certain of time.
It works. Thats really great. :)
Well, tmux isnt installed by default as it seems but screen definitively is.
So I start screen and after seeing a bit of introductory text Im in the screen session.
After that I startedsudo clonezilla and I enetred the TUI mode.
Tmux is included in Clonezilla live. Any error message you had when you started it?
However, personally I like screen more, so most of the time I use screen.
Yes, the way you use screen is correct.
It's nice to know now things work there. Enjoy Clonezilla.
Is it possible that the fingerprint for the ECDSA key sent by clonezilla may be different each time I try to ssh into it?
When using other VMs (e.g. Debian10 Buster) the key remains the same.
But then: The other VMs are installed whereas clonezilla is a live system...
I've followed the instructions for installing and using Clonezilla, unpacking the .zip file onto my USB "E:" drive running the \utils\win64\syslinux64 -d \syslinux -sfmar E: command, verifying that this copies ldlinux.c32 and ldlinux.sys onto E:\syslinux, then restarting my computer (a Windows 7 laptop), and interrupting the startup to specify the boot device. At that point, I get a DOS-style menu with entries
* ATAPI CD0:* ATA HDD0:* USB HDD:* PCI LAN:
I select the USB HDD: entry and hit , but all that happens is that the selection jumps back to the first entry and then nothing happens. Fortunately, when I select ATA HDD0: (or reboot with interrupting) Windows 7 boots up OK, but unfortunately I'm no closer to backing up my hard drive onto the USB drive.
Chuck, I downloaded Rufus and fired it up, and I have the Rufus 3.10.1647 window open. I see under BOOT SELECTION that it's asking for file (e.g., ubuntu...iso). I don't know what file it's looking for, nor where to get it. I did download CloneZilla itself, but that's a .zip file that I extracted to my USB drive (the volume I want to make bootable), but I don't know if that's relevant? Can you explain further?
Rufus now is working for me, producing a bootable USB drive. It turns out that I had to make one modification to get the drive to boot: I had to change the image mode from ISO to DD. Once I did that, I was able to boot up from the USB drive (after changing the boot order to go to the USB drive first). And then... CloneZilla came up! I started following the instructions there and got to the final (I think...) "are you sure you want to continue (y/n)" BUT then the actual imaging operation failed with an error that the target directory /home/partimag/ was not writable.
When I went into the command line prompt and did ls -al /home/ I saw that the permissions for partimag were root root r-xr-xr-x; indeed not writable, although I noticed another directory /home/user that was (user) writable. I thought maybe I could change the permissions on /home/partimag/ (which would have to be chmod ugo+w) but since my command line session was logged in as user (not root) I couldn't even do the chmod.
You are off to a good start. But it sounds like you are trying to save the image on the same USB drive that you booted with Clonezilla Live. This is possible but not recommended. The best option is to use a small USB boot drive with Clonezilla Live installed (which you have just created) and then use another USB drive to hold the saved image(s).
Chuck, I managed to use Rufus to create a bootable volume containing CloneZilla on an old 16GB memory stick. That booted fine, and once it did, I started CloneZilla; I pulled out the 16GB stick just to make sure I didn't try to write on it. CloneZilla proceeded until the point where I was asked to select the device to mount /home/partimag, I was given three choices:
d3342ee215