This is weird... There is no any modification about this in the live-config between these two versions.
How about other releases, like 20141208-utopic? http://clonezilla.org/downloads.php
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I hit enter, I get the "root@utopic:~#" prompt. At that prompt, I can type "exit" and clonezilla will finish booting. Running "date" from a command line prompt will display the correct time as local time.
After downloading other alternative stable versions, I found that none of the trusty or saucy versions that I tested would display local time. This included:
still works around the problem. It looks like the ocs_prerun gets executed before the "Start Clonezilla" menu and every time I exit from the command line back to the "Start Clonezilla" menu. There are no error messages when hwclock is run from ocs_prerun.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Adding "utc=no" as a boot parameter no longer reads the hwclock as localtime. The "utc=no" boot parameter worked correctly with 2.2.4-12-amd64.
This workaround will get the correct time for me:
utc=no timezone=America/Chicago ocs_prerun="hwclock -s --localtime"
Thank you for your work on Clonezilla.
This is weird... There is no any modification about this in the live-config between these two versions.
How about other releases, like 20141208-utopic?
http://clonezilla.org/downloads.php
Steven.
I had not used the alternative versions before.
The same thing happens with
clonezilla-live-20141208-utopic-amd64.iso
"utc=no timezone=America/Chicago" still reads the hwclock as UTC instead of local time.
One difference is that the workaround of adding:
ocs_prerun="hwclock -s --localtime"
causes the boot to stop at the command:
root@utopic:~# sudo locales tzdata keyboard-configuration upstart util-linux login openssh-server.
If I hit enter, I get the "root@utopic:~#" prompt. At that prompt, I can type "exit" and clonezilla will finish booting. Running "date" from a command line prompt will display the correct time as local time.
After downloading other alternative stable versions, I found that none of the trusty or saucy versions that I tested would display local time. This included:
clonezilla-live-20131029-saucy-amd64.iso
clonezilla-live-20131118-saucy-amd64.iso
clonezilla-live-20131125-saucy-amd64.iso
clonezilla-live-20140114-saucy-amd64.iso
clonezilla-live-20140331-saucy-amd64.iso
clonezilla-live-20140415-saucy-amd64.iso
clonezilla-live-20140518-trusty-amd64.iso
clonezilla-live-20140630-trusty-amd64.iso
clonezilla-live-20140915-trusty-amd64.iso
clonezilla-live-20141208-utopic-amd64.iso
I found that the last stable raring,
clonezilla-live-20130819-raring-amd64.iso
worked with "utc=no timezone=America/Chicago" and displayed the correct time.
Thanks for all the tests.
I will find some time to fix it next week.
Appreciate.
Steven.
Thanks for you quick work on this.
utc=no now works correctly with:
clonezilla-live-20141230-utopic-amd64.iso
clonezilla-live-20141230-vivid-amd64.iso
but fails with clonezilla-live-2.3.2-2-amd64.iso.
It has an error from hwclock during the boot.
The /var/log/live/config.log has this message in it:
and of course the time is still read as UTC.
Adding
ocs_prerun="hwclock -s --localtime"
still works around the problem. It looks like the ocs_prerun gets executed before the "Start Clonezilla" menu and every time I exit from the command line back to the "Start Clonezilla" menu. There are no error messages when hwclock is run from ocs_prerun.
Thanks. Yes, I confirmed this issue on Debian-based Clonezilla live.
I will try to fix it asap.
Steven.
@rja,
This issue has been fixed in Clonezilla live >= 2.3.2-5.
Could you please confirm this?
Thanks.
Steven.