Clonezilla - Revision history

Leo: Added category

2020-06-14T23:33:00Z

Added category

← Older revision		Revision as of 23:33, 14 June 2020
Line 202:		Line 202:

	Try booting Clonezilla again. If everything's good, you should be able to boot into it.		Try booting Clonezilla again. If everything's good, you should be able to boot into it.

			{{Navbox Linux}}[[Category:Linux]]
			[[Category:LinuxUtilities]]

Leo: /* USB */

2019-11-25T03:25:38Z

USB

@@ Line 29: / Line 29: @@
 # mount /dev/sdg1 /mnt/usb
 # cd /mnt/usb
-# tar -xzf ~/clonzilla*zip
+# unzip ~/clonzilla*zip
 }}
-Install the MBR on the USB drive using the included script.
+Install the MBR on the USB drive using the included script. This requires the {{code|mtools}} package installed.
 {{highlight|lang=terminal|code=
 # cd /mnt/usb/utils/linux
 # bash makeboot.sh /dev/sdg1
 }}

Leo: Import WP content from http://leo.steamr.com/2012/10/clonezilla-1-2-doesnt-boot/

2019-09-12T04:59:00Z

Import WP content from http://leo.steamr.com/2012/10/clonezilla-1-2-doesnt-boot/

← Older revision		Revision as of 04:59, 12 September 2019
Line 82:		Line 82:

	If you want the entry to boot by default, uncomment the {{code\|MENU DEFAULT}} line and then comment out the one that is.		If you want the entry to boot by default, uncomment the {{code\|MENU DEFAULT}} line and then comment out the one that is.

			== Troubleshooting ==
			=== TFTP Boot Issues ===
			Clonezilla 1.2 does not boot from a TFTP server running on FreeBSD (9.0-RELEASE). Everything seems to boot fine until it tries to fetch the root filesystem. Below is what is seen on the console during the boot process:

			{{highlight\|lang=text\|code=
			IP-Config: eth0 complete (dhcp from 10.1.1.9)
			address: 10.1.1.55 broadcast: 10.1.1.255 netmask: 255.255.255.0
			gateway: 10.1.1.1 dns0 : 10.1.1.9 dns1 : 0.0.0.0
			domain : home.steamr.com
			rootserver: 10.1.1.9 rootpath:
			filename : /pxelinux.0
			Creating /etc/resolv.conf
			Begin: Trying tftp -g -b 10240 -r /images/clonezilla/live/filesystem.squashfs -l /images/clonezilla/live/filesystem.squashfs 10.1.1.9 ... ^M /images/clonezilla/l 0% {{!}}
			tftp: timeout

			.''`.
			: :' : BOOT FAILED!
			`. `'`
			`- This Debian Live image failed to boot.

			Please file a bug against the 'live-boot' package or email the Debian
			Live mailing list at <debian-live@lists.debian.org>, m aking sure to note
			the exact version, name and distribution of the image you were attempting to boot.

			< snip >

			BusyBox v1.20.1 (Debian 1:1.20.0-4) built-in shell (ash)
			Enter 'help' for a list of built-in commands.

			/bin/sh: can't access tty; job control turned off
			(initramfs) _
			}}

			The tftpboot {{code\|pxelinux.cfg/default}} configuration file contains:
			{{highlight\|lang=text\|code=
			label 3
			menu label ^3. Clonezilla Live CD (x86)
			kernel images/clonezilla/live/vmlinuz
			append initrd=images/clonezilla/live/initrd.img boot=live config noswap nolocales edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=788 nosplash noprompt fetch=tftp://10.1.1.9/images/clonezilla/live/filesystem.squashfs
			}}

			Obviously, tftp works. This is evident by the fact that Clonezilla managed to boot and the fact that I was greeted by the pxe boot menu. Furthermore, if I typed in {{code\|tftp -g -r /images/clonezilla/live/filesystem.squashfs 10.1.1.9}}, I am able to retrieve the {{code\|filesystem.squashfs}} file without issue.

			Checking the logs on the FreeBSD machine, I see:
			{{highlight\|lang=text\|code=
			Oct 3 04:42:34 nas tftpd[38727]: send_packet: Message too long
			Oct 3 04:42:34 nas tftpd[38727]: Cannot send DATA packet #1, trying again
			Oct 3 04:42:34 nas tftpd[38727]: DATA block 1, attempt 0 failed (Error 40: Message too long)
			Oct 3 04:42:35 nas tftpd[38727]: DATA block 1, attempt 1 failed (Error 40: Message too long)
			Oct 3 04:42:37 nas tftpd[38727]: DATA block 1, attempt 2 failed (Error 40: Message too long)
			Oct 3 04:42:38 nas tftpd[38783]: DATA block 1, attempt 4 failed (Error 40: Message too long)
			Oct 3 04:42:41 nas tftpd[38727]: DATA block 1, attempt 3 failed (Error 40: Message too long)
			}}

			So, obviously, the transfer block size is causing some sort of issue. I spent easily over an hour trying to get it to work using different parameters and different tftpd servers to avail.

			{{Info
			\|1=Possible Packet Size + MTU Cause
			\|2=A friendly guy named Torsten mentioned that the TFTP command used by Clonezilla uses a maximum packet size of 10240 bytes which exceeds most ethernet MTUs. The TFTP server most likely defaulted to a 65464 byte MTU which was the cause of this issue.

			If you run into this issue again, try changing the TFTP server's maximum packet size to MTU - 32 bytes. Run {{code\|tcpdump}} and see what sizes these network frames are.
			}}

			Alternatively, use NFS. Change the configuration to match the following:

			{{code\|/etc/exports}}:
			{{highlight\|lang=text\|code=
			/tftpboot/images/clonezilla -network 10.1.1 -mask 255.255.255.0 # or whatever network address you're on. I'm on 10.1.1.0/24
			}}

			{{code\|/tftpboot/pxelinux.cfg/default}}:
			{{highlight\|lang=text\|code=
			label 3
			menu label ^3. Clonezilla Live CD (x86)
			kernel images/clonezilla/live/vmlinuz
			append initrd=images/clonezilla/live/initrd.img boot=live live-config noswap <strong>union=aufs netboot=nfs nfsroot=10.1.1.9:/tftpboot/images/clonezilla</strong> ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=788
			}}

			Then, re-export or restart/reload NFS:

			{{highlight\|lang=terminal\|code=
			# kill -HUP `cat /var/run/mountd.pid `
			}}

			Try booting Clonezilla again. If everything's good, you should be able to boot into it.

Leo at 22:14, 29 November 2018

2018-11-29T22:14:20Z

← Older revision		Revision as of 22:14, 29 November 2018
Line 1:		Line 1:
	Clonezilla is a disk imaging ~~distro~~.		Clonezilla is a disk imaging Linux distribution that can be live booted from a USB, CD, or network.

	== USB ~~Setup~~ ==		== USB ==
	For other ways to set up a ~~clonezilla~~ USB drive, see http://clonezilla.org/liveusb.php.		For other ways to set up a Clonezilla USB drive, see http://clonezilla.org/liveusb.php.

	To set up a USB key with Clonezilla manually:		To set up a USB key with Clonezilla manually, partition a USB drive with one FAT32 partition. If using {{code\|fdisk}} to partition, set the partition type to 'b' and make it bootable with 'a'.

	~~Partition~~ a USB ~~stick so it looks something like this~~. ~~Set~~ the type to 'b' and make it bootable with 'a'.

	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 25:		Line 23:
	}}		}}

	Download the ~~clonezilla~~ zip archive, then extract it to the USB drive.		Download the Clonezilla zip archive, then extract it to the USB drive.

	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 32:		Line 30:
	# cd /mnt/usb		# cd /mnt/usb
	# tar -xzf ~/clonzilla*zip		# tar -xzf ~/clonzilla*zip
	## Install the MBR using the ~~built in~~ script		}}

			Install the MBR on the USB drive using the included script.
			{{highlight\|lang=terminal\|code=
	# cd /mnt/usb/utils/linux		# cd /mnt/usb/utils/linux
	# bash makeboot.sh /dev/sdg1		# bash makeboot.sh /dev/sdg1

Leo at 22:10, 29 November 2018

2018-11-29T22:10:34Z

@@ Line 36: / Line 36: @@
 # bash makeboot.sh /dev/sdg1
 }}
 == Automated Imaging ==

Leo: /* Automated Imaging */

2017-09-01T18:27:57Z

Automated Imaging

← Older revision		Revision as of 18:27, 1 September 2017
Line 38:		Line 38:

	== Automated Imaging ==		== Automated Imaging ==
	To automatically ~~reimage~~ a ~~computer on boot (either via PXE~~ or ~~USB), create a boot entry in {{code\|syslinux/syslinux.cfg}} that contains the~~ restore ~~(or imaging) command specified~~ by the {{code\|ocs_live_run}} ~~parameter~~.		You can automatically image a drive or restore an image by using the {{code\|ocs_live_run}} option that is passed to the kernel on boot. This will work with PXE or USB.

	~~For example~~, to restore an image located ~~on the root of the USB drive at~~ {{code\|/partimag~~/display-v1.1~~}} ~~automatically~~:		To do this on a USB stick, create a boot entry in {{code\|syslinux/syslinux.cfg}} that contains the restore (or imaging) command specified by the {{code\|ocs_live_run}} parameter. On an EFI system, you will want to edit {{code\|/EFI/boot/grub.cfg}} instead.

			To restore an image located in {{code\|/partimag}}, create a boot entry similar to the one below:

	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
Line 49:		Line 51:
	# Automatic Restore for display-v1.1		# Automatic Restore for display-v1.1
	label Clonezilla restore display		label Clonezilla restore display
			# MENU DEFAULT
	# MENU HIDE		# MENU HIDE
	MENU LABEL Clonezilla Restore Display v1.1		MENU LABEL Clonezilla Restore Display v1.1
Line 61:		Line 64:
	...		...
	}}		}}

			If you want the entry to boot by default, uncomment the {{code\|MENU DEFAULT}} line and then comment out the one that is.

Leo: /* Automated Imaging */

2017-09-01T18:17:58Z

Automated Imaging

← Older revision		Revision as of 18:17, 1 September 2017
Line 38:		Line 38:

	== Automated Imaging ==		== Automated Imaging ==
	To automatically reimage a computer on boot (either via PXE or USB), create a boot entry in {{code\|~~isolinux~~.cfg}} that contains the restore (or imaging) command specified by the {{code\|ocs_live_run}} parameter.		To automatically reimage a computer on boot (either via PXE or USB), create a boot entry in {{code\|syslinux/syslinux.cfg}} that contains the restore (or imaging) command specified by the {{code\|ocs_live_run}} parameter.

	For example, to restore an image located on the root of the USB drive at {{code\|/partimag/display-v1.1}} automatically:		For example, to restore an image located on the root of the USB drive at {{code\|/partimag/display-v1.1}} automatically:

Leo: /* Automated Imaging */

2017-09-01T18:14:08Z

Automated Imaging

← Older revision		Revision as of 18:14, 1 September 2017
Line 38:		Line 38:

	== Automated Imaging ==		== Automated Imaging ==
	To automatically reimage a computer on boot (either via PXE or USB), create a boot entry that contains the restore (or imaging) command in the {{code\|ocs_live_run}} parameter.		To automatically reimage a computer on boot (either via PXE or USB), create a boot entry in {{code\|isolinux.cfg}} that contains the restore (or imaging) command specified by the {{code\|ocs_live_run}} parameter.

			For example, to restore an image located on the root of the USB drive at {{code\|/partimag/display-v1.1}} automatically:

	~~For example, on a USB drive, I wanted to reimage the computer using the image located in {{code\|/partimag/latest-nvidia}}:~~
	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
			...
			# simple menu title
			MENU TITLE clonezilla.org, clonezilla.nchc.org.tw

	label Clonezilla ~~auto ttuff~~		# Automatic Restore for display-v1.1
			label Clonezilla restore display
	# MENU HIDE		# MENU HIDE
	MENU LABEL Clonezilla ~~Auto TTuff~~		MENU LABEL Clonezilla Restore Display v1.1
	# MENU PASSWD		# MENU PASSWD
	kernel /live/vmlinuz		kernel /live/vmlinuz
	append initrd=/live/initrd.img boot=live union=overlay username=user hostname=~~yakkety~~ config components noswap edd=on nomodeset noeject locales=en_US.UTF-8 keyboard-layouts=NONE ocs_live_run="ocs-sr -g auto -e1 auto -e2 -r -icds -j2 -p reboot restoredisk ../../lib/live/mount/medium/partimag/~~latest~~-~~nvidia~~ sda" ocs_live_extra_param="" ocs_live_batch="no" vga=788 ip= net.ifnames=0 splash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=1		append initrd=/live/initrd.img boot=live union=overlay username=user hostname=zesty config components noswap edd=on nomodeset noeject locales=en_US.UTF-8 keyboard-layouts=NONE ocs_live_run="ocs-sr -g auto -e1 auto -e2 -r -icds -j2 -p reboot restoredisk ../../lib/live/mount/medium/partimag/display-v1.1 sda" ocs_live_extra_param="" ocs_live_batch="no" vga=788 ip= net.ifnames=0 splash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=1
	TEXT HELP		TEXT HELP
	Automatically images from USB for the TTuff 1U computer		Automatically images from USB for the TTuff 1U computer
	ENDTEXT		ENDTEXT

			label Clonezilla live
			...
	}}		}}

Leo: /* USB Setup */

2017-09-01T18:00:04Z

USB Setup

← Older revision		Revision as of 18:00, 1 September 2017
Line 2:		Line 2:

	== USB Setup ==		== USB Setup ==
	To set up a USB key with Clonezilla:		For other ways to set up a clonezilla USB drive, see http://clonezilla.org/liveusb.php.

			To set up a USB key with Clonezilla manually:

	Partition a USB stick so it looks something like this. Set the type to 'b' and make it bootable with 'a'.		Partition a USB stick so it looks something like this. Set the type to 'b' and make it bootable with 'a'.

Leo: /* USB Setup */

2017-09-01T17:59:26Z

USB Setup

← Older revision		Revision as of 17:59, 1 September 2017
Line 19:		Line 19:
	/dev/sdg1 * 2048 60555263 60553216 28.9G b W95 FAT32		/dev/sdg1 * 2048 60555263 60553216 28.9G b W95 FAT32

			## Format the drive
			# mkfs.vfat -F 32 /dev/sdg1
	}}		}}

Line 32:		Line 34:
	# bash makeboot.sh /dev/sdg1		# bash makeboot.sh /dev/sdg1
	}}		}}


	== Automated Imaging ==		== Automated Imaging ==