clonezilla-live Mailing List for Clonezilla (Page 42)
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
clonezilla-live — Anything about Clonezilla live
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
(3) |
Apr
(5) |
May
(13) |
Jun
(6) |
Jul
(5) |
Aug
|
Sep
(12) |
Oct
(8) |
Nov
(9) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(9) |
Feb
(5) |
Mar
(16) |
Apr
(10) |
May
(2) |
Jun
(4) |
Jul
(22) |
Aug
(26) |
Sep
(8) |
Oct
(33) |
Nov
(25) |
Dec
(13) |
| 2009 |
Jan
(54) |
Feb
(65) |
Mar
(15) |
Apr
(12) |
May
(29) |
Jun
(46) |
Jul
(23) |
Aug
(71) |
Sep
(22) |
Oct
(13) |
Nov
(16) |
Dec
(65) |
| 2010 |
Jan
(18) |
Feb
(22) |
Mar
(26) |
Apr
(82) |
May
(36) |
Jun
(45) |
Jul
(40) |
Aug
(6) |
Sep
(44) |
Oct
(33) |
Nov
(8) |
Dec
(38) |
| 2011 |
Jan
(16) |
Feb
(13) |
Mar
(19) |
Apr
(27) |
May
(37) |
Jun
(14) |
Jul
(4) |
Aug
(2) |
Sep
(13) |
Oct
(5) |
Nov
(6) |
Dec
(6) |
| 2012 |
Jan
(6) |
Feb
(1) |
Mar
(36) |
Apr
(13) |
May
(4) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(5) |
Dec
(4) |
| 2013 |
Jan
(7) |
Feb
(6) |
Mar
(3) |
Apr
(5) |
May
(1) |
Jun
(8) |
Jul
(5) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2014 |
Jan
(12) |
Feb
(10) |
Mar
|
Apr
(2) |
May
(3) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(1) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2015 |
Jan
(13) |
Feb
(6) |
Mar
(2) |
Apr
(4) |
May
(15) |
Jun
(6) |
Jul
(20) |
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
(4) |
Dec
(1) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
(7) |
May
(1) |
Jun
(12) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(6) |
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(15) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(2) |
Oct
(6) |
Nov
(4) |
Dec
(4) |
| 2019 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(11) |
Dec
(2) |
| 2021 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(16) |
Jun
(3) |
Jul
(6) |
Aug
(13) |
Sep
|
Oct
|
Nov
(2) |
Dec
(1) |
| 2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
(4) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(9) |
Dec
(2) |
| 2024 |
Jan
(8) |
Feb
(1) |
Mar
|
Apr
(9) |
May
(2) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(7) |
Oct
(1) |
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(10) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
|
Dec
|
|
From: Zach B. <bil...@gm...> - 2010-02-03 16:40:23
|
-------CUT BEGIN HERE-------------------------------------------- Description of problem: When client boots on etherboot it will boot up part way and then error and say that it "failed to mount root filesystem". I do not believe that any of the given cases are the cause. Except maybe the network card driver. I had an issue with the network card when using Clonezilla Live but it was resolved in using the unstable version. Could that be the same case here? How reproducible: Every time the client boots using etherboot Steps to Reproduce: boot the client using etherboot Actual results: error message "Failed to mount root filesystem!!" Expected results: Should boot into Clonezilla to be able to image the hard drive. Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!): === OS version: Ubuntu 9.10 Server arch: i686 Server CPU: Intel(R) Pentium(R) 4 CPU 3.40GHz Server memory size: 3095216 kB Server Kernel version: 2.6.31-17-generic Installed DRBL-related packages: drbl-1.9.5-42 clonezilla-2.3.4-54 $ Client kernel version: 2.6.31-17-386 Client kernel arch: i486 NICs with private IP address in server: Private IP address in server: Total client no: 12 Client IP address: 131.212.24.1 131.212.24.10 131.212.24.11 131.212.$ === -------CUT END HERE---------------------------------------------- Zach Biles |
|
From: Steven S. <st...@nc...> - 2010-01-28 23:52:17
|
Hi James, James Dutton wrote: > My system configuration: > HP DX2250 Box > AMD Athlon 64x2 Dual Core Processor 4000+ > Dual 80GB Hard Drives > Windows XP PRO on Drive 0 > Fedora 12 on Drive 1 > No Dual Boot - Boot using F9 Boot Menu > No Floppy Drive > > Here is some feedback on my experience with three of the latest > Clonezilla releases (2-31, 3-24, 3-27). I am going to stay with > Clonezilla 2-31 for now. I have used it many times to copy and > restore my hard drive image with no apparent problems It’s only > problem is encountered during “restore” of the image copy to the > original hard drive. It falls all over it’s self trying to resolve a > “boot record” issue and the lack of a floppy drive. It hangs and a > power down is necessary to exit the situation. > > I have tried both Clonezilla 3-24 and 3-27. Both releases have the > same problem prior to image copying the original hard drive. At a > certain point in the process there is a rolling screen of repetitive > error messages (the same message is repeated over and over many > unknown times). I do not see these error messages in release 2-31. > The “Scroll Lock” and “Pause/Break” keys are ineffective and the > subsequent messages are sufficient in number to roll the last > iteration of the error message off the screen. Due to this, I am > hesitant to rely on either version for an accurate image copy. Also > release 3-27 has a significant problem at the end of the image copy > process. When the image copy finished I entered “3” to terminate the > task. It went into a non interruptible loop with a single line > message flooding a rolling screen, which required a power down to exit > the situation. Maybe a future release will include certain keyboard > interrupt handling to support better diagnostics/reporting of certain > error situations. > Thanks for this feedback. Could you give clonezilla live 20100121-karmic a try? We will see if any difference between these. Please report the results. Thanks. Steven. > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: James D. <jdu...@gm...> - 2010-01-27 16:11:10
|
My system configuration: HP DX2250 Box AMD Athlon 64x2 Dual Core Processor 4000+ Dual 80GB Hard Drives Windows XP PRO on Drive 0 Fedora 12 on Drive 1 No Dual Boot - Boot using F9 Boot Menu No Floppy Drive Here is some feedback on my experience with three of the latest Clonezilla releases (2-31, 3-24, 3-27). I am going to stay with Clonezilla 2-31 for now. I have used it many times to copy and restore my hard drive image with no apparent problems It’s only problem is encountered during “restore” of the image copy to the original hard drive. It falls all over it’s self trying to resolve a “boot record” issue and the lack of a floppy drive. It hangs and a power down is necessary to exit the situation. I have tried both Clonezilla 3-24 and 3-27. Both releases have the same problem prior to image copying the original hard drive. At a certain point in the process there is a rolling screen of repetitive error messages (the same message is repeated over and over many unknown times). I do not see these error messages in release 2-31. The “Scroll Lock” and “Pause/Break” keys are ineffective and the subsequent messages are sufficient in number to roll the last iteration of the error message off the screen. Due to this, I am hesitant to rely on either version for an accurate image copy. Also release 3-27 has a significant problem at the end of the image copy process. When the image copy finished I entered “3” to terminate the task. It went into a non interruptible loop with a single line message flooding a rolling screen, which required a power down to exit the situation. Maybe a future release will include certain keyboard interrupt handling to support better diagnostics/reporting of certain error situations. |
|
From: Steven S. <st...@nc...> - 2010-01-26 15:25:16
|
Duplicated post. Let's focus on this: https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3527055/index/page/1 Thanks. Steven. Petr Matula wrote: > Clonezilla 1.2.3-27 don't read top level directories from disk on RAID1(linux software raid). Disk probably is not mounted for unknown fs type linux_raid_ member. > > Before version 1.2.3-5 t disks from RAID1 was mountable and readeble as /dev/sda1.. > -------------- > > Petr Matula > pe...@se... > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Petr M. <pe...@se...> - 2010-01-22 14:23:22
|
Clonezilla 1.2.3-27 don't read top level directories from disk on RAID1(linux software raid). Disk probably is not mounted for unknown fs type linux_raid_ member. Before version 1.2.3-5 t disks from RAID1 was mountable and readeble as /dev/sda1.. -------------- Petr Matula pe...@se... |
|
From: Steven S. <st...@nc...> - 2010-01-14 01:07:44
|
Do you have any problem to follow the link on http://clonezilla.org/download/sourceforge/ to get the checksum? The sums are: MD5SUMS f16f2c08df81af7b333b9613b2512af5 clonezilla-live-1.2.3-24.iso f16f2c08df81af7b333b9613b2512af5 clonezilla-live.iso e3b601bce510334074fd4aaaabb8965f clonezilla-live-1.2.3-24.zip e3b601bce510334074fd4aaaabb8965f clonezilla-live.zip SHA1SUMS 5cf8e147e485d1facfd966799d8efd67b076ebc3 clonezilla-live-1.2.3-24.iso 5cf8e147e485d1facfd966799d8efd67b076ebc3 clonezilla-live.iso c2f9a6e41aaee535158ebd82faa205a738f674f3 clonezilla-live-1.2.3-24.zip c2f9a6e41aaee535158ebd82faa205a738f674f3 clonezilla-live.zip Steven. On 2010/1/14 上午 12:56, James Dutton wrote: > I have Google searched the internet and cannot fine the md5sum for > this release. Does anyone know where it can be found? > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > |
|
From: James D. <jdu...@gm...> - 2010-01-13 16:56:38
|
I have Google searched the internet and cannot fine the md5sum for this release. Does anyone know where it can be found? |
|
From: Steven S. <st...@nc...> - 2010-01-12 15:21:40
|
Hi everybody, We are happy to announce that clonezilla-live 1.2.3-24 is the new stable release. This release features some new functions, some new programs included, and some bugs were fixed. * The underlying GNU/Linux operating system was upgraded. This release is based on the Debian Sid repository (as of 2010/Jan/08). Linux kernel 2.6.32-4 is used. * Updated partclone to 0.1.9-5, live-initramfs to 1.157.4-10drbl, syslinux to 3.84. * Pakcages wpasupplicant, bind9-host and cdrdao were added. * Language files were updated. Thanks to Juan Ramon Martinez, Alex Ibanez Lopez ,Jean-Francois Nifenecker, Gianfranco Gentili, Annie Wei, Akira YOSHIYAMA and Zhiqiang Zhang. * New features: * A boot parameter ocs_live_run_tty was added. It is used to assign the tty to run ocs_live_run. By default tty1 is used. * An option to ignore CRC checking of partclone was added. * Now clonezilla live iso supports grub2 iso loopback boot. Check Clonezilla website for how to edit your grub2 config file for this function. * Boot menu is more compact now. * The Clonezilla theme of usplash was added. However, it's not on by default. It can be turned on by adding "quiet splash" in the boot parameters. * The lspci results will be saved when saving an image. Thanks to Acty Chen for this idea. * Bugs fixed: * The 2 instances of ocs_live_run running in tty1 and ttyS0 issue was fixed. Now by default ocs_live_run will only be run on tty1 only. No more both on tty1 and ttyS0. If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter. Ref: https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3499579. Thanks to lukas666 for this bug report. * Boot parameter live-netdev was not working. * I386 version of OS running grub-install for the x86-64 restored OS was fixed. Thanks to John Ouzts <jouzts _at_ gmail com> and Lukasz I. <physik _at_ poczta onet pl> for tihs bug report. * A bug about using tar to create recovery Clonezilla live was fixed. Thanks to wellurs for this bug report. * A bug about scripts in $OCS_PRERUN_DIR won't run was fixed. Thanks to gsusterman for this bug report. * A bug about creating recovery iso/zip with images not in /home/partimag was fixed. Thanks to dersucker for this bug report. Steven. -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Steven S. <st...@nc...> - 2010-01-12 00:55:31
|
Thanks for the bug report. It's a harmless bug actually: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513216 Steven. On 2010/1/12 上午 03:16, James Dutton wrote: > I have tried to find via Google a place to report this potential > clonezilla bug. If this is the wrong place please let me know where I > can report this. > > HP DX2250 Box > AMD Athlon 64x2 Dual Core Processor 4000+ > Dual 80GB Hard Drives > Windows XP PRO on Drive 0 > Fedora 12 on Drive 1 > No Dual Boot - Boot using F9 Boot Menu > No Floppy Drive > clonezilla-live-1.2.2-31.iso > > The image copy from the Fedora 12 hard drive goes well and Clonezilla > executes properly - as expected - with no errors. The image copy from > the USB external hard drive goes well and Clonezilla executes properly > - as expected - except during the final stage of the process. After > the image copy is complete the following messages are produced and the > process does not terminate gracefully. I have seen this situation at > the end of every image restore. There is no difference when the target > hard drive is formatted with one NTFS partition or if it contains a > bootable Fedora 12 system. The problem does not have any apparent > effect on usage of the Fedora 12 system after the image restore. > ------------------------------------------------------------------------------------------------------------------------------- > (normal processing messages followed by this message): > > there is a separate boot partition in target device. trying to mount > root partition for grub-install to work with that ... > > (then messages pertaining to device allocation are issued followed by > these messages): > > grub-probe: error: cannot open '/boot/grub/device.map/' > /usr/sbin/grub-install :line 374: [: =: unary operator expected > > (activity stops - no further messages - keyboard input has no effect - > must power down to exit situation) > > -------------------------------------------------------------------------------------------------------------------------- > > Here is the source code surrounding line 374 in grub-install: > > 369 --root-directory=*) > 370 rootdir=`echo "$option" | sed 's/--root-directory=//'` ;; > 371 --grub-shell=*) > 372 grub_shell=`echo "$option" | sed 's/--grub-shell=//'` ;; > 373 --no-floppy) > 374 no_floppy="--no-floppy" ;; > 375 --force-lba) > 376 force_lba="--force-lba" ;; > 377 --recheck) > 378 recheck=yes ;; > 379 --just-copy) > 380 justcopy=yes ;; > 381 # This is an undocumented feature... > 382 --debug) > 383 debug=yes ;; > 384 -*) > 385 echo "Unrecognized option \`$option'" 1>&2 > 386 usage > 387 exit 1 > 388 ;; > 389 *) > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: scar <sc...@dr...> - 2010-01-11 21:49:44
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 hi, i tried using the same USB stick, with 1.2.2-31 on it, in another, newer laptop, and it worked fine with the default boot option (top choice, 1024x768...) so apparently it was just a problem with the older laptop. -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAktLnNEACgkQXhfCJNu98qB1TQCdEpYcODo6N9GVK9eGbGcoQpIt jjAAoOy6Hm8zmy7G6N8UucAcHFS3Cobp =t14F -----END PGP SIGNATURE----- |
|
From: James D. <jdu...@gm...> - 2010-01-11 19:16:52
|
I have tried to find via Google a place to report this potential clonezilla bug. If this is the wrong place please let me know where I can report this. HP DX2250 Box AMD Athlon 64x2 Dual Core Processor 4000+ Dual 80GB Hard Drives Windows XP PRO on Drive 0 Fedora 12 on Drive 1 No Dual Boot - Boot using F9 Boot Menu No Floppy Drive clonezilla-live-1.2.2-31.iso The image copy from the Fedora 12 hard drive goes well and Clonezilla executes properly - as expected - with no errors. The image copy from the USB external hard drive goes well and Clonezilla executes properly - as expected - except during the final stage of the process. After the image copy is complete the following messages are produced and the process does not terminate gracefully. I have seen this situation at the end of every image restore. There is no difference when the target hard drive is formatted with one NTFS partition or if it contains a bootable Fedora 12 system. The problem does not have any apparent effect on usage of the Fedora 12 system after the image restore. ------------------------------------------------------------------------------------------------------------------------------- (normal processing messages followed by this message): there is a separate boot partition in target device. trying to mount root partition for grub-install to work with that ... (then messages pertaining to device allocation are issued followed by these messages): grub-probe: error: cannot open '/boot/grub/device.map/' /usr/sbin/grub-install :line 374: [: =: unary operator expected (activity stops - no further messages - keyboard input has no effect - must power down to exit situation) -------------------------------------------------------------------------------------------------------------------------- Here is the source code surrounding line 374 in grub-install: 369 --root-directory=*) 370 rootdir=`echo "$option" | sed 's/--root-directory=//'` ;; 371 --grub-shell=*) 372 grub_shell=`echo "$option" | sed 's/--grub-shell=//'` ;; 373 --no-floppy) 374 no_floppy="--no-floppy" ;; 375 --force-lba) 376 force_lba="--force-lba" ;; 377 --recheck) 378 recheck=yes ;; 379 --just-copy) 380 justcopy=yes ;; 381 # This is an undocumented feature... 382 --debug) 383 debug=yes ;; 384 -*) 385 echo "Unrecognized option \`$option'" 1>&2 386 usage 387 exit 1 388 ;; 389 *) |
|
From: Steven S. <st...@nc...> - 2010-01-11 15:00:25
|
Hi, Since you have asked the same question in the forum: https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3512761 So let focus on the one in the forum. Steven. Gilles wrote: > Hello > > I recently started using the www.partedmagic.com Linux live CD > because it lets me manage partitions and save/restore partition > images using the Clonezilla live CD. > > I'm using CloneZilla on a test host, the active OS is installed in > sda1, and sda2 is where I save images, ie. /dev/partimage. > > After trying out Windows7, I restored an XPSP3 image, but I get the > following error message when rebooting: > > "Reboot and select proper boot device" > > Could it be that Clonezilla didn't save/restore the MBR? Gparted > didn't let me set a partition as "active", so it could also be this, > but I have no idea. > > Thank you for any help. > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Steven S. <st...@nc...> - 2010-01-11 14:28:57
|
scar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Steven Shiau @ 01/07/2010 12:55 AM: > >> I am afraid that now Clonezilla live is larger than 115 MB roughly... so >> it might not fit 128 USB flash drive... >> > > sorry, i'm not sure what you mean, because 1.2.3-23 and 1.2.2-31 both > fit on a 128 MB flash drive. > Please forget about that. BTW, Did you try to use "ToRAM" option? Steven. > -----BEGIN PGP SIGNATURE----- > > iEYEAREIAAYFAktH+JEACgkQXhfCJNu98qCZ9gCeKxNUuXMWVBz4sNllvvV0Tn9X > M7gAn0D8bo2knzd/cVxlNouxii6l+smM > =RMTJ > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Gilles <cod...@fr...> - 2010-01-09 20:38:38
|
Hello I recently started using the www.partedmagic.com Linux live CD because it lets me manage partitions and save/restore partition images using the Clonezilla live CD. I'm using CloneZilla on a test host, the active OS is installed in sda1, and sda2 is where I save images, ie. /dev/partimage. After trying out Windows7, I restored an XPSP3 image, but I get the following error message when rebooting: "Reboot and select proper boot device" Could it be that Clonezilla didn't save/restore the MBR? Gparted didn't let me set a partition as "active", so it could also be this, but I have no idea. Thank you for any help. |
|
From: scar <sc...@dr...> - 2010-01-09 03:32:09
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Steven Shiau @ 01/07/2010 12:55 AM: > I am afraid that now Clonezilla live is larger than 115 MB roughly... so > it might not fit 128 USB flash drive... sorry, i'm not sure what you mean, because 1.2.3-23 and 1.2.2-31 both fit on a 128 MB flash drive. -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAktH+JEACgkQXhfCJNu98qCZ9gCeKxNUuXMWVBz4sNllvvV0Tn9X M7gAn0D8bo2knzd/cVxlNouxii6l+smM =RMTJ -----END PGP SIGNATURE----- |
|
From: Steven S. <st...@nc...> - 2010-01-07 07:53:53
|
I am afraid that now Clonezilla live is larger than 115 MB roughly... so it might not fit 128 USB flash drive... Sorry for that. Steven. scar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Steven Shiau @ 01/05/2010 08:12 AM: > >> Maybe the problem is the kernel does not support your USB flash drive >> very well, or maybe there is a hardware issue about your USB flash drive. >> Did you try different USB flash drive? Or did you try different versions >> of Clonezilla live, e.g. 1.2.3-23 or 20091230-karmic? >> > > thank you for the suggestions. i did try 1.2.3-23 and obtained similar > results, except that the repeating messages included an error like > "unable to access /dev/sda". i attempted to try 20091230-karmic but it > was just a bit too large to fit on to the stick. i tried a different, > 2.0 GB stick with 1.2.2-31 and it booted fine and i was able to start > clonezilla. > > it would be nice if i could get the 128 MB stick to work. is it > possible? what kind of information is needed to find out? > > thanks. > -----BEGIN PGP SIGNATURE----- > > iEYEAREIAAYFAktEJpAACgkQXhfCJNu98qDl9wCeJF0pm/kIA8xgZ0yL1D99uW1X > CfwAniLfgQ0greK3zw96b8FIh+nokYPV > =OQqz > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: scar <sc...@dr...> - 2010-01-06 05:59:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Steven Shiau @ 01/05/2010 08:12 AM: > Maybe the problem is the kernel does not support your USB flash drive > very well, or maybe there is a hardware issue about your USB flash drive. > Did you try different USB flash drive? Or did you try different versions > of Clonezilla live, e.g. 1.2.3-23 or 20091230-karmic? thank you for the suggestions. i did try 1.2.3-23 and obtained similar results, except that the repeating messages included an error like "unable to access /dev/sda". i attempted to try 20091230-karmic but it was just a bit too large to fit on to the stick. i tried a different, 2.0 GB stick with 1.2.2-31 and it booted fine and i was able to start clonezilla. it would be nice if i could get the 128 MB stick to work. is it possible? what kind of information is needed to find out? thanks. -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAktEJpAACgkQXhfCJNu98qDl9wCeJF0pm/kIA8xgZ0yL1D99uW1X CfwAniLfgQ0greK3zw96b8FIh+nokYPV =OQqz -----END PGP SIGNATURE----- |
|
From: Steven S. <st...@nc...> - 2010-01-05 15:13:13
|
Maybe the problem is the kernel does not support your USB flash drive very well, or maybe there is a hardware issue about your USB flash drive. Did you try different USB flash drive? Or did you try different versions of Clonezilla live, e.g. 1.2.3-23 or 20091230-karmic? Steven. scar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > hi all, > > i have tried out CloneZilla live today for the first time. i grabbed > 1.2.2-31. i was hoping to use an old 128 MB USB stick for this purpose, > but it seems to get stuck in a loop after booting. the menu comes up > fine, and i choose the default choice. then, after some seconds i am > getting these errors repeating over and over every second: > > NTFS volume version 3.1 > FAT utf8 is not a recommended IO character set for FAT filesystems, > filesystem will be case sensitive > > at the same time i can hear the hard disk being accessed every second. > > then, after about a minute, a message saying a failure to boot the live > image. > > i then tried using the live CD and all went well. anyone know what the > problem with USB is? > > thanks > -----BEGIN PGP SIGNATURE----- > > iEYEAREIAAYFAktC6TcACgkQXhfCJNu98qDSjQCgs4uI2IeMDhX+75Fd9M9BVUJY > G3oAoN53wz0jsVT4B/cqwqWql52DoeDa > =L4Ut > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: scar <sc...@dr...> - 2010-01-05 07:45:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 hi all, i have tried out CloneZilla live today for the first time. i grabbed 1.2.2-31. i was hoping to use an old 128 MB USB stick for this purpose, but it seems to get stuck in a loop after booting. the menu comes up fine, and i choose the default choice. then, after some seconds i am getting these errors repeating over and over every second: NTFS volume version 3.1 FAT utf8 is not a recommended IO character set for FAT filesystems, filesystem will be case sensitive at the same time i can hear the hard disk being accessed every second. then, after about a minute, a message saying a failure to boot the live image. i then tried using the live CD and all went well. anyone know what the problem with USB is? thanks -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAktC6TcACgkQXhfCJNu98qDSjQCgs4uI2IeMDhX+75Fd9M9BVUJY G3oAoN53wz0jsVT4B/cqwqWql52DoeDa =L4Ut -----END PGP SIGNATURE----- |
|
From: Steven S. <st...@nc...> - 2009-12-30 14:16:05
|
Santiago Bruno wrote: > On Wed, Dec 30, 2009 at 5:35 AM, Steven Shiau <st...@nc...> wrote: > >> On 2009/12/29 上午 01:31, Santiago Bruno wrote: >> >>> On Sat, Dec 26, 2009 at 8:24 AM, Steven Shiau<st...@nc...> wrote: >>> >>>> Santiago Bruno wrote: >>>> >>>>> On Thu, Dec 24, 2009 at 4:46 AM, Steven Shiau<st...@nc...> >>>>> wrote: >>>>> >>>>> >>>>>> Santiago Bruno wrote: >>>>>> >>>>>> >>>>>>> On Wed, Dec 23, 2009 at 11:59 AM, Steven Shiau<st...@nc...> >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>>> Santiago Bruno wrote: >>>>>>>> >>>>>>>> >>>>>>>>> On Mon, Dec 14, 2009 at 4:47 AM, Steven Shiau<st...@nc...> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> Thanks for the bug reports. I reply your question sin the >>>>>>>>>> following. >>>>>>>>>> >>>>>>>>>> Santiago Bruno wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> I'm trying to use Clonezilla live in a machine that will boot >>>>>>>>>>> using >>>>>>>>>>> PXE through its interface eth1. This machine can redirect the >>>>>>>>>>> console >>>>>>>>>>> using Serial over Lan with its own hardware and is configured to >>>>>>>>>>> do >>>>>>>>>>> so. >>>>>>>>>>> >>>>>>>>>>> I added live-getty and console=ttyS0,115200n8 to the kernel >>>>>>>>>>> command >>>>>>>>>>> line but I'm having a strange problem. >>>>>>>>>>> >>>>>>>>>>> When I'm looking at the serial console, after booting clonezilla, >>>>>>>>>>> there is output at the console as expected, but some output also >>>>>>>>>>> goes >>>>>>>>>>> to the VGA. And it's not the same output. Is like there are two >>>>>>>>>>> different clonezilla instances in tty1 and ttyS0. They even start >>>>>>>>>>> cloning the same partitions at diferent times messing all up. At >>>>>>>>>>> the >>>>>>>>>>> end one can go to the command line on both consoles and evidently >>>>>>>>>>> they >>>>>>>>>>> are two different processes. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> How did you configure your clonezilla live ? Please show us the >>>>>>>>>> config >>>>>>>>>> files, e.g. syslinux.cfg... So it's easier for me to reproduce the >>>>>>>>>> problem >>>>>>>>>> then we can fix this problem. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> Well, I'm using some custom scripts, but now I reduced the >>>>>>>>> configuration to try to use a script that does not exists to see if >>>>>>>>> the problem still happened so it could be easier to reproduce. >>>>>>>>> >>>>>>>>> The pxe file for the machine would be like this: >>>>>>>>> >>>>>>>>> default Clonezilla >>>>>>>>> label Clonezilla >>>>>>>>> kernel /clonezilla/vmlinuz >>>>>>>>> append initrd=/clonezilla/initrd.img boot=live live-getty >>>>>>>>> console=ttyS0,115200n8 union=aufs noswap noprompt nosplash >>>>>>>>> live-netdev="eth1" >>>>>>>>> fetch=tftp://<SERVER_IP>/clonezilla/filesystem.squashfs >>>>>>>>> ocs_live_keymap="NONE" ocs_live_batch="yes" ocs_lang="en_US.UTF-8" >>>>>>>>> ocs_live_run="/blablablabla" >>>>>>>>> >>>>>>>>> and what happens when booting is the following. >>>>>>>>> >>>>>>>>> VGA starts displaying the pxe boot, "Decompressing Linux..." >>>>>>>>> decompressing the initrd, and the last lines are >>>>>>>>> "Ready >>>>>>>>> Probing EDD (...) ok" >>>>>>>>> >>>>>>>>> It stops there, and then, text starts coming out through ttyS0 >>>>>>>>> instead. squashfs is decompressed, init starts, I can see that it >>>>>>>>> tries to set up eth0 through dhcp because I see some >>>>>>>>> "DHCPDISCOVER..." >>>>>>>>> lines until it times out. >>>>>>>>> Then I think it sets up eth1 very fast and then the problem starts. >>>>>>>>> I think it is when the ocs scripts begin executing. >>>>>>>>> The VGA changes from the typical console text to another font, >>>>>>>>> probably a framebuffer, and some scripts begin executing both in >>>>>>>>> tty1 >>>>>>>>> and ttyS0 >>>>>>>>> obviously they fail inmediately because there is no blablablabla >>>>>>>>> script, but I get the prompt to select what to do next in both >>>>>>>>> terminals and they are different processes. >>>>>>>>> If I type "tty" one gives /dev/tty1 and the other /dev/ttyS0. >>>>>>>>> I would expect that everything happens in ttyS0 if I specified >>>>>>>>> console=ttyS0 on the command line, or to have an option to do that. >>>>>>>>> Is >>>>>>>>> it possible? I would expect in that case to keep tty1 blocked or in >>>>>>>>> a >>>>>>>>> login prompt. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> Yes. Here I think the best solution is in your customized script, add >>>>>>>> one >>>>>>>> line in the beginning: >>>>>>>> ================================ >>>>>>>> [ "$(tty)" != "/dev/ttyS0" ]&& exit 1 >>>>>>>> ================================ >>>>>>>> >>>>>>>> Then the rest of your script will only be run in the /dev/ttyS0. >>>>>>>> >>>>>>>> Hope this helps. >>>>>>>> >>>>>>>> >>>>>>> Yes, I considered implementing exactly that workaround. The only >>>>>>> problem is that I will be using the script as part of a bigger system >>>>>>> with an user interface where the user may choose to redirect the >>>>>>> output or not. So I will have two different customized scripts, one >>>>>>> for redirecting and another for not redirecting, and selecting which >>>>>>> script to use through the generated pxe config file. >>>>>>> I thought of reporting the problem so I had to work less :P >>>>>>> But this should work. >>>>>>> >>>>>>> Thank you! >>>>>>> >>>>>>> Santiago. >>>>>>> >>>>>>> >>>>>> Another possibility is we can implement another ocs option to force >>>>>> $ocs_live_run to be run in specific tty, e.g. ttyS0. Now it will be run >>>>>> in >>>>>> tty1 and ttyS0. >>>>>> E.g. with boot parameter >>>>>> ocs_live_tty="/dev/ttyS0" >>>>>> then the $ocs_live_run will be run in ttyS0 only. Not in tty1. >>>>>> >>>>>> This should work. Or maybe you have better idea? >>>>>> >>>>>> >>>>> That would be something nice to have. I have no other idea. But I >>>>> don´t know how complicated it will be to implement it. I can live with >>>>> the workaround you suggested ;) >>>>> But let me know if you implement it in some future release or if I can >>>>> help in some way, like testing. >>>>> >>>>> Cheers, >>>>> >>>>> Santiago. >>>>> >>>>> >>>> I have uploaded Clonezilla live 1.2.3-21 in the testing branch. A boot >>>> parameter "ocs_live_run_tty" was added for this purpose. Please refer to >>>> >>>> http://clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc >>>> for how to use it. >>>> >>>> Please let us know the results if you test that. >>>> Thanks. >>>> >>> I've just integrated this new release of clonezilla to my system and >>> I'm using the new boot parameter when console redirection is selected. >>> I did some tests redirecting and not redirecting and it is working as >>> I expected on the first time. Everything looks good so far. I will let >>> you know if I find any problem later but it seems to be working great! >>> Thanks for your work! >>> >>> Santiago. >>> >> Santiago, >> Due to an issue >> (https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3499579) >> we have to change this again. Now by default the clonezilla command will be >> run on /dev/tty1 only. If you want to use /dev/ttyS0, you can assign >> "live-getty console=ttyS0,115200n81" and it will be run on /dev/ttyS0 only. >> For more info, please check the changelog: >> http://free.nchc.org.tw/clonezilla-live/experimental/ubuntu-based/ChangeLog-Clonezilla-live.txt >> or >> http://clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc >> >> I believe this change should make things easier and better. If you have any >> thought or suggestion, please let us know. >> >> Please test it again and let us know the results. >> Thanks again. >> > > Well, I did a couple of tests with the new version and everything > seems to be working as I expected on the first time. So, the > ocs_live_run_tty boot parameter (at least in my case) isn't needed > anymore? I just need to add or remove "live-getty > console=ttyS0,115200n81" to redirect? That is what I did and it > worked. What is ocs_live_run_tty used for now? > Basically you are correct. In your case, ocs_live_run_tty is not required. However, if someone would like to run in tty2, for example, although it's very rare... ocs_live_run_tty provides such a possibility... And since we have implemented it, to keep it is not a bad idea I think. This makes Clonezilla live more flexible. :) Steven. > Thanks, > > Santiago. > -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Santiago B. <san...@gm...> - 2009-12-30 14:06:40
|
On Wed, Dec 30, 2009 at 5:35 AM, Steven Shiau <st...@nc...> wrote: > > > On 2009/12/29 上午 01:31, Santiago Bruno wrote: >> >> On Sat, Dec 26, 2009 at 8:24 AM, Steven Shiau<st...@nc...> wrote: >>> >>> >>> Santiago Bruno wrote: >>>> >>>> On Thu, Dec 24, 2009 at 4:46 AM, Steven Shiau<st...@nc...> >>>> wrote: >>>> >>>>> >>>>> Santiago Bruno wrote: >>>>> >>>>>> >>>>>> On Wed, Dec 23, 2009 at 11:59 AM, Steven Shiau<st...@nc...> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> Santiago Bruno wrote: >>>>>>> >>>>>>>> >>>>>>>> On Mon, Dec 14, 2009 at 4:47 AM, Steven Shiau<st...@nc...> >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> Thanks for the bug reports. I reply your question sin the >>>>>>>>> following. >>>>>>>>> >>>>>>>>> Santiago Bruno wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I'm trying to use Clonezilla live in a machine that will boot >>>>>>>>>> using >>>>>>>>>> PXE through its interface eth1. This machine can redirect the >>>>>>>>>> console >>>>>>>>>> using Serial over Lan with its own hardware and is configured to >>>>>>>>>> do >>>>>>>>>> so. >>>>>>>>>> >>>>>>>>>> I added live-getty and console=ttyS0,115200n8 to the kernel >>>>>>>>>> command >>>>>>>>>> line but I'm having a strange problem. >>>>>>>>>> >>>>>>>>>> When I'm looking at the serial console, after booting clonezilla, >>>>>>>>>> there is output at the console as expected, but some output also >>>>>>>>>> goes >>>>>>>>>> to the VGA. And it's not the same output. Is like there are two >>>>>>>>>> different clonezilla instances in tty1 and ttyS0. They even start >>>>>>>>>> cloning the same partitions at diferent times messing all up. At >>>>>>>>>> the >>>>>>>>>> end one can go to the command line on both consoles and evidently >>>>>>>>>> they >>>>>>>>>> are two different processes. >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> How did you configure your clonezilla live ? Please show us the >>>>>>>>> config >>>>>>>>> files, e.g. syslinux.cfg... So it's easier for me to reproduce the >>>>>>>>> problem >>>>>>>>> then we can fix this problem. >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> Well, I'm using some custom scripts, but now I reduced the >>>>>>>> configuration to try to use a script that does not exists to see if >>>>>>>> the problem still happened so it could be easier to reproduce. >>>>>>>> >>>>>>>> The pxe file for the machine would be like this: >>>>>>>> >>>>>>>> default Clonezilla >>>>>>>> label Clonezilla >>>>>>>> kernel /clonezilla/vmlinuz >>>>>>>> append initrd=/clonezilla/initrd.img boot=live live-getty >>>>>>>> console=ttyS0,115200n8 union=aufs noswap noprompt nosplash >>>>>>>> live-netdev="eth1" >>>>>>>> fetch=tftp://<SERVER_IP>/clonezilla/filesystem.squashfs >>>>>>>> ocs_live_keymap="NONE" ocs_live_batch="yes" ocs_lang="en_US.UTF-8" >>>>>>>> ocs_live_run="/blablablabla" >>>>>>>> >>>>>>>> and what happens when booting is the following. >>>>>>>> >>>>>>>> VGA starts displaying the pxe boot, "Decompressing Linux..." >>>>>>>> decompressing the initrd, and the last lines are >>>>>>>> "Ready >>>>>>>> Probing EDD (...) ok" >>>>>>>> >>>>>>>> It stops there, and then, text starts coming out through ttyS0 >>>>>>>> instead. squashfs is decompressed, init starts, I can see that it >>>>>>>> tries to set up eth0 through dhcp because I see some >>>>>>>> "DHCPDISCOVER..." >>>>>>>> lines until it times out. >>>>>>>> Then I think it sets up eth1 very fast and then the problem starts. >>>>>>>> I think it is when the ocs scripts begin executing. >>>>>>>> The VGA changes from the typical console text to another font, >>>>>>>> probably a framebuffer, and some scripts begin executing both in >>>>>>>> tty1 >>>>>>>> and ttyS0 >>>>>>>> obviously they fail inmediately because there is no blablablabla >>>>>>>> script, but I get the prompt to select what to do next in both >>>>>>>> terminals and they are different processes. >>>>>>>> If I type "tty" one gives /dev/tty1 and the other /dev/ttyS0. >>>>>>>> I would expect that everything happens in ttyS0 if I specified >>>>>>>> console=ttyS0 on the command line, or to have an option to do that. >>>>>>>> Is >>>>>>>> it possible? I would expect in that case to keep tty1 blocked or in >>>>>>>> a >>>>>>>> login prompt. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Yes. Here I think the best solution is in your customized script, add >>>>>>> one >>>>>>> line in the beginning: >>>>>>> ================================ >>>>>>> [ "$(tty)" != "/dev/ttyS0" ]&& exit 1 >>>>>>> ================================ >>>>>>> >>>>>>> Then the rest of your script will only be run in the /dev/ttyS0. >>>>>>> >>>>>>> Hope this helps. >>>>>>> >>>>>> >>>>>> Yes, I considered implementing exactly that workaround. The only >>>>>> problem is that I will be using the script as part of a bigger system >>>>>> with an user interface where the user may choose to redirect the >>>>>> output or not. So I will have two different customized scripts, one >>>>>> for redirecting and another for not redirecting, and selecting which >>>>>> script to use through the generated pxe config file. >>>>>> I thought of reporting the problem so I had to work less :P >>>>>> But this should work. >>>>>> >>>>>> Thank you! >>>>>> >>>>>> Santiago. >>>>>> >>>>> >>>>> Another possibility is we can implement another ocs option to force >>>>> $ocs_live_run to be run in specific tty, e.g. ttyS0. Now it will be run >>>>> in >>>>> tty1 and ttyS0. >>>>> E.g. with boot parameter >>>>> ocs_live_tty="/dev/ttyS0" >>>>> then the $ocs_live_run will be run in ttyS0 only. Not in tty1. >>>>> >>>>> This should work. Or maybe you have better idea? >>>>> >>>> >>>> That would be something nice to have. I have no other idea. But I >>>> don´t know how complicated it will be to implement it. I can live with >>>> the workaround you suggested ;) >>>> But let me know if you implement it in some future release or if I can >>>> help in some way, like testing. >>>> >>>> Cheers, >>>> >>>> Santiago. >>>> >>> >>> I have uploaded Clonezilla live 1.2.3-21 in the testing branch. A boot >>> parameter "ocs_live_run_tty" was added for this purpose. Please refer to >>> >>> http://clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc >>> for how to use it. >>> >>> Please let us know the results if you test that. >>> Thanks. >> >> I've just integrated this new release of clonezilla to my system and >> I'm using the new boot parameter when console redirection is selected. >> I did some tests redirecting and not redirecting and it is working as >> I expected on the first time. Everything looks good so far. I will let >> you know if I find any problem later but it seems to be working great! >> Thanks for your work! >> >> Santiago. > > Santiago, > Due to an issue > (https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3499579) > we have to change this again. Now by default the clonezilla command will be > run on /dev/tty1 only. If you want to use /dev/ttyS0, you can assign > "live-getty console=ttyS0,115200n81" and it will be run on /dev/ttyS0 only. > For more info, please check the changelog: > http://free.nchc.org.tw/clonezilla-live/experimental/ubuntu-based/ChangeLog-Clonezilla-live.txt > or > http://clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc > > I believe this change should make things easier and better. If you have any > thought or suggestion, please let us know. > > Please test it again and let us know the results. > Thanks again. Well, I did a couple of tests with the new version and everything seems to be working as I expected on the first time. So, the ocs_live_run_tty boot parameter (at least in my case) isn't needed anymore? I just need to add or remove "live-getty console=ttyS0,115200n81" to redirect? That is what I did and it worked. What is ocs_live_run_tty used for now? Thanks, Santiago. |
|
From: Steven S. <st...@nc...> - 2009-12-30 09:47:04
|
Hi John, The "chroot: cannot run command '/grub2-sh-RSkJuV': Exec format error" issue should have been fixed in Clonezilla live 1.2.3-23 or 20091230-karmic. Could you please give it a try and let us know the results? Thanks. Steven. On 2009/11/22 上午 07:04, John Ouzts wrote: > Steven, > > I found all the favorable comment about CloneZilla on the web while > looking for a way to clone a new Ubuntu Koala grub2/ext4 install. The > current version of CloneZilla with the Koala kernel did indeed work. One > error message appeared in the section about reinstalling grub2: > > chroot: cannot run command '/grub2-sh-RSkJuV': Exec format error > > However, the newly cloned drive did boot up (after I reset the harddrive > boot order in BIOS). Is this error something that I need to fix? > > Many thanks for a GREAT LiveCD! > > John > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > > > _______________________________________________ > Clonezilla-live mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clonezilla-live > > --===============39269408305456 -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Steven S. <st...@nc...> - 2009-12-30 08:36:09
|
On 2009/12/29 上午 01:31, Santiago Bruno wrote: > On Sat, Dec 26, 2009 at 8:24 AM, Steven Shiau<st...@nc...> wrote: >> >> >> Santiago Bruno wrote: >>> >>> On Thu, Dec 24, 2009 at 4:46 AM, Steven Shiau<st...@nc...> wrote: >>> >>>> >>>> Santiago Bruno wrote: >>>> >>>>> >>>>> On Wed, Dec 23, 2009 at 11:59 AM, Steven Shiau<st...@nc...> >>>>> wrote: >>>>> >>>>>> >>>>>> Santiago Bruno wrote: >>>>>> >>>>>>> >>>>>>> On Mon, Dec 14, 2009 at 4:47 AM, Steven Shiau<st...@nc...> >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> Thanks for the bug reports. I reply your question sin the following. >>>>>>>> >>>>>>>> Santiago Bruno wrote: >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I'm trying to use Clonezilla live in a machine that will boot using >>>>>>>>> PXE through its interface eth1. This machine can redirect the >>>>>>>>> console >>>>>>>>> using Serial over Lan with its own hardware and is configured to do >>>>>>>>> so. >>>>>>>>> >>>>>>>>> I added live-getty and console=ttyS0,115200n8 to the kernel command >>>>>>>>> line but I'm having a strange problem. >>>>>>>>> >>>>>>>>> When I'm looking at the serial console, after booting clonezilla, >>>>>>>>> there is output at the console as expected, but some output also >>>>>>>>> goes >>>>>>>>> to the VGA. And it's not the same output. Is like there are two >>>>>>>>> different clonezilla instances in tty1 and ttyS0. They even start >>>>>>>>> cloning the same partitions at diferent times messing all up. At the >>>>>>>>> end one can go to the command line on both consoles and evidently >>>>>>>>> they >>>>>>>>> are two different processes. >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> How did you configure your clonezilla live ? Please show us the >>>>>>>> config >>>>>>>> files, e.g. syslinux.cfg... So it's easier for me to reproduce the >>>>>>>> problem >>>>>>>> then we can fix this problem. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Well, I'm using some custom scripts, but now I reduced the >>>>>>> configuration to try to use a script that does not exists to see if >>>>>>> the problem still happened so it could be easier to reproduce. >>>>>>> >>>>>>> The pxe file for the machine would be like this: >>>>>>> >>>>>>> default Clonezilla >>>>>>> label Clonezilla >>>>>>> kernel /clonezilla/vmlinuz >>>>>>> append initrd=/clonezilla/initrd.img boot=live live-getty >>>>>>> console=ttyS0,115200n8 union=aufs noswap noprompt nosplash >>>>>>> live-netdev="eth1" >>>>>>> fetch=tftp://<SERVER_IP>/clonezilla/filesystem.squashfs >>>>>>> ocs_live_keymap="NONE" ocs_live_batch="yes" ocs_lang="en_US.UTF-8" >>>>>>> ocs_live_run="/blablablabla" >>>>>>> >>>>>>> and what happens when booting is the following. >>>>>>> >>>>>>> VGA starts displaying the pxe boot, "Decompressing Linux..." >>>>>>> decompressing the initrd, and the last lines are >>>>>>> "Ready >>>>>>> Probing EDD (...) ok" >>>>>>> >>>>>>> It stops there, and then, text starts coming out through ttyS0 >>>>>>> instead. squashfs is decompressed, init starts, I can see that it >>>>>>> tries to set up eth0 through dhcp because I see some "DHCPDISCOVER..." >>>>>>> lines until it times out. >>>>>>> Then I think it sets up eth1 very fast and then the problem starts. >>>>>>> I think it is when the ocs scripts begin executing. >>>>>>> The VGA changes from the typical console text to another font, >>>>>>> probably a framebuffer, and some scripts begin executing both in tty1 >>>>>>> and ttyS0 >>>>>>> obviously they fail inmediately because there is no blablablabla >>>>>>> script, but I get the prompt to select what to do next in both >>>>>>> terminals and they are different processes. >>>>>>> If I type "tty" one gives /dev/tty1 and the other /dev/ttyS0. >>>>>>> I would expect that everything happens in ttyS0 if I specified >>>>>>> console=ttyS0 on the command line, or to have an option to do that. Is >>>>>>> it possible? I would expect in that case to keep tty1 blocked or in a >>>>>>> login prompt. >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> Yes. Here I think the best solution is in your customized script, add >>>>>> one >>>>>> line in the beginning: >>>>>> ================================ >>>>>> [ "$(tty)" != "/dev/ttyS0" ]&& exit 1 >>>>>> ================================ >>>>>> >>>>>> Then the rest of your script will only be run in the /dev/ttyS0. >>>>>> >>>>>> Hope this helps. >>>>>> >>>>> >>>>> Yes, I considered implementing exactly that workaround. The only >>>>> problem is that I will be using the script as part of a bigger system >>>>> with an user interface where the user may choose to redirect the >>>>> output or not. So I will have two different customized scripts, one >>>>> for redirecting and another for not redirecting, and selecting which >>>>> script to use through the generated pxe config file. >>>>> I thought of reporting the problem so I had to work less :P >>>>> But this should work. >>>>> >>>>> Thank you! >>>>> >>>>> Santiago. >>>>> >>>> >>>> Another possibility is we can implement another ocs option to force >>>> $ocs_live_run to be run in specific tty, e.g. ttyS0. Now it will be run >>>> in >>>> tty1 and ttyS0. >>>> E.g. with boot parameter >>>> ocs_live_tty="/dev/ttyS0" >>>> then the $ocs_live_run will be run in ttyS0 only. Not in tty1. >>>> >>>> This should work. Or maybe you have better idea? >>>> >>> >>> That would be something nice to have. I have no other idea. But I >>> don´t know how complicated it will be to implement it. I can live with >>> the workaround you suggested ;) >>> But let me know if you implement it in some future release or if I can >>> help in some way, like testing. >>> >>> Cheers, >>> >>> Santiago. >>> >> >> I have uploaded Clonezilla live 1.2.3-21 in the testing branch. A boot >> parameter "ocs_live_run_tty" was added for this purpose. Please refer to >> http://clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc >> for how to use it. >> >> Please let us know the results if you test that. >> Thanks. > > I've just integrated this new release of clonezilla to my system and > I'm using the new boot parameter when console redirection is selected. > I did some tests redirecting and not redirecting and it is working as > I expected on the first time. Everything looks good so far. I will let > you know if I find any problem later but it seems to be working great! > Thanks for your work! > > Santiago. Santiago, Due to an issue (https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3499579) we have to change this again. Now by default the clonezilla command will be run on /dev/tty1 only. If you want to use /dev/ttyS0, you can assign "live-getty console=ttyS0,115200n81" and it will be run on /dev/ttyS0 only. For more info, please check the changelog: http://free.nchc.org.tw/clonezilla-live/experimental/ubuntu-based/ChangeLog-Clonezilla-live.txt or http://clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc I believe this change should make things easier and better. If you have any thought or suggestion, please let us know. Please test it again and let us know the results. Thanks again. Steven. -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A |
|
From: Kevin W. W. <kev...@gm...> - 2009-12-29 02:35:52
|
Uriel Avalos wrote: > OK thanks. But what's "smart utilities"? Is that part of clonezilla? or > do I get that somewhere else? A quick google search didn't turn > anything up... Uriel, I think Bob Coffman was referring to S.M.A.R.T. (which stands for "Self-Monitoring, Analysis, and Reporting Technology") hard drive utilities. Google for the terms S.M.A.R.T. hard drive Linux utilities and you will find a bunch of stuff. Not sure which, if any of them, are on the Clonezilla distro. If you only have a few bad blocks, you can rescan your drive and rebuild it with a new bad block list. But if you have bad blocks, you seriously want to think about replacing your hard drive. HTH, -kevin -- Kevin W. Wall "The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." -- Nathaniel Borenstein, co-creator of MIME |
|
From: Santiago B. <san...@gm...> - 2009-12-28 17:31:17
|
On Sat, Dec 26, 2009 at 8:24 AM, Steven Shiau <st...@nc...> wrote: > > > Santiago Bruno wrote: >> >> On Thu, Dec 24, 2009 at 4:46 AM, Steven Shiau <st...@nc...> wrote: >> >>> >>> Santiago Bruno wrote: >>> >>>> >>>> On Wed, Dec 23, 2009 at 11:59 AM, Steven Shiau <st...@nc...> >>>> wrote: >>>> >>>>> >>>>> Santiago Bruno wrote: >>>>> >>>>>> >>>>>> On Mon, Dec 14, 2009 at 4:47 AM, Steven Shiau <st...@nc...> >>>>>> wrote: >>>>>> >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> Thanks for the bug reports. I reply your question sin the following. >>>>>>> >>>>>>> Santiago Bruno wrote: >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I'm trying to use Clonezilla live in a machine that will boot using >>>>>>>> PXE through its interface eth1. This machine can redirect the >>>>>>>> console >>>>>>>> using Serial over Lan with its own hardware and is configured to do >>>>>>>> so. >>>>>>>> >>>>>>>> I added live-getty and console=ttyS0,115200n8 to the kernel command >>>>>>>> line but I'm having a strange problem. >>>>>>>> >>>>>>>> When I'm looking at the serial console, after booting clonezilla, >>>>>>>> there is output at the console as expected, but some output also >>>>>>>> goes >>>>>>>> to the VGA. And it's not the same output. Is like there are two >>>>>>>> different clonezilla instances in tty1 and ttyS0. They even start >>>>>>>> cloning the same partitions at diferent times messing all up. At the >>>>>>>> end one can go to the command line on both consoles and evidently >>>>>>>> they >>>>>>>> are two different processes. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> How did you configure your clonezilla live ? Please show us the >>>>>>> config >>>>>>> files, e.g. syslinux.cfg... So it's easier for me to reproduce the >>>>>>> problem >>>>>>> then we can fix this problem. >>>>>>> >>>>>>> >>>>>> >>>>>> Well, I'm using some custom scripts, but now I reduced the >>>>>> configuration to try to use a script that does not exists to see if >>>>>> the problem still happened so it could be easier to reproduce. >>>>>> >>>>>> The pxe file for the machine would be like this: >>>>>> >>>>>> default Clonezilla >>>>>> label Clonezilla >>>>>> kernel /clonezilla/vmlinuz >>>>>> append initrd=/clonezilla/initrd.img boot=live live-getty >>>>>> console=ttyS0,115200n8 union=aufs noswap noprompt nosplash >>>>>> live-netdev="eth1" >>>>>> fetch=tftp://<SERVER_IP>/clonezilla/filesystem.squashfs >>>>>> ocs_live_keymap="NONE" ocs_live_batch="yes" ocs_lang="en_US.UTF-8" >>>>>> ocs_live_run="/blablablabla" >>>>>> >>>>>> and what happens when booting is the following. >>>>>> >>>>>> VGA starts displaying the pxe boot, "Decompressing Linux..." >>>>>> decompressing the initrd, and the last lines are >>>>>> "Ready >>>>>> Probing EDD (...) ok" >>>>>> >>>>>> It stops there, and then, text starts coming out through ttyS0 >>>>>> instead. squashfs is decompressed, init starts, I can see that it >>>>>> tries to set up eth0 through dhcp because I see some "DHCPDISCOVER..." >>>>>> lines until it times out. >>>>>> Then I think it sets up eth1 very fast and then the problem starts. >>>>>> I think it is when the ocs scripts begin executing. >>>>>> The VGA changes from the typical console text to another font, >>>>>> probably a framebuffer, and some scripts begin executing both in tty1 >>>>>> and ttyS0 >>>>>> obviously they fail inmediately because there is no blablablabla >>>>>> script, but I get the prompt to select what to do next in both >>>>>> terminals and they are different processes. >>>>>> If I type "tty" one gives /dev/tty1 and the other /dev/ttyS0. >>>>>> I would expect that everything happens in ttyS0 if I specified >>>>>> console=ttyS0 on the command line, or to have an option to do that. Is >>>>>> it possible? I would expect in that case to keep tty1 blocked or in a >>>>>> login prompt. >>>>>> >>>>>> >>>>>> >>>>> >>>>> Yes. Here I think the best solution is in your customized script, add >>>>> one >>>>> line in the beginning: >>>>> ================================ >>>>> [ "$(tty)" != "/dev/ttyS0" ] && exit 1 >>>>> ================================ >>>>> >>>>> Then the rest of your script will only be run in the /dev/ttyS0. >>>>> >>>>> Hope this helps. >>>>> >>>> >>>> Yes, I considered implementing exactly that workaround. The only >>>> problem is that I will be using the script as part of a bigger system >>>> with an user interface where the user may choose to redirect the >>>> output or not. So I will have two different customized scripts, one >>>> for redirecting and another for not redirecting, and selecting which >>>> script to use through the generated pxe config file. >>>> I thought of reporting the problem so I had to work less :P >>>> But this should work. >>>> >>>> Thank you! >>>> >>>> Santiago. >>>> >>> >>> Another possibility is we can implement another ocs option to force >>> $ocs_live_run to be run in specific tty, e.g. ttyS0. Now it will be run >>> in >>> tty1 and ttyS0. >>> E.g. with boot parameter >>> ocs_live_tty="/dev/ttyS0" >>> then the $ocs_live_run will be run in ttyS0 only. Not in tty1. >>> >>> This should work. Or maybe you have better idea? >>> >> >> That would be something nice to have. I have no other idea. But I >> don´t know how complicated it will be to implement it. I can live with >> the workaround you suggested ;) >> But let me know if you implement it in some future release or if I can >> help in some way, like testing. >> >> Cheers, >> >> Santiago. >> > > I have uploaded Clonezilla live 1.2.3-21 in the testing branch. A boot > parameter "ocs_live_run_tty" was added for this purpose. Please refer to > http://clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc > for how to use it. > > Please let us know the results if you test that. > Thanks. I've just integrated this new release of clonezilla to my system and I'm using the new boot parameter when console redirection is selected. I did some tests redirecting and not redirecting and it is working as I expected on the first time. Everything looks good so far. I will let you know if I find any problem later but it seems to be working great! Thanks for your work! Santiago. |
4 messages has been excluded from this view by a project administrator.
