Thought I'd clone a few drives with rescuezilla Save a bit of keyboard bashing. No deal.
Messed with the BIOS settings for some strange reason. Seemed to be looking for and failing to find non existing folders Seems it needs a Linux drive to be installed on the machine. Wouldn't start with no internal drive installed or only a Win drive installed. I usually pull the drives not needed when doing dangerous stuff. The source and destination drives are mounted in cradles
Clone function failed with disk full error even though there was over four times more space than needed.
Tried going the image path. Made the image ok but refused to restore. Same no space error
Wasted most of Sunday afternoon. Got no where. Did the job cloning the four drives as I usually do by bashing the keyboard in terminal. Knocked it over in a bit over an hour.
Interesting if nothing else
Greer Kylus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Weird -- Rescuezilla should start with no internal drive installed or onl a Windows drive installed.
Hmm, Clone failing with disk full is very weird, were you overwriting the destination partition table and cloning all content?
Could you please upload the clonezilla-img log either here or send it to rescuezilla at gmail
What kind of source disks were you you trying to copy? Were there any interesting configuration things like RAID, Linux LVM (Logical Volume Manager) etc?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2023-07-07
Just ubuntu 22.04 on a 250 G ssd to some 1 T drives Nothing odd or fancy Went across with the manual copy and fix grub
Didn't keep any log files. Scrub ed it all and went back to the tried and true method
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thought I'd clone a few drives with rescuezilla Save a bit of keyboard bashing. No deal.
Messed with the BIOS settings for some strange reason. Seemed to be looking for and failing to find non existing folders Seems it needs a Linux drive to be installed on the machine. Wouldn't start with no internal drive installed or only a Win drive installed. I usually pull the drives not needed when doing dangerous stuff. The source and destination drives are mounted in cradles
Clone function failed with disk full error even though there was over four times more space than needed.
Tried going the image path. Made the image ok but refused to restore. Same no space error
Wasted most of Sunday afternoon. Got no where. Did the job cloning the four drives as I usually do by bashing the keyboard in terminal. Knocked it over in a bit over an hour.
Interesting if nothing else
Greer Kylus
Hi Greer Kylus,
Sorry to hear your experiences here.
Weird -- Rescuezilla should start with no internal drive installed or onl a Windows drive installed.
Hmm, Clone failing with disk full is very weird, were you overwriting the destination partition table and cloning all content?
Could you please upload the
clonezilla-imglog either here or send it to rescuezilla at gmailWhat kind of source disks were you you trying to copy? Were there any interesting configuration things like RAID, Linux LVM (Logical Volume Manager) etc?
Just ubuntu 22.04 on a 250 G ssd to some 1 T drives Nothing odd or fancy Went across with the manual copy and fix grub
Didn't keep any log files. Scrub ed it all and went back to the tried and true method