Activity for Steven Shiau
-
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
-
The massive checking function for spam posts does not work.
-
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
-
Cool. Thanks for clarifying that. Steven
-
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
-
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
-
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
-
Cool. Thanks for confirming that. Steven
-
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
-
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
-
Duplicated post. Let's focus on this one: https://sourceforge.net/p/clonezilla/discussion/Help/thread/c8eb1a6f35/ Steven
-
Normally Clonezilla won't modify your source disk, unless you hit a bug. In your case, make sure you do not choose the wrong source disk and destination one. If they are correct, normally this is due to you do not remove one of them from the machine after cloning and just boot your machine. This might confuse the OS you have. In this case, you can boot Clonezilla live and to mount the file system on your source disk/partition, and copy the data. Your data should be still there, just the booting mechanism...
-
You can refer to this: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/05_Preseed_options_to_do_job_after_booting The syntax of syslinux/isolinux is very similar to grub. Just need to do some conversion. Steven
-
OK, great. Thanks for sharing that. Steven
-
From the photos, apparently you have no /dev/sdb, and your image was saved from /dev/sdb. It looks like you are using Clonezilla lite server. Before you start the server, you have to convert the image to /dev/sda so that it can be restored to your destination machines, if the /dev/sda is the disk you want to deploy. As the prompt mentioned, you can use this command to convert the image to /dev/sda format: https://drbl.org/management/techrpt.php?c=cnvt-ocs-dev&t=To%20change%20the%20device%20name%20in%20saved%20clonezilla%20image...
-
Thanks for your feedback. OK, this is a wishlist. Maybe in the future we will implement that. Steven
-
"when i create iso file with ocs-iso, the created iso still have old version." -> What did you mean? Please describe more so that we can try to help you. Steven
-
It's recommended that you can attach those files, not paste them in in the discussion content. It's not easy to read... "So I believe there is a confusion when both MBR & GPT" -> So in your case, you have two disks, and one is GPT, and the other one is MBR? They form the LV you have? Or? Steven
-
Please use "-" to separate the name, i.e., in your case, you should use: autoname-SRV-TST-datefmt_%d%m%Y Then it will give you the image name like: SRV-TST-24072024 Steven
-
Stable Clonezilla live 3.1.3-16 Released
-
So it looks like you are saving your Proxmox server? AFAIK, Proxmox uses thin provisioning LVM, and due to some technical issues, Clonezilla does not support thin provisioning LVM: https://github.com/jthornber/thin-provisioning-tools/issues/126 I believe that's the reason why. Steven
-
"is there a way to see what the Image contains?" -> You can list the files in the image directory by running: ls -alF /home/partimag/$YOURIMAGENAME Replace $YOURIMAGENAME with yours. Steven
-
Thanks for your feedback. '"please skip those zfs partition, as we only want save the "physical disk" or "physical partition"' -> It will be great if you can provide us the patch file so that this is clearer to us. Thanks. Steven
-
Sure, we will update that in the files of Clonezilla. However, most of the distributions they maintain their own packaging files. Hence reporting this to the upstream will be better.
-
The name shown in GParted, or Parted, is actually not really unique in a machine. Different partitions might have same name... When in saving mode, it might be OK to use that. However, when restoring, things might be complicated... Steven
-
Great. Thanks for confirming that. Steven
-
partclone failed on 100% when cloning windows c drive
-
Thanks for your feedback. Please give testing Clonezilla live a try, i.e., >= 3.1.3-16 or 20240715-*: https://clonezilla.org/downloads.php Someone has confirmed this version works: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/005484a513/?limit=25#1f72 As for the shim, we use juse the one from Debian/Ubuntu repository. Therefore if anything you'd like to suggest, maybe you can report that to Debian Or Ubuntu. Steven
-
So the improvement for the next release is just leave away these commands which I currently have to undo using lvreduce to put it to the original LV size." -> Are you sure? I believe there is more. Actually tried to support thin provisioning LVM in Clonezilla. However, we encountered this issue: https://github.com/jthornber/thin-provisioning-tools/issues/126 Steven
-
@Kenzie, Did you try Clonezilla live 3.1.3-16? Gilles has tested the improved version 3.1.3-16, and he confirmed the issue is gone: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/005484a513/?limit=25#1f72 Steven
-
Hi Gilles, Great. Thanks for conforming that. Steven
-
Thanks for your feedback. This issue is related to this one: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/1148da4c7a/?limit=25#ac0b Please check that. Thanks. Steven
-
Guys, Thanks for your feedback. Could you please give testing Clonezilla live a try, i.e., >= 3.1.3-16 or 20240715-*: https://clonezilla.org/downloads.php We have reverted the NTFS-related codes to the previous version in the package Partclone. This issue should have been fixed. Please let us know the results. Thanks. Steven
-
Do you have 2nd DHCP server in your LAN? Steven
-
Actually I would suggest you run: sudo drblsrv -i after you run "apt install drbl clonezilla". It will detect the GNU/Linux version and put the required packages. Steven
-
What did you mean by name? Label or? Actually it's shown in the TUI, e.g., https://clonezilla.org//clonezilla-live/doc/01_Save_disk_image/images/ocs-10-2-disk-selection.png Or you meant different thing? Steven
-
Thanks for your feedback. We will examine this issue. @Rody, Does Clonezilla live 3.1.2-22 work for you? Steven
-
Your Clonezilla live version is old. I suggest you try the latest stable one (e.g., 3.1.3-11) first, and if the issue remains, please report it. https://clonezilla.org/downloads.php Steven
-
Is that possible you can show the files list in the image dir by running some like: ls -l /home/partimag/sri16jun2024-*/*? It's better to output that to a text file so that it's easier for us to read, e.g., ls -l /home/partimag/sri16jun2024-*/*? > /tmp/imglist.txt then share the imglist.txt file. BTW, if you kept the log file /var/log/clonezilla.log., please share that, too. You can email me at steven@clonezilla.org. Steven
-
DRBL live is not maintained due to some technical issues. The image format version you are using in DRBL live 2.5.1 is older than that in Clonezilla live 20240408. I suggest you give Clonezilla lite server a try: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server It's based on Clonezilla live, and you can use the same version of Clonezilla live, i.e., 20240408 or newer stable one. Steven
-
Thanks for your feedback. Please give testing Clonezilla live >= 3.1.3-15 or 20240711-* a try: https://clonezilla.org/downloads.php This issue should have been fixed. Please let us know the results. Thanks. Steven
-
Thanks for your feedback. It's great to know you have solve the issue. Steven
-
Well, we can not reproduce this issue here, and you are the only one mentioned this issue. Normally this kind of CRC error is hardware-related. E.g., RAM, CPU fan or network cable,,, You'd better to check your hardware. BTW, it's possible you can bypass the CRC error. Just enter expert mode, and choose the option "-icrc", as shown here: https://clonezilla.org//clonezilla-live/doc/02_Restore_disk_image/images/ocs-09-advanced-param-extra.png Steven
-
Thanks for your feedback. Somehow here I just can not reproduce this issue. I used Clonezilla live 3.1.3-11 amd64 release, and saved Ubuntu Jammy which has 1 LUKS partition. It ran smoothly here. The image repository I had: root@debian:~# findmnt /home/partimag/ TARGET SOURCE FSTYPE OPTIONS /home/partimag //192.168.120.8/smb cifs rw,relatime,vers=3.1.1,cache=strict,username=bryan,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.120.8,file_mode=0755,dir_mode=0755,so When it saved an image, in the step...
-
Hi Bastien, It's synced. Let us know if any issues. Thanks. Steven
-
Stable Clonezilla live 3.1.3-11 Released
-
Is this issue reproducible with testing Clonezilla live, i.e., >=3.1.3-11 or 20240630-*: https://clonezilla.org/downloads.php Steven
-
Maybe it's easier that if you can create a VM with such a LVM layout? Then share that with us? It's easier for us to reproduce this issue. Steven
-
sshfs missing in dependency list
-
Well, sshfs is not really a must. You can only say it's recommended to have that. Hence please report to the distribution you are using, i.e., Ubuntu Linux, or Debian, to suggest the user to install sshfs when installing the clonezilla package. Steven
-
Not sure. Did you check the log files, e.g., /var/log/syslong? Maybe you can find some clues. BTW, if what you need DRBL is for Clonezilla massive deployment function, you can also try this mode: https://clonezilla.org//clonezilla-SE/use_clonezilla_live_in_drbl.php i.e., use Clonezilla live as the client's OS when deploying. In addition, you can also use Clonezilla lite server: https://clonezilla.org///fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server Steven
-
If you Clonezilla live for legacy BIOS, the boot menu you have to modify is syslinux/syslinux.cfg or syslinux/isolinux.cfg. Ref: https://clonezilla.org//fine-print-live-doc.php?path=./clonezilla-live/doc/99_Misc/00_live-boot-parameters.doc#00_live-boot-parameters.doc Steven
-
Clonezilla can save a partition as an image, and you can restore it to another partition. It can also clone a partition to another partition. However, your restored/cloned OS has to be responsible for the booting and other related mechanism. "Also, can I backup the C drive, install new windows in a laptop, resize the C drive backup then restore it?" -> What did you mean by this? Steven
-
Thanks for asking again. Actually the stable Clonezilla live will be released next week. Hence the repository will be synced then. Steven
-
It seems the Linux kernel does not support your hardware. Do you know which version of GNU/Linux support your hardware? BTW, please remember to use amd64 (x86-64) release. Do not use i686 one since it's only for very old machine. Steven
-
Before you reboot/shutdown the machine, please enter command line prompt, and check if the image repository (/home/partimag/) is still mounted by running: mount If it is, you can run: find /home/partimag/ -print to see the results. Please show the results to us. BTW, the log file /var/log/clonezilla.log contains many info, so please also share that with us. Steven
-
You still can find the archived files here: http://free.nchc.org.tw/drbl-live/testing/ Actually due to some technical issues, we do not create newer DRBL live. It's recommended to use Clonezilla lite server if you need Clonezilla server functions. For more info, please check: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server Steven
-
Are you sure the image is saved in the mounted image repository? How did you mount your USB flash drive? Please describe all of your steps in detail so that we can help you. Steven
-
Is your image was saved for some partitions, not a whole disk? Steven
-
Please run the following command in the Clonezilla live command line prompt: 1.sudo -i 2. cat /proc/partitions 3. mount Please show the results of 2 & 3. Thanks. Steven
-
Mmm.. Actually Clonezilla does not support thin provisioning LVM, due to some tools do not have required functions. So your issue is about thin provisioning LVM? If so, for the moment it's can not be done. Steven
-
...
-
First, always use amd64 (x86-64) version of Clonezilla live if you can. The i686 version is only for very old machine. Second, please give testing Clonezilla live a try, e.g., 3.1.3-10 or 20240624-oracular: https://clonezilla.org/downloads.php It comes with the newer Linux kernel so your hardware should be supported better. Steven
-
You can try to install sysprep on your MS Windows before you take an image using Clonezilla. Then try to restore the image to newer machine to see if it will detect and load the drivers automatically. Steven
-
Well, software license is complicated. It really depends. Some of the licenses will detect the hardware info. Hence even the license is kept in the hard drive, it will deny you to use the software. Some of the software will force you to login to verify the permission, say MS Office 365... Anyway, you have to consult your software vendor about that. Steven
-
It looks like this is related to Linux kernel. Have you tried newer, testing Clonezilla live? e.g., 3.1.3-10 or 20240624-oracular? https://clonezilla.org/downloads.php It comes with newer Linux kernel so it might support your hardware better. Steven
-
Thanks for updating that. Is that possible you can share the VM with us? We'd like to reproduce this issue, and try to improve it. Steven
-
I suggest you can use Clonezilla lite server: https://clonezilla.org///fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server You can try the multicast mode or BT mode. If all of them are identical, you can have a template machine ready. Use it as the Clonezilla lite server, and use BT mode directly reading the data from its hard drive. i.e., try this one: https://clonezilla.org///fine-print-live-doc.php?path=clonezilla-live/doc/12_lite_server_BT_from_dev Steven
-
Did you mean you want to save the image in unattended mode? If so, you can refer to this: https://clonezilla.org///fine-print-live-doc.php?path=clonezilla-live/doc/05_Preseed_options_to_do_job_after_booting Basically you have to mount the image repository, and use ocs-sr command to save the image to the repository. BTW, the PXE boot configuration files you have to edit are: uEFI netboot: /tftpboot/nbi_img/grub/grub.cfg Legacy BIOS netboot: /tftpboot/nbi_img/pxelinux.cfg/default Steven
-
If you use DRBL is for Clonezilla SE purpose, I suggest you can try this mode: https://clonezilla.org//clonezilla-SE/use_clonezilla_live_in_drbl.php In addition, give different versions of Clonezilla live a try, e.g., the latest testing one, 20240625-oracular: https://clonezilla.org/downloads.php Steven
-
Please refer to this: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/457da2b48a/?limit=25#9faa Steven
-
Basically you can follow this: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/03_Disk_to_disk_clone Just remember to choose "part to local part" here: https://clonezilla.org//clonezilla-live/doc/03_Disk_to_disk_clone/images/ocs-06-disk-to-local-disk-clone.png Pay attention to the source partition and destination one. Do not choose the wrong one. //NOTE// Backup important data before you use Clonezilla. Just in case. Steven
-
It's great to know you have fixed that, though I have no idea what's happened there. Steven
-
Cool. Thanks for sharing that. Steven
-
"Could it be solved by choosing -k1 instead of -k0? " -> Well, maybe. However, the best is to follow the method 2 mentioned here: https://drbl.org/fine-print.php?path=./faq/2_System/119_larger_to_smaller_disk_restore_clone.faq#119_larger_to_smaller_disk_restore_clone.faq Steven
-
OK, great. Thanks for your feedback. Steven
-
Thanks for your feedback. We will read that and try to improve that in the future. Steven
-
Please give testing Clonezilla live <= 3.1.3-8 or 20240614-* a try: https://clonezilla.org/ Steven
-
Maybe, not very sure. You can try to restore that to a virtual machine to see if it works or not. Steven
-
Please give testing Clonezilla live a try, i.e., 3.1.3-8 or 20240614-*: https://clonezilla.org/downloads.php We have updated Partclone with newer BTRFS version support. Please let us know the results. Steven
-
Please give testing Clonezilla live a try, i.e., 3.1.3-8 or 20240614-*: https://clonezilla.org/downloads.php We have updated Partclone with newer BTRFS version support. Please let us know the results. Steven
-
"by choosing 1 or 2 or does the choice only count for the clone being made?" -> It will modify /dev/sda1, the FAT file system which you have cloned. Basically the source one won't be touched. "is there a way to test the clone and if its working, without whiping the PC by doing so? (similar to Linux Live Mode)' -> Not really. However, you can try and test it by restoring the image to a virtual machine. Steven
-
Not sure what's happened there. However, is this issue reproducible in Clonezilla live >= 3.1.3-7 or 20240609-*? https://clonezilla.org/downloads.php Steven
-
Duplicated post. Let's focus on this one: https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/457da2b48a/ Steven
-
Not sure, but I guess either 1 or 2 should be OK. //NOTE// Backup important files before you use Clonezilla. Just in case. Steven
-
Thanks. We will try to reproduce this and, and will update Partclone about BTRFS recently. Steven
-
Thanks for your feedback. It is a bug, and has been fixed in Clonezilla live >= 3.1.3-7 or 20240609-*: https://clonezilla.org/downloads.php Please let us know the results. Thanks. Steven
-
No, I meant the original source partition, the BTRFS one (or it's /dev/sda6? /dev/sdh6? whatever), not the cloned one. How did you create that? Is it formatted by Mint when you installed that? Or? Steven
-
So how did you format your /dev/sdb6 as BTRFS? Any specific parameters? Thanks. Steven
1 >