Hi Chuck, Thank you very much for taking the time to give such helpful and detailed advice. Ed
Hello, I need quick help. I need to make a copy of the entire image of a 128GB SSD drive encrypted with BitLocker from Windows 10. After selecting expert mode, it asks for my BitLocker password, and even though I'm 100% sure it's correct, it won't accept it, giving me the message in the attachment. By the way, there's no way to exit back to the main menu, and then I have to restart Clonozilla. However, as a test, I managed to make a copy of a pendrive image with BitLocker on the same hardware, password,...
Request : Unlock LUKS2 partitions to be used as image repository folders, and enable selecting them in the local devices.
Delete this i make new one
Request : Unlock LUKS2 partitions to be used as image repository folders, and enable selecting them in the local devices.
Request : Unlock LUKS2 partitions to be used as the image repository folders, and enable selecting them in the local devices.
Unlock LUKS2 partitions to be used as the image repository folders, and enable selecting them in the local devices.
Unlock (and use) the LUKS2 partition which the img file will be saved into.
Unlock and use the LUKS2 partition which the img file will be saved into.
Unlock the LUKS2 partition which the img file will be saved into.
Hi Ed New computers with NVMe M.2 drives are usually configured from the factory with the BIOS UEFI set to RAID mode. This usually requires a proprietary driver to read the data from the drive. The RAID driver configuration mode has many names, it may be listed as RAID, VMD, RST or other. Clonezilla may not include a RAID driver that can read your data in RAID mode. This is why you may need to switch to ACHI driver mode. Just change the BIOS UEFI driver mode to ACHI mode and then Clonezilla can read...
Hi Chuck, thanks again for your help, again it has solved a problem for me. I was having trouble booting after changing the RAID setting to AHCI, and I hadn't worked out that that was the reason, I was at a loss so thank you very much. Do you know why it has to be in the RAID setting to boot? Would you be able to explain it or point me towards a link that elaborates on this as I have never encountered it before and would like to understand as I use Clonezilla so much. If I reinstall the OS will I...
Tested with "clonezilla-live-20260705-stonking-amd64", and I can confirm that the issue has been fixed. This means that clonezilla now reports a correct (failed) result when interrupting ntfsclone.
Please give testing Clonezilla live >= 3.3.3-15 or 20260705-* a try: https://clonezilla.org/downloads.php This issue should have been fixed. Let us know the results if you test it. Thanks.
If Clonezilla live 20260525-resolute works for you, then the culprit should be on the Linux kernel which might be too new and buggy for your hardware. At least now you have a working version. We will keep updating the Linux kernel so maybe in the future the bug will be gone and it will work for your hardware.
Thank's again for your patience. In fact, I was able to boot with the alternate clonezilla-live-20260525-resolute-amd64.iso without an issue. That's odd. Anyway, I'll try to use the alternate from now on (at least with Hyper-V) and see what happens. If you have the time and wish to view the error happening attached is the exported Hyper-V VM.
OK, great. Thanks for sharing that.
i have changed vmlinuz and initrd.img with new versions and it worked ! thank you :)
If what you want to use DRBL is for Clonezilla purppse, maybe you can try this mode: https://clonezilla.org/clonezilla-SE/use_clonezilla_live_in_drbl.php IIRC, we have forced to add the USB NIC driver in the initrd. It should work for your case. How about giving that method a try?
Some methods you can try: Change the layout of your VM, i.e., try to tune different settings for your machine. Use alternative Clonezilla live: https://clonezilla.org/downloads.php If none of them works, please export your VM and share that with us. If the issue is reproducible here, there is a chance it can be fixed.
Hey, Steven, thanks for your time. Unfortunatelly, the error persists. The message did changed a bit, but not so much. :-(
Hi Ed You should be good to clone once you change the controller to AHCI. You may need to restore the setting to RAID after cloning to be able to boot your PC. Enjoy.
"Waiting for single CPU states... Failed to disable /sys/devices/system/cpu/cpu1" -> even it failed to disable the CPU1, but I believe the process still ran. Please remove "quiet" and increase the "loglevel=3" to 4 or 5 in the boot parameters so that it gives you more verbose message.
We use Debian and Ubuntu Linux as our underlying OS for the Clonezilla live system. The upstream has dropped the i686 support... I suggest maybe you can move the disk to x86-64 machine to do the system back or cloning (if it's doable), that would be easier.
This issue was fixed in Clonezilla live >= 3.3.3-15 or 2026005-stonking. It was due to the package network-manager-tui was missing. Please give it a try and let us know the result. Thanks.
Hi Chuck, I found a setting in the bios to change from RAID to AHCI mode and that enabled me to image the drive, thank you so much for your advice. I thoroughly searched through the bios multiple times but could find no settings for VMD anywhere. I tested it quite a bit with both the latest stable releases and the older alternative version I have been using long term. On the alternative stable versions, the ssd showed up in the list of drives and mtdblock0 was also there, while the latest stable...
Hi Chuck, I found a setting in the bios to change from RAID to AHCI mode and that enabled me to image the drive, thank you so much for your advice. I thoroughly searched through the bios multiple times but could find no settings for VMD anywhere. I tested it quite a bit with both the latest stable releases and the older alternative version I have been using long term. On the alternative stable versions, the ssd showed up in the list of drives and mtdblock0 was also there, while the latest stable...
Hey all. I run clonezilla live in many scenarios, but I'm facing a curious issue when booting into any Hyper-V VM. As soon after it passes the boot menu, it starts disabling SMP-like behaviror, but, it throws me the error "Waiting for single CPU states... Failed to disable /sys/devices/system/cpu/cpu1" and the computer hangs. As a workaround, the error doesn't show if I set to just one processor, or if I use an old version of clonezilla (last working version is clonezilla-live-3.3.0-33-amd64, by...
Hi Chuck, I will try that as soon as I've got the computer in front of me again. Thank you very much for your help.
Hi Ed Your drive controller may be configured in RAID or VMD mode instead of AHCI mode required for Clonezilla. Please see this FAQ : https://drbl.org/fine-print.php?path=./faq/2_System/136_VMD_disk.faq#136_VMD_disk.faq Chuck
Hello, Using clonezilla-3.3.2-31. I am trying to create an image from a computer with 3 partitions sda1,sda3 and sda4. It gives me no errors during the creation of the image, I checked logs and everything is all right. But when clonezilla checks the image created sda1 and sda3 gives no errors but it says that sda4 doesn't exists. ls -l /var/www/webdav/ ..... -rw-r--r-- 1 www-data www-data 435 Jul 1 18:49 sda-pt.parted.compact -rw-r--r-- 1 www-data www-data 763 Jul 1 18:49 sda-pt.sf -rw-r--r-- 1 www-data...
Hello, Using clonezilla-3.3.2-31. I am trying to create an image from a computer with 3 partitions sda1,sda3 and sda4. It gives me no errors during the creation of the image, I checked logs and everything is all right. But when clonezilla checks the image created sda1 and sda3 gives no errors but it says that sda4 doesn't exists. ls -l /var/www/webdav/ ..... -rw-r--r-- 1 www-data www-data 435 Jul 1 18:49 sda-pt.parted.compact -rw-r--r-- 1 www-data www-data 763 Jul 1 18:49 sda-pt.sf -rw-r--r-- 1 www-data...
I just realised that I stupidly misspelled mdtblock0 when it is actually mtdblock0. I have edited my post to correct this.
Hi, I have been using Clonezilla to image my operating systems for years and it has made my life much easier, thank you for making such a great piece of software. I have just bought a used computer and when I tried to image the ssd like I usually do it didn’t show in the list of drives, in its place was the following: mtdblock0 32mb I searched the internet for solutions and have tried both the latest stable and alternative releases of Clonezilla, one gave the same result of mtdblock0 and the other...
Hello to everyone, we have a legacy system with a 686 compatible cpu (vortex) and we have a issue with ssd recnognition. Until now we have used a older clonezilla version (2.6.6) without problems but that version doesn'r recognize our new ssd model. So we tried to use newer clonezilla version 3.2.0 but after the selection of keyboard language the main program doesn't start and instead we have a bash shell. In your opinion is an issue due to incompatibility with our older configuration or maybe is...
Hi, I have been using Clonezilla to image my operating systems for years and it has made my life much easier, thank you for making such a great piece of software. I have just bought a used computer and when I tried to image the ssd like I usually do it didn’t show in the list of drives, in its place was the following: mdtblock0 32mb I searched the internet for solutions and have tried both the latest stable and alternative releases of Clonezilla, one gave the same result of mdtblock0 and the other...
I am using DRBL/Clonezilla with PXE boot to restore a captured image onto several laptops. These laptops do not have an onboard (integrated) network interface card (NIC), so I am forced to use external USB-to-Ethernet adapters. The issue is that when Clonezilla boots via PXE, it strictly looks for eth0. Since the live environment names the external USB NIC differently, Clonezilla gets stuck and throws the following error: Waiting for eth0 to be linked... Timed out! To resolve this, I tried modifying...
remote-dest and remote-source mode fails with "ask_user" is an unknown hard drive
Thanks for confirming this bug has been fixed.
Did you have any error messages when you run "drblsrv -i" and "drblpush -i"? It seems the linux kernel for your DRBL clients does not exist... Here my test went well: steven@noble-efi:~$ sudo drbl-proxy-dhcp enable *****************************************************. Synchronizing state of isc-dhcp-server.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable isc-dhcp-server Removed "/etc/systemd/system/multi-user.target.wants/isc-dhcp-server.service"....
NFS server feature in latest releases of Clonezilla is broken, specificly (alternative stable -20260525 - resolute - Ubuntu based) (alternative testing - 20260520 - resolute and stoking - Ubuntu based) Error code is as follows; Disable channel bonding since there is only one NIC found. Try to up wlan0... /usr/sbin/ocs-live-netcfg: line 423: nmtul: command not found No network card is configured! Do you want to try configuring one again?? {Y/n}_
Thanks for the fast fix! indeed 20260616 it's working. Did not try 20260620 yet.
I came across the same problem a week ago. I had success with 20260616-resolute. Thanks!
I can confirm it works with 20260620. Just tried today after having the same problem
Great. Thanks for confirming that.
Thanks! I have already test with clonezilla-live-20260620-resolute-amd64.iso : # Modify Client boot parameter echo 'supp_boot_param_ocs_live_extra="ocs_1_cpu_udev scsi_mod.use_blk_mq=0 nvme.poll_queues=1 ezio_seed_max_connect=10 ezio_see d_max_upload=0 ezio_upload_timeout=10"' >> /etc/drbl/drbl-ocs.conf ocscmd_='ocs-live-feed-img -cbm netboot -dm start-new-dhcpd -lscm massive-deployment -mdst from-image -g auto -e1 auto -e2 -r - x -j2 -edio -k0 -sc0 -p reboot -md bittorrent start "2026-06-12-09-img"...
thanks steven, ive emailed you
Sure, please email me at steven@clonezilla.org Thanks.
can i email it to you incase its got senstive data in it?
Thanks for your feedback. Could you please run "drbl-bug-report" on your DRBL server and share the generated file? It's easier for us to debug. Thanks.
Interesting... In that case, please report this resizing issue to GParted project: https://gparted.org/bugs.php
Hello!! Using clonezilla lite stable 3.3.2-31 I've set up a PXE server that allows me to run Clonezilla live without the need of USB. It uses ipxe.efi as a bootloader, so i'm showing here ipxe menus, that should not be a problem. I've followed the tutorial https://clonezilla.org/livepxe.php and adapted the kernel and initrd line adding the fetch option. kernel http://10.0.10.66/live/vmlinuz vmlinuz boot=live union=overlay username=user config components quiet loglevel=3 hostname=cl-3.3.1-35 noswap...
Thanks for the reply. I actually keep using partclone with checksums as I feel much more comfortable with it. Reliability is more important than performance.
As I said, I followed the suggested fixes from the Gparted website, which included the suggestion from the log itself. Booting Windows, running "chkdsk/f", rebooting twice, and trying Gparted again had no effect; this error continues to persist.
I see. I somehow missed that. Thanks for pointing that out. If there's a viable way to make that text more distinct visually, maybe it would help others avoid this mistake? That's the only thought I have for how to improve things; otherwise, it seems like you have everything.
Please give testing Clonezilla live >= 3.3.3-10 or 20260620-* a try: https://clonezilla.org/downloads.php With this version, after booting Clonezilla live, before you start lite server, you can edit /etc/drbl/drbl-ocs.conf, append the boot parameter you want in supp_boot_param_ocs_live_extra, e.g., Change supp_boot_param_ocs_live_extra="ocs_1_cpu_udev scsi_mod.use_blk_mq=0 nvme.poll_queues=1" to supp_boot_param_ocs_live_extra="ocs_1_cpu_udev scsi_mod.use_blk_mq=0 nvme.poll_queues=1 ezio_upload_timeout=10...
"When I interrupt the backup of a partition (CTRL-C) when using ntfsclone, clonezilla still reports an overall successful backup. Using partclone, clonezilla correctly reports an unsuccessful backup in that case." -> I believe it's a bug.... We will try to fix it in the future. However, actually we are thinking about to drop ntfsclone support in the future. It's recommended to have checksum for the image. It's much safer for your data.
From the log file, it said: "ERROR: Filesystem check failed! Windows wasn't shutdown properly or inconsistent filesystem. Please run chkdsk /f on Windows then reboot it TWICE." So are you able to boot your restored MS Windows and run "chkdsk /f"? Once it's done, you should be able to use GParted live to resize that again.
Basically the description is shown like this: https://clonezilla.org//clonezilla-live/doc/01_Save_disk_image/images/ocs-06-dev-img.png or https://clonezilla.org//clonezilla-live/doc/01_Save_disk_image/images/ocs-10-2-disk-selection.png Of course it can be improved in the future...
I believe you can ignore this BIOS error messages, since it's a warning from Linux system. It means it detects some bugs in your BIOS. However, normally it's harmless.
"Maybe there is an option to get the same result using the gui. What should I do?" -> No, for the time being, the way you did is the best one.
Thanks for your feedback. This is interesting... Somehow it's fixed by some newer packages from upstream? Maybe...
Please give testing Clonezilla live >= 3.3.3-8 or 20260616-* a try: https://clonezilla.org/downloads.php Let us know the results if you try that. Thanks.
stable = debian = no non-free software alternative-stable = ubuntu = contains non-free software
Was able to clone disk successfully. However, attempts to resize after cloning via Gparted Live 1.8.1-3 have been unsuccessful. When trying to resize the main partition (or overwrite it with data from the original drive), I get an error as shown in the attached file. I found and followed the steps on the gparted website for trying to resolve/avoid this error for NTFS file systems, but to no avail. I figured I'd share the log in case you had other suggestions for how to solve it. My only remaining...
hi all, get this error when i try to enable dhcp proxy as i dont want drbl to be my dhcp server as we already have one /usr/sbin/drbl-proxy-dhcp enable *****************************************************. Synchronizing state of isc-dhcp-server.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable isc-dhcp-server tftpd-hpa.service is not a native service, redirecting to systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install...
I described two problems, the partition name changing and the Partition Table destruction. Related with the second point I have found that the option “Use sfdisk from source …” generates the “-k” option in ocs-sr command and therefore it respects the destination Partition Table. By the way, the “Manual – enter command prompt” which adds the “-k2” option doesn’t prompt anything.
Thanks for the information. I've tried your suggestion and I actually see only a minimal improvement in speed with a0 instead of a3 (~3GB/Minute). This means - for my setting - ntfsclone is still much faster than partclone. Therefore I would like to use ntfsclone, but the final result of a backup reported by clonezilla is not reliable when using ntfsclone. When I interrupt the backup of a partition (CTRL-C) when using ntfsclone, clonezilla still reports an overall successful backup. Using partclone,...
Clonezilla live 3.3.2-31; ISO running off of DVD. In trying to get screenshots, I figured out that I had to hit spacebar to select the source/target device before pressing Enter to confirm. I'd recommend adding text to explain that to the user; I had previously assumed I only needed to hit Enter while the source/target image was highlighted. Cloning is currently proceeding. If I need further assistance and can't find what I'm looking for in another thread, I'll leave another comment here.
For the testing - 3.3.3-5 version, I am using it via Ventoy. In the case of the testing - 3.3.3-5 version, after booting and selecting the menu, a BIOS error message appears. Just like in this video: https://youtu.be/6wAFqi86Jy0 My environment is Windows 11, not a Linux environment. Is it okay that this BIOS error occurs? I'm reporting this just in case... My computer is a 2024 Korean LG laptop. The model is 15UD50T-GX5JK. The backup works fine, and everything else seems to be okay... This symptom...
From my understanding, Debian Linux (the underlying OS of Clonezilla live) natively supports Intel Volume Management Device (VMD) and software RAID through the Linux kernel and mdadm. Hence it should be supported. Did you encounter any issue when using Clonezilla live 3.3.2-31?
There is no any checksum mechanism in NTFSCLONE. Hence that's one of the reasons it can be faster. If you really care about the speed while wanting to ignore the checksum mechanism, you can actually edit /etc/drbl/drbl-ocs.conf change PARTCLONE_SAVE_OPT_INIT="-a3 -z 10485760" to PARTCLONE_SAVE_OPT_INIT="-a0 -z 10485760"
It's not a good way to remaster an existing GNU/Linux to a live system. That makes things more complicated. I suggest this: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/04_Create_Recovery_Clonezilla With this, you can restore to the destination machine and boot it. Most of the time it's easier.
Which version of Clonezilla live did you use? Could you please also take some of the screenshots and share that? It's easier for us to understand that.
Thanks for your feedback. This issue was fixed uploaded to Clonezilla git repo. It will be used in the next testing Clonezilla live, i.e., >= 3.3.3-5 or 20260613-*.