I have just upgraded our Clonezilla setup to 2.4.1-11-amd64, from 2.3.2-2-amd64. When booting from it to create an image from a disk I encounter a problem:
sulogin: root account is locked, starting shell
Then I'm dumped at a root prompt. Here are the PXE menu details:
The 'vmlinuz-unicast', 'initrd-unicast.img' and 'unicast.squashfs' files are symbolic links to the actual version being used. I've checked all the links and they are correct.
If I manually enter each pre-run command and then the ocs-sr command as above it all works fine and cloning is successful. So why is it not starting automatically with this release?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Attempting to restore the image with 2.4.1-11-amd64 gives different results. After a while loading (I saw systemd entries) the screen is blanked and I'm left with a flashing cursor top-left of the screen and nothing further. I can't break into it or change TTY.
Somehow the live-config/live-boot does not finish all its modules.
Are you able to reproduce this issue on different machine? E.g and older machine, or even in virtual machine, like virtualbox or VMWare WS?
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I haven't tried on more than one hardware type yet. Will give it a go. Incidentally I also tried 20150505-vivid-amd64 and that version will let me create an image, unlike 2.4.1-11-amd64, but again it gets stuck trying to do an image restore.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, please keep us posted.
BTW, remember to add "components" in your boot parameters in the newer testing Clonezilla live which uses live-boot/live-config v4. You can check the /syslinux/syslinux.cfg for the new boot parameters.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have just upgraded our Clonezilla setup to 2.4.1-11-amd64, from 2.3.2-2-amd64. When booting from it to create an image from a disk I encounter a problem:
sulogin: root account is locked, starting shell
Then I'm dumped at a root prompt. Here are the PXE menu details:
KERNEL http://192.168.15.0/vmlinuz/vmlinuz-unicast
APPEND initrd=http://192.168.15.0/initrd.img/initrd-unicast.img boot=live config noswap locales=en_GB.UTF-8 edd=on nomodeset noprompt nodmraid ocs_prerun="mkdir /home/partimagparent" ocs_prerun2="rmdir /home/partimag" ocs_prerun3="mount -t cifs -o user=clone,password=password //192.168.15.2/clone /home/partimagparent" ocs_prerun4="ln -s /home/partimagparent/upload /home/partimag" ocs_live_run="ocs-sr -q2 -c -j2 -rm-win-swap-hib -z1p -i 4096 -v -fsck-src-part-y -sc -p poweroff -um expert savedisk ask_user ask_user" ocs_live_extra_param="" keyboard-layouts=gb ocs_live_batch=no vga=791 nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.blacklist=yes fetch=http://192.168.15.0/filesystem.squashfs/unicast.squashfs
The 'vmlinuz-unicast', 'initrd-unicast.img' and 'unicast.squashfs' files are symbolic links to the actual version being used. I've checked all the links and they are correct.
If I manually enter each pre-run command and then the ocs-sr command as above it all works fine and cloning is successful. So why is it not starting automatically with this release?
Attempting to restore the image with 2.4.1-11-amd64 gives different results. After a while loading (I saw systemd entries) the screen is blanked and I'm left with a flashing cursor top-left of the screen and nothing further. I can't break into it or change TTY.
The menu options used to do the restore are:
KERNEL http://192.168.15.0/vmlinuz/vmlinuz-unicast
APPEND initrd=http://192.168.15.0/initrd.img/initrd-unicast.img boot=live config noswap locales=en_GB.UTF-8 edd=on nomodeset noprompt ocs_prerun="mount -t cifs -o user=clone,password=password //192.168.15.2/clone /home/partimag" ocs_live_run="ocs-sr -g auto -e1 auto -e2 -c -r -k1 -icds -j2 -p true -um expert -v restoredisk ask_user ask_user" ocs_live_extra_param="" keyboard-layouts=gb ocs_live_batch=no vga=791 nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.blacklist=yes fetch=http://192.168.15.0/filesystem.squashfs/unicast.squashfs
Reverted to 2.3.2-2-amd64 for now.
Somehow the live-config/live-boot does not finish all its modules.
Are you able to reproduce this issue on different machine? E.g and older machine, or even in virtual machine, like virtualbox or VMWare WS?
Steven.
I haven't tried on more than one hardware type yet. Will give it a go. Incidentally I also tried 20150505-vivid-amd64 and that version will let me create an image, unlike 2.4.1-11-amd64, but again it gets stuck trying to do an image restore.
OK, please keep us posted.
BTW, remember to add "components" in your boot parameters in the newer testing Clonezilla live which uses live-boot/live-config v4. You can check the /syslinux/syslinux.cfg for the new boot parameters.
Steven.
I think I may have found the cause of my problem. Adding 'union=overlay' appears to fix it. I didn't have that option in older versions.
Oh, right. For Linux kernel aufs was replaced by overlay, so it's a must to add "union=overlay" for the latest testing Clonezilla live.
Steven.