Paul B.

Sure. Here is the contents of my Grub custom.cfg file. I have 11 partitions on this machine, and Grub goes to hdd3,1 and finds the viable file path to the ISO there, without speccing the partition. However, the following code is not perfect yet. I am getting repeated cannot change locale errors and the keyboard layout is not changed to Dvorak as I would like. But at least it does boot and work. menuentry "ISO-boot: Clonezilla Live" { set isofile=/Seeds/clonezilla-live-2.6.5-21-amd64.iso search --no-floppy...

I am very surprised. That actually worked. I assumed Grub would need to know which partition the ISO was on, but apparently it checks them all for a viable file path. Thanks much, Steven.

Hi Steven, thanks for responding. I'm trying to boot from an ISO on a different drive and partition. So far I'm getting a "no such device" error. I did have a space in my keyboard spec. I've now corrected that. Here's my Grub custom.cfg: menuentry "ISO-boot: Clonezilla Live" { set isofile='hd2,1'/Seeds/clonezilla-live-2.6.5-21-amd64.iso # search --set -f /live/vmlinuz search --no-floppy --set=root --file $isofile loopback loop $isofile set root=(loop) echo "Booting $isofile ..." linux /live/vmlinuz...

Hi, I've succeeded in booting Clonezilla Live from an ISO using Grub2. But two problems remain. I'd like to move the ISO out of my root drive and into a partition I never back up. Apparently it being in root prevents that partition from being worked on by CZ. And I'd like to make the keyboard layout US-Dvorak, and eliminate some of the other questions. I tried keyboard-layouts= US-d to no avail. I see now that maybe the capitals were the problem? Anyway, step 1 is to get the remote ISO to boot. Thanks...

Just to update my situation. Loukas very generously worked with me and found some problems in the logs. Turns out specifying "Only Include" for the backup job was creating the problems (I'm not sure of the technicals of it). So I broke the job of three tasks up into individual tasks, one for each Source folder, each operating as "Normal Include". This wasn't hard because two tasks only had two folders each, making a total of four tasks. And then the last task, my /home profile, which already was...

OK, will do Loukas. Thank you. I hope I have the correct address...

Hi Loukas, Thanks very much for responding. Yes, I deleted the .l-s folders from my /home directory and from each of the three target directories of the backup job. In addition, this time I also deleted the Snaps subfolder from my /home/.luckybackup hierarchy. When I ran the job, the .l-s folders were recreated in the three target directories, but not in the /home directory. The Snaps subfolder also was not recreated there. The errors in the log are plentiful, and all seem to pertain to target folders,...

Hello guys, I'm on MX Linux and am having the same problem. I've deleted all .luckybackup-snapshots folders I could find, and stilll have tons of "cannot delete non-empty folder" errors. Not sure what to do. Edit: I've also made sure my Permissions are in order. I'm running Lucky non-elevated.