2x Clonezilla on the same USB Drive
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
I have a problem booting clonezilla live (unicast) from my USB Drive.
I have downloaded the latest version of this program -v. 1.2.2-31- (wich was recently added) because it is possible for me to install saved IDE images to SATA HD machines, vice versa.
But, I also have the Clonezilla live server version on the save USB drive(that is older and not able to install iamges from IDE to SATA).
There is a conflict, clonezilla live (unicast) boots normally until it needs to find the filesystem.squashfs. The server version's filesystem is loaded instead.
I have tried changing command lines to add bootfrom=/dev/sda or /hda,
I have also tried live_media_path=/live wich also failed.
The only way I could make it work is to rename filesystem.squashfs in the server version ton another name, but then, when I try to multicast, the live (unicast) version boots instead.
I appreciate your help and hope my information is thourought.
I have tried with multiple boot managers to try and help me boot the good version of clonezilla.
These boot managers wont make it work either: GAG Graphical boot manager, PLoP linux boot manager.
I would really appreciate your thoughts about this! Thanks in advance.
Maybe you can use the "module" boot parameter. i.e. by assigning different file names of root filesystem, you can make it.
Please refer to this:
http://clonezilla.org/clonezilla-live/live-initramfs-param.php
If you make it, please share how to do that. Thanks.
Steven.
Here is what I found in the link that should make it work:
*{live-media|bootfrom}=**DEVICE**::
If you specify one of this two equivalent forms, live-initramfs will first try to find this device for the "/live" directory where the read-only root filesystem should reside. If it did not find something usable, the normal scan for block devices is performed.*
Like I said in the fist post, I have tried bootfrom=/dev/sda(b)(C) or hda(b)(C) and it wouldn't find the good filesystem.
*live-media-path=**PATH**::
Sets the path to the live filesystem on the medium. By default, it is set to '/live' and you should not change that unless you have customized your media accordingly.*
I have changed the path to /live2 (edited the syslinux.cfg file). The boot sequence find the live2 folder and boots accordingly, but when the filesystem.squash has to be used, it jumps to the clonezilla server filesystem.
Also, when I try to point to the good filesystem after I have changed it's name, it either finds the one from clonezilla server or can't boot correctly.
In syslinux.cfg:
*append initrd=/live/initrd1.img boot=live union=aufs nolocales ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" noprompt vga=791 **toram=filesystem1.squashfs** ip=frommedia*
I couldn't find any other files than syslinux.cfg that had a string related to booting the filesystem.squashfs. If there are other files that are related to how the filesystem is copied to ram or anything related, I'd like some more assistance.
Thanks for the link you have given me, and I hope you can find some way to solve this puzzle!
With what is stated in the previous post, I do not think we can make it work. I am wondering if and how this command works :
/live/filesystem.module
This optional file (inside the live media) contains a list of white-space or carriage-return-separated file names corresponding to disk images in the "/live" directory. If this file exists, only images listed here will be merged into the root aufs, and they will be loaded in the order listed here. The first entry in this file will be the "lowest" point in the aufs, and the last file in this list will be on the "top" of the aufs, directly below /cow. Without this file, any images in the "/live" directory are loaded in alphanumeric order.
If I rename my filesystem.squashfs to filesystem1.squashfs and create a filesystem.module containing only "filesystem1.squashfs", will it load it?
Actually I never tried this before. Just did a test, and it failed… No idea how to use that. Maybe you can ask that in Debian live/live-initramfs mailing list.
Steven.