Activity for Clonezilla
-
Suncatcher posted a comment on discussion Open Discussion
the versions of clonezilla: drbl: 5.0.0-drbl1 clonezilla: 5.0.1-drbl1 partclone: 0.3.18-drbl1 partimage: 0.6.9-8build1
-
Stefn Vincec posted a comment on discussion Help
Hello, I noticed that the latest version of Clonezilla doesn't detect my LUKS partition. seemingly because of the "-luks no" in the ocs-sr command when I go through the TUI configuration. I am doing a full disk-to-disk clone. I have LVM behind a LUKS partition. Is this intended behaviour? Thanks.
-
wrong forum, oops
-
Hello, I noticed that the latest version of Clonezilla doesn't detect my LUKS partition. seemingly because of the "-luks no" in the ocs-sr command when I go through the TUI configuration. Is this intended behaviour? Thanks.
-
Hello, I noticed that the latest version of Clonezilla doesn't detect my LUKS partition. seemingly because of the "-luks no" in the command when I go through the TUI configuration. Is this intended behaviour? Thanks.
-
Batiste DONDOGLIO modified a comment on discussion Help
Hello Steven, Thank you for your response! I just tried it as ocs_live_run parameters when booting Clonezilla through PXE, and while it didn't produce any error, it didn't name the image correctly. It literally interprets it as is and produces the image with the same name. I will try to use the command line manually and see how it behaves, and report my findings here. In the meantime, here are my command line arguments when using iPXE to boot Clonezilla and saving the image to a NFS share. Please...
-
Juan posted a comment on discussion Open Discussion
Hi everyone, I'm having this issue when restoring a clonzilla image (Windows server 2016). I can restore the image without any problems. However, Windows won't boot. I noticed that at the end of the image recovery, it shows "EFI system partition was NOT found on this hard drive: /dev/sda". The image backup has two disk partions sda and sdb (I could be wrong, not quite sure what sda and sdb are). sdb seems to have all booting data. When clonezilla restores the image it just restores sda. I have restored...
-
Heavyboots posted a comment on discussion Clonezilla live
In the end, the solution has been to wait for Microsoft to update the Surface Pro 9 firmware for anyone else who was struggling with this. I just noticed today that everything is working as expected finally after applying all the latest patches that came up on today's (Aug 2024) Patch Tuesday.
-
dreael posted a comment on discussion Clonezilla live
In the meantime I tested the latest 3.1.3-16 release with LVM. Used test scenario does not use thin pool, i.e. should be compatible with the current Clonezilla release. Result: Several red messages still appears. Details see https://beilagen.dreael.ch/Diverses/KVM2_LVM_ohneThinpool_Clonezilla_aktVers/ First I thought that something could be corrupted on the test LVM so I tested the following long way: Backed up all LVs, then delete everything and then recreating the whole LVM again. Result: https://beilagen.dreael.ch/Diverses/KVM2_LVM_ohneThinpool_Clonezilla_LVM_neu/...
-
@steven_shiau?
-
Scott Brewer posted a comment on discussion Clonezilla live
I would like to know the oder that these are run: IP OCS_Prerun OCS_Repository I already know that OCS_Repository runs after IP, but it would be helpful to know if Prerun runs before or after IP. I am currently using IP and OCS_Repository to assign an IP, and map a network share as the repository. However, the initial attempt at mapping always fails. After waiting a 5-10 seconds, it will start to work. I suspect that this is likely caused by STP/RSTP on the switch, because the link light on the NIC...
-
Malina, Alfred posted a comment on discussion Clonezilla live
Here is a foto of the error message
-
Hello Steven - many thanks for your hint - and sorry that the "formating" of the table was gone after I pressed the send button. I already tried expert mode - with only q1 option selected. but the check was done anyway (kind of strange when sector copy was selectet) and the program aborted as described
-
I get the error in title and this error wording makes absolutely no sense to me. The verbose output before the error Target disk nvme0n1 does not exist in the image saved from disks "" also makes no sense to me. Of course target and source disks are always different, this shouldn't be a problem. When I do checking if the image is restorable it returns successful result, it is restorable. I do restore of disk image to a new disk. Any hints?
-
Afiro Nari posted a comment on discussion Open Discussion
Hi! I have two partitions $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 931.5G 0 disk └─sda1 8:1 0 931.5G 0 part nvme0n1 259:0 0 931.5G 0 disk └─cpart 254:1 0 931.5G 0 crypt I want to copy unencrypted sda1ext4 partition into the LUKS encrypted cpart partition. I tried to run part_to_local_part mode but there was no cpart option but only nvme0n1 in the target list. I chose nvme0n1 option and I wasn't asked for LUKS part open or something like that so I was scared to press ENTER because...
-
vas_smirn81 posted a comment on discussion Help
I used Clonezilla-live- 3.1.3-16-amd64. On my laptop installed two OS: windows 11 and Ubuntu. 1. I created image from partition. As a result my laptop failed to boot. I didn't do restore from image, I just created image from partition. I received this error message when I tried to boot: "verifying shim SBAT data failed: Security policy violation. Something has gone wrong: SBAT self-check failed: Security policy violation." After this error message my laptop switched off. After that I disable Secure...
-
CloneZilla breaks Secure Boot while creating image.
-
Srikanthsivasai Gudavalli posted a comment on discussion Open Discussion
I have single physical disk. I have created 2 LVMs out of this disk. Using 1 LVM, I have created 1 VM with GPT disk format and using the 2nd LVM I have created another VM with MBR disk format. Now I try to create an image of the phisycal disk via clonezilla and clonezilla only detects MBR disk LVM. It never detects GPT disk based LVM at all.
-
Kenneth R. McCormick posted a comment on discussion Clonezilla live
I have had similar problems moving from one disk or even BIOS or CPU type to another, in the past. The issue being in the configuration of the Windows OS for the old hardware, is sometimes amenable to a repair-reinstall of the OS.
-
Apple King posted a comment on discussion Open Discussion
Hi Steven, Just wondering if there is any documentation to make Clonezilla to boot off a partition in a Windows PC? If so can you share it? Trying to do it it for weeks and keep hitting a brick wall. Cheers Apple
-
Steven Shiau posted a comment on discussion Open Discussion
You still can manually run dd to clone the whole disk: https://linuxhint.com/clone-disk-using-dd-linux/ Steven
-
molnart posted a comment on discussion Open Discussion
i would swear i have cloned such drives a few years ago with clonezilla... so what are my options then? any othetr tool i could use to copy the data?
-
Maybe you can try to enter expert mode, and deselect the option "-j2": https://clonezilla.org//clonezilla-live/doc/03_Disk_to_disk_clone/images/ocs-05-b-2-expert-param-extra.png Steven
-
Due to some technical issue, Clonezilla does not support LVM thin provisioning at the moment. Ref: https://github.com/jthornber/thin-provisioning-tools/issues/126 Steven
-
No idea. We do not encounter this issue, and you are the 1st one reporting this. Maybe this is only hardware specific. Have you tried that on different brand/model machine? Steven
-
I am trying to move my Proxmox backup to a larger drive. I have successfully did this in the past via clonezilla, but now I am getting this error: Creating the PV... WARNING: Couldn't find device with uuid 2LN7QE-SVzv-2irJ-1JZ7-fCxB-Sp3n-pLfv8w. Physical volume "/dev/sda3" successfully created. done. Restoring the VG config... Consider using option --force to restore Volume Group pve with thin volumes. Restore failed. I did the backup with dd, hoping that a block-for-block copy would go trought,...
-
Antony Byrom posted a comment on discussion Help
Good Morning, I am really hoping someone can help me with this issue since it is starting to drive me insane. I have a PC that I use to install Linux (Usually Linux Mint) customise the OS & then create Clonezilla backup, and then from that create a restore .iso file which is then sent to the person who wanted it, for them to use Rufus to write to a USB and then load onto a PC. Until recently that was working fine - now nothing has changed with my system, or with the process for creating the images...
-
Guido posted a comment on discussion Clonezilla live
Hi Steven, I was able to fix the problem for clonezilla Version 3.0.0-26. In BIOS, I had to switch the "shared memory" for the integrated graphics to "auto" or "64MB" instead of "128MB". But this doesn't work for the latest version or even 3.1.0-22. Then again, I get the "out of memory" message: Error: out of memory Press any key to continue... No different "shared memory"-settings solves th problem for 3.1.0-22. So, I think it has something to do with the memory of the integrated graphics. But I...
-
Cool. Thanks for clarifying that. Steven
-
Clonezilla released /clonezilla_live_alternative_testing/20240806-noble/clonezilla-live-20240806-noble-amd64.iso
-
-
-
-
When you boot Clonezilla live, apparently you included the image dir from your hard drive? We can see it copied the image files from /img/ to your RAM disk. The image + Clonezilla live >= 4 GB (your RAM size). That's why it failed there. Steven
-
-
-
-
-
-
-
-
Many thanks for your help Regards Alfred
-
Hello Steven Many Thanks for your response Here is the result of the command as you asked for Model ATA ST2000LM015-2E81 (scsi) Disk /dev/sda: 3907029168s Sector size (logical/physical) : 512B/4096B Partition Table: msdos Disk Flags: Number Start End Size Type Filesystem Flags 1 2048s 1050623s 1048576s primary fat32 boot, esp 2 1052670s 3907028991s 3905976322s extended 6 1052672s 3898879999s 3897827328s logical ext4 5 3898880000s 3907028991s 8148992s logical linux-swap(v1) swap
-
Mark Knutson posted a comment on discussion Clonezilla live
Turned out I was using an older version. Once I downloaded and used the newest version, all the problems went away and the clone restored perfectly. Thanks for the help!!
-
Peter Freudenberger posted a comment on discussion Clonezilla live
Hello, We're seeing the following "out of memory" and "kernel panic: system is deadlocked on memory" errors when attempting to restore a 3.1GB compressed disk image to a local disk. Total size when restored to disk is less than 8GB. We are using Clonezilla live version 3.1.3-16 on HP Engage Go 10 and HP Engage Go 13.5 devices. Issue occurs when restoring the image from both local USB-attached storage and network storage. Issue does not occur on the same hardware with 8GB of RAM. Is there anything...
-
Thanks for your feedback. "Ideally, it would be nice to be able to use an underscore if possible, to give the user more flexibility in how they want to name their images. " -> Well, basically we separate the words by "-". If "_" mixes with "-", it won't be easy to parse that. That's why. Steven
-
Have you tried the latest one, i.e., Clonezilla live 3.1.3-16? "When I use this setting with 3.0.0-26 or above, it doesn#T work and I got an "out of memory"-Error." -> Please take a photo about the error messages on the screen then post it. Thanks. Steven
-
Edit: From the command line, it indeed works properly, but only if I use a dash instead of an underscore as follows: autoname-SRV-ZBX-datefmt_%d%m%Y -> Gives: SRV-ZBX-06082024 But this doesn't work and results in the issue stated in my previous post: autoname-SRV-ZBX_datefmt_%d%m%Y -> Gives SRV-ZBX_%d%m%Y (literally) Expected: SRV-ZBX_06082024 Ideally, it would be nice to be able to use an underscore if possible, to give the user more flexibility in how they want to name their images. Thank you for...
-
Hello Steven, the machine is an ASRock N100DC-Board (Intel N100 CPU) with 16GB of Ram. The ISO-Image boots from an USB-Stick on this machine without any problem.
-
Hello Steven, Thank you for your response! I just tried it as ocs_live_run parameters when booting Clonezilla through PXE, and while it didn't produce any error, it didn't name the image correctly. It literally interprets it as is and produces the image with the same name. I will try to use the command line manually and see how it behaves, and report my findings here. In the meantime, here are my command line arguments when using iPXE to boot Clonezilla and saving the image to a NFS share. Please...
-
Thanks for your feedback. My bad. Now I know the issue you have. Those reserved image is only used in the command line prompt. Hence you should use it in the green command here: https://clonezilla.org//clonezilla-live/doc/01_Save_disk_image/images/ocs-10-8-img-save-command-prompt.png We will try to extend that to the TUI in the future release. Steven
-
What's the RAM size of your machine? Is this issue reproducible on the machine with larger RAM? Say >=2 GB RAM? Steven
-
Do you have any images in /home/partimag/? Please boot clonezilla live, mount the image repository, and enter command line prompt, then run: 1. mount 2. tree -h /home/partimag/ Please post the results of (1) & (2). Thanks. Steven
-
Please boot Clonezilla live 3.1.3-16-amd64, and enter command line prompt, then run: 1. sudo -i 2. parted -s /dev/sdx unit s print (Replace sdx with your source disk) Please post the results of (2). Thanks. Steven
-
Bump
-
Hello everyone, since clonezilla_3.0.0-26, I'm not able to boot the iso in grub2. The last "clonezilla_2.8.1-12" was workiung perfectly- Here my working setting in "/etc/grub.d/40-custom" with 2.8.1-12: menuentry "clonezilla-live_2.8.1-12" { ISO="/clonezilla-live-2.8.1-12-amd64.iso" search --set -f $ISO loopback loop $ISO linux (loop)/live/vmlinuz boot=live union=overlay username=user config components toram=filesystem.squashfs quiet noswap edd=on nomodeset locales> initrd (loop)/live/initrd.img...
-
Hello everyone, since clonezilla_3.0.0-26, I'm not able to boot the iso in grub2. The last "clonezilla_2.8.1-12" was workiung perfectly- Here my working setting in "/etc/grub.d/40-custom" with 2.8.1-12: menuentry "clonezilla-live_2.8.1-12" { ISO="/home/guido/ISOs/clonezilla-live-2.8.1-12-amd64.iso" search --set -f $ISO loopback loop $ISO linux (loop)/live/vmlinuz boot=live union=overlay username=user config components toram=filesystem.squashfs quiet noswap edd=on nomodeset locales> initrd (loop)/live/initrd.img...
-
When booting off the Clonezilla live there is no option to restore. Only to save. As shown by the screen shot, so how do you restore the cloned image?
-
Hello - I am trying to clone my Ubuntu drive for backup reasons Clonezilla (versions 3.1.3.16-amd64 and 20240630-nobel-amd64) abort with the following information " the hidden space between MBR and 1st partition is -1 sectors which is smaller than the hidden data size 2047 sectors unable to find target partition sdc1" sdc is my original hard disk - i tried to copy sector by sector - by activating q1 option only - but this also failed with above failure - GParted does not show any failure on this...
-
Cool. Thanks for confirming that. Steven
-
Russ Kubes posted a comment on discussion Clonezilla live
I apologize for the delay, it took me some time to get to a position to test this again. By the time I tested, I saw 3.1.3-16 was already available as 'stable'. I tried with that version and no longer have this issue. It seems to be resolved now. Thanks!
-
The one you are you are using is clonezilla-live-20170626-zesty-amd64? It was released more than 7 years ago... Please give the latest Clonezilla live a try, either 3.1.3--22 or 20240715-noble: https://clonezilla.org/downloads.php Steven
-
MS Windows is a black box, so it's complicated to us. In your case, if the restored OS on the destination machine can boot, you can reset MS Windows' serial number. If it does not boot, I would suggest you reinstall it. It will be easier. Yes, switch to GNU/Linux would be a better solution if GNU/Linux works for you. Steven
-
ernesto coatimundi posted a comment on discussion Clonezilla live
I tried SYSPREP on a pc with just a few apps and it was not a good experience, First it complained about failing to validate Windows installation which is a misnomer as it reads. Using more searches with help from one website I found how to read the log file, which implicated some exotic printer app was holding things up. Attempts to fix using powershell failed so I simply uninstalled the app and sysprep worked. On reboot the pc was itself completely OOBEd (out of the box experience) I don't know...
-
After a lot more looking I found some answers but still it is surprising there aren't dozens of the usual youtube videos on using cloning with sysprep for moving to a new machine seamlessly once an old one is used up. The answers to my questions above: 1. It should work reasonably well in principle, but the details of each hardware can make trouble 2. here are a couple of websites that give semi-useful answers: https://www.youtube.com/watch?v=hF5TNvgFoGk and https://community.spiceworks.com/t/create-an-image-using-clonezilla/1005458...
-
Romario posted a comment on discussion Clonezilla live
Hello Steven! I make image of my PC (UEFI GPT Linux) with clonezilla-live-20170626-zesty-amd64 (Newest versions want boot) disk to image menu. I want restore image to other same PC (image to disk), but see error messages on the screen - grub2-install error!! see photo
-
I found time to play with clonezilla and made images of my pc's as back up. But my biggest worry is when the mission critical pc completely fails (e.g. due to windows updates) and I would want to buy a new pc (incl its own windows license and device drivers) if I restore the image, it will overwrite the new pc's windows and drivers. According to the conversation above I understood that if I run SYSPREP then boot to clonsezilla and make the image the usual way this time, I will get an image I might...
-
It looks like the cloned OS is looking for a device with some specific disk ID? To me it seems the disk ID is related to hardware. Basically they won't be the same. The destination machine has its own disk ID and it is definitely different from the source one. Therefore in the future, before you clone it, I suggest you modify that so that it won't be hardware related. By doing this, the cloned OS should be able to boot in the destination machine. Steven
-
Please describe your issue/question in detail so that we can do something for you. You should mention all the steps you have done, and the issue when it does not what you expect, etc. Steven
-
No idea. It never happens to us. Steven
-
Thanks. The dialog in GNU/Linux command line/text mode has space limitation. Hence we can not put too long sentence. We will try to explain more in the future if we find some better description. Steven
-
Thanks for your feedback. Actually if you read it carefully, it says: "so that we can read or save the image in /home/partimag/" in the 1st line. That's the reason why we need to mount /home/partimag/. Steven
-
FERFAIL TXZ posted a comment on discussion Help
So uh... I need the PC so I did a fresh install in the cloned drive...
-
So I have two drives connected in the same PC. One of them has Fedora in it and the other was empty. I followed these instructions step by step and everything worked fine. After the cloning, I selected the "Shut Down" option, then disconected the source drive (the one that has Fedora in it), I left the drive where Fedora were cloned and I started my PC. The GRUB screen appears as normal, but after starting Fedora, the loading screen appears (where the Fedora logo in the bottom and the snipping circle...
-
BEEB posted a comment on discussion Help
well i need it to restore the image on /dev/nvme0n1p3
1 >