Clonezilla versions affected: alternative stable, 20191024-eoan; the current 'testing' version of Clonezilla.
When booting Clonezilla live, my system freezes. Sometimes that happens just after the words, 'Configuring keyboard' have appeared on the screen - and those words remain on the screen. At other times (i.e. during other attempts to boot the same USB) that same text appears, but then the screen goes blank, and then I get the hang.
The hang occurs (in one form or other) if I leave the syslinux.cfg file unmodified but also if I modify it to set my keyboard layout.
Here are the details of the machine on which I experience the behaviour.
OS: Linux Mint 19.3 Tricia x86_64
Host: 20KHCTO1WW ThinkPad X1 Carbon 6th
Kernel: 5.3.18-050318-generic
Shell: bash 4.4.20
Resolution: 2560x1440 @ 60.01Hz
DE: Cinnamon 4.4.5
WM: Mutter (Muffin)
CPU: Intel i7-8550U (8) @ 1.800GHz
GPU: Intel UHD Graphics 620
Memory: 1689MiB / 15907MiB
Disk (/dev/nvme0n1p4): 18G / 40G (48%)
Disk (/dev/nvme0n1p2): 149G / 405G (39%)
Disk (udev): 0 / 7.8G (0%)
No idea about this, and you are the only one reporting this issue so far. Hence I think it's hardware specific, and is related to Linux kernel and hardware support issue, or maybe your hardware is not stable. Please try to use the same version of Clonezilla live to boot on different machine to see if it has similar issue. If not, then that's what I have mentioned.
Steven
I have tested now on another laptop - a ThinkPad X230. On that computer, Clonezilla worked, even when I choose the 'large fonts' boot option (an option inappropriate to the machine; I chose the option to replicate what I had done on the first machine).
So it does seem that it is the ThinkPad X1 (as against ThinkPad X230) that is the problem. Or rather: your software is the problem, for it does not work on the machine on which I wish to use it. EDIT: Also, the proprietary backup program 'ShadowProtect Recovery Environment' does not work on that same laptop (the X1) and so I am in a pickle now that Clonezilla does not work on it either. I note that in the problem with ShadowProtect seems to be that its version of the Linux kernel is too old for my hardware. (The makers of ShadowProtect said that a new version of their software, with a newer kenel, would be out any week now. That was some eighteen months ago. It's still not out.)
Last edit: JN 2019-12-29
In that case, you can give testing Clonezilla live a try, e.g., >= 2.6.5-8 or 20191226-focal:
https://clonezilla.org/downloads.php
They come with newer Linux kernel so your hardware might be supported better.
Steven
Thanks, but as I wrote: in addition to the stable version, I tried also the latest testing version.
I also have reports about this, for me it happened in one out of three hosts.
All three hosts are identical in HW and SW DELL R640.
We currently use clonezilla live version: clonezilla-live-2.5.0-25-i686.iso
I will also test a newer version of Clonezilla and report back here once it is done.
We boot the Live iso via iDRAC as virtual media.
Booting is halted at Configuring keyboard. See attached image.!
TL-DR don't use KMS.
I can duplicate error using latest 20210127-groovy and selecting option 2 to boot from pendrive to RAM, KMS, large font. Booting from UEFI pendrive (FAT32 usb2) using a Microsoft Surface Pro 7 (PVR-00016) Model 1866. On screen text shows:
Live media is in /run/live/medium
Updating /etc/ocs/ocs-live.conf based on kernel parameters if found...
done!
Using font size for the console: 16x32
(several blank lines, then at bottom of screen)
Configuring keyboard...
_
(Underscore at end intentional)
Issue apparent with or without the surface pro keyboard attached.
Fault only apparent when booting with KMS. When booting, to RAM or otherwise, without KMS, works fine. Not a large-font option, so awful resolution on the Surface Pro's high pixel density screen, but it works.
It may be totally unrelated, but mentioning - source is NTFS with MS Bitlocker which CZ clones as RAW. Since I'm unsure how CZ handles backing up and restoring to SSD with bitlocker, I'm not proceeding with clonezilla in this scenario.
I see this problem using clonezilla-live-2.7.1-22-amd64 or clonezilla-live-20210127-groovy-amd64. I selected (Default settings, KMS with large font & To RAM). The last output is "Configuring keyboard..." I used an Acer Swift 1 (model SF114-32) with an Intel Pentium Silver N5000 CPU. I booted from a USB drive.
I don't see this problem when I select (Default settings, VGA 800x600) or (Default settings, VGA 1024x768).
@John,
What the results if you press Enter key? Any progress or it still hangs?
Thanks.
Steven
Try adding kernel boot param
keyboard-layouts=us
.I have the similar issue with Clonzilla 2.5 and 2.7 on Dell e7420. It has been working fine on all Dell Latitude - the only change on this latest model is come with a fingerprint reader.
Hi
I am encountering the same problem with the latest release:
clonezilla-live-2.7.2-39-amd64.
I had the same problem with a much, much older release so I created a brand new boot USB from scratch.
The new USB works correctly on two other machines so that probably rules out some sort of corruption error etc. with the USB. However the port on the Samsung machine is USB 3.0 type "C". I believe it is a Thunderbolt port.
I have tried different Video modes but all totally freezes on start up when it gets to the the "Choose Language Screen" . The only way to get the machine back is to do a hard reboot - ie hold the powerkey down until the laptop powers off.
I would try "keyboard-layout=us" mentioned above by Ichan but I am not sure where that parameter should go ( I am not that knowledgeable about Linux) .
The machine that is having the problem is a Samsung Galaxy Book S. The details of the machine are below.
The bugs is repeatable so if you need me to create logging information I can. Just tell me explicitly which files need to be edited to do so and how to get the logs back to you. .
I have tried to capture some of the messages that go to the screen if that helps but frankly that is hard as they roll off so quick. I have attached the screenshots.
This is the first problem I have ever had with Clonezilla in probably over 10 years of usage. Clonezilla has saved the day for me a number of times and I have recommended it to lots of friends.
Thanks
Stephen
Boot USB : 16 GB with 13.3 GB free.
PC Info
System Name SAMSUNG-S2
System Manufacturer SAMSUNG ELECTRONICS CO., LTD.
System Model 767XCL
System Type x64-based PC
System SKU SCAI-A5A5-A5A5-A5A5-PAJD
Processor Intel(R) Core(TM) i5-L16G7 CPU @ 1.40GHz, 1382 Mhz, 5 Core(s), 5 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P07AJD.053.200820.KS, 8/20/2020
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer SAMSUNG ELECTRONICS CO., LTD.
BaseBoard Product NP767XCM-K01US
BaseBoard Version SGLA395A21-C01-G001-S0003+10.0.18363
Platform Role Mobile
Secure Boot State On
Is this issue reproducible on testing Clonezilla live? E.g., 2.7.3-19 or 20210817-impish?
https://clonezilla.org/downloads.php
As for the boot parameter to preset language and keyboard, you can refer to:
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
I tried the both testing version of Clonezilla (2.7.3-19) and to preset the keyboard language.
Both work on the Thinkpad but not on the Samsung S2.
While testing I noticed that the Samsung S2 has "Secure Boot" enabled but the Thinkpad did not. So I enabled it on the Thinkpad. (I have a good backups of the Thinkpad...but not of the S2 so I reasoned that if I was going to play with boot features it was much safer to use Thinkpad).
Net result was that the Thinkpad worked OK with and without "Secure Boot" enabled so it would seem pretty unlikely, but clearly not impossible, that this is causing the issue.
Thanks
Stephen
Have you tried to update the BIOS firmware for your Samsung S2? Maybe that helps?
Steven
Can you confirm
keyboard-layouts=us
is appended on the kernel boot param?I don't see Configuring keyboard message in your screenshot, perharps just a timing?
Yes, exactly, as described here:
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
To respond to all above here:
BIOS is up to date.
As regards to keyboard layout parameter . I had been editing the ones in syslinux. I didn't realize I was supposed to edit the one in \boot\grub\grub.cfg.
So I edited that and it now has the following parameter set for all possible boot options (11 of them I believe) :
keyboard-layouts=us
i.e. :
$linux_cmd /live/vmlinuz boot=live union=overlay username=user config components quiet noswap edd=on nomodeset enforcing=0 noeject locales= keyboard-layouts=us ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch="no" vga=788 ip= net.ifnames=0 nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=1
$initrd_cmd /live/initrd.img
Sadly although this did change where the machine hung Clonezilla is still not working.
It now hangs on the "Start Clonezilla or enter login shell" (see attached photo of screen
Same symptom : keyboard totally locked, no mouse movement and the only way to recover is forced power-off by holding down the power button till the machine recycles.
Thanks
Stephen
It is also possible that keyboard doesn't work since you are in Terminal User Interface (TUI) and there is no mouse support.
Are you able to boot to other distro (Ubuntu, Centos,etc) ?
I have not tried other distros. I am not really much of a Linux guy so I have little reason to try them.
As for TUI issues - why does the same USB drive boot perfectly on three other machines?
What would make the mouse support different, or even applicable, in this context as I am not using the trackpad /mouse. The cursor keys don't work, along with every other key on the keyboard - all dead.
There are a large number of messages sent to the screen as the system boots and configures Clonezilla. Is there a simple way that these can be captured as they roll off too quickly to read?
Have you try using legacy boot?
No BIOS option to use legacy boot . I checked all the options in the BIOS menu and no Legacy option found. :(
" why does the same USB drive boot perfectly on three other machines?" -> Maybe this is really a hardware issue. Or the Linux kernel comes with Clonezilla live does have an issue to support your chips on the motherboard.
" Is there a simple way that these can be captured" -> Well, the easiest way is to take a video by your smart phone I believe. :)
Some messages might exist in /var/log/messages or /var/log/syslog, and if you run "dmesg" it might be shown, too.
Steven
1) I can not find /var/ folder on USB stick???
2) Taking video is actually no so easy ...but I got it done.
3) To cut a long story short on the Samsung machine there are error messages that pop up complaining about "Secure Boot". Normally you can't see them because they flash of too quickly to read, with the video I could freeze the frame ( see attached frame print Secure_boot_error.png)).
So I thought.... lets turn off "Secure Boot " and see what happens. So I did!
Result : the "Secure Boot" error messages went away! Yay !... But sadly when the first Clonezilla screen came up it was again totally frozen just like before. No change.
I captured a number of screen prints which I have attached with all the messages produced as Clonezilla boots and then freezes. I would attach the video file but it is over 120MB and even then without freezing the screen you can not read the messages as they come and go too fast.
Just to make clear I am still using: clonezilla-live-2.7.3-19-amd64
Thanks
Stephen
Last edit: Stephen Leftly 2021-09-04
"1) I can not find /var/ folder on USB stick???" -> I meant after you boot Clonezilla live, you can enter command line prompt, then you should be able to find the /var/log/ dir.
Steven
That is the problem :Clonezilla freezes the laptop hard immediately. Keyboard , mouse etc totally frozen .
I can not do anything except a hard power off reset.
The only way to look at the contents of the USB stick is to boot into windows and search there. I searched the USB drive and no such file exists.
Thanks
Stephen
So you meant it was frozen like the photo "9_Option_screen_frozen_01.png"?
BTW, have you tried Clonezilla live 20210829-impish?
https://clonezilla.org/downloads.php
Any difference?
Steven