First, an enormous thank you to the author of this program for providing one of the best cloning tools to ever exist. Fast, reliable, professional and accurate support from what I've read on the forum. I use this software on a daily basis and it has saved my butt and the butts of my clients many times, managed to save a lot of data over the years and brought a smile on many client's faces. This tool worked when other tools, both free and paid ones didn't know what to do and just gave up. This tool is the most essential and important one in my arsenal. Even though I have noticed the newer versions have bugs, they are ironed out faster than full blown company teams that are responsible for support. Please accept my deepest gratitude and I hope the development of this software continues smoothly and easily, without any problems.
The disk cloning is very slow an occasionally freezes, took a lot of time to unmount disks as well. Here are some error messages that appeared at the end of the clone before the unmounting process (command line showing) started.
Any Input/Output error error message is almost always a physical issue. Eg:
bad sectors on drive
bad or loose USB cable, or SATA cable
bad USB hub
bad HDD enclosure
etc
Generally, this error can occur on on the source disk or destination disk, but from the image above it's happening on /dev/sdb, which happens to be the destination disk for the operation being conducted here.
One tip I use myself with bad disks is to open a terminal window and type dmesg -Tw and then when you run the operation you may see a big batch of more detailed error messages indicating the specific bad sectors as they are attempted to be processed, which can give more information for the disk being processed. (side note: I should include this information with the Rescuezilla user-interface itself).
There are a number of other things to check/try eg, SMART disk health information, but when we suspect a not-so-great disk, the best thing is to retry with an alternative disk, perhaps even using a different SATA cable and port etc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well both disks are brand new with a few days of use and no smart errors. I think the enclosure might be the culprit since it's one of the cheap Chinese ones and took a bad fall but seemed to work fine but ig not. Thanks for the immaculate support as always, will try another one and get back to you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2025-06-07
The other enclosure was faulty, changed the enclosure and it worked on another laptop flawlessly but not on this one. It has a new error messages now.
First, an enormous thank you to the author of this program for providing one of the best cloning tools to ever exist. Fast, reliable, professional and accurate support from what I've read on the forum. I use this software on a daily basis and it has saved my butt and the butts of my clients many times, managed to save a lot of data over the years and brought a smile on many client's faces. This tool worked when other tools, both free and paid ones didn't know what to do and just gave up. This tool is the most essential and important one in my arsenal. Even though I have noticed the newer versions have bugs, they are ironed out faster than full blown company teams that are responsible for support. Please accept my deepest gratitude and I hope the development of this software continues smoothly and easily, without any problems.
The disk cloning is very slow an occasionally freezes, took a lot of time to unmount disks as well. Here are some error messages that appeared at the end of the clone before the unmounting process (command line showing) started.
Any Input/Output error error message is almost always a physical issue. Eg:
Generally, this error can occur on on the source disk or destination disk, but from the image above it's happening on
/dev/sdb, which happens to be the destination disk for the operation being conducted here.One tip I use myself with bad disks is to open a terminal window and type
dmesg -Twand then when you run the operation you may see a big batch of more detailed error messages indicating the specific bad sectors as they are attempted to be processed, which can give more information for the disk being processed. (side note: I should include this information with the Rescuezilla user-interface itself).There are a number of other things to check/try eg, SMART disk health information, but when we suspect a not-so-great disk, the best thing is to retry with an alternative disk, perhaps even using a different SATA cable and port etc
Here's another picture.
Well both disks are brand new with a few days of use and no smart errors. I think the enclosure might be the culprit since it's one of the cheap Chinese ones and took a bad fall but seemed to work fine but ig not. Thanks for the immaculate support as always, will try another one and get back to you.
The other enclosure was faulty, changed the enclosure and it worked on another laptop flawlessly but not on this one. It has a new error messages now.
Changed the usb and reflased again. Got further but got this.
Last edit: Werewolf IT Support 2025-06-07
There's less space on the second drive?
I figured it out, correct me if I'm wrong. Second drive has less space and can't write sectors the program needs?
Yes, Rescuezilla (and Clonezilla) have some limitations if the second drive has less space.
There is a workaround that works but is manual, time-consuming and inconvenient: https://github.com/rescuezilla/rescuezilla/wiki/HOWTO:-Restoring-to-a-smaller-disk.-Eg,-1000GB-HDD-to-500GB-SSD
Thank you very much for confirming. Have a nice day.