04-14-2018, 11:09 PM
(This post was last modified: 10-24-2018, 06:52 PM by Jay Smith. Edited 12 times in total.)
For those who are interested in cloning all operating systems.
I had worked on this method of cloning any OS System for some time now and solved some main issues.
It works very good, I am so glad not having to configure systems over and over. Saves a lot of time.
It looks like a lot to do, but once you create images and restore drives you will see it is very easy.
There is a forum for Clonezilla for help to solve any error issues. This will make you weak in configuring because you won't be doing it so often.
Always write solutions and configuration instructions in a text file so no time is wasted trying to figure something out later on. It's called an engineering book.
Best to have an engineering text file. You can do searches in it.
If you only want to use clonezilla live, simply download it and burn it to a cd/dvd drive and boot it.
https://clonezilla.org/
https://www.backup-utility.com/articles/...-4348.html
http://www.geekyprojects.com/storage/how...ler-drive/
Clonezilla steps:
Clonezilla (CZ) ver. 2.2.3.10-amd64 or for Intel
Important: Before Restoring use gparted to create one partition on the target and format it.
Take the TBos MicroSD to the other desktop and plug it into the usb. Use another internal or external drive to store the image to be created.
1 Run and select Clonezilla Default When ask to use .isoask, ignor it and let boot.
2 Enter ok for Engish, Don't touch keymap
3 Start-CZ Device-image work with disks or partitions using images
4 Select local_dev (USB, HDrive, SSD), Assign where CZ image will be saved/read for restoring It will be
mounted as Temporary /home/partimag.
5 Select sdb or sdc, Don't use the device you will be creating an image for.
6 Select / top_directory_in_the_local_device
7 Select Beginner mode: accept the default option
8 Select Save Disk saves local disk as image. If image is found, CZ will offer the restore option also.
9 Name the saved image, Remember: Don't use spaces or CZ will not recognize it.
10 Select the local disk to save, It will create an image of the device you chose and all of it's partitions and the MasterBootRecord (MBR).
11 If using Clonezilla zesty, it will make the mount /media/ owned by root.
You can change it with su or sudo chown -R username /media/driveMountName or /media/*
Then you can move/delete/copy images to the partition.
The Programmers make it root owned for security reasons. I don't have this problem anymore since I create the image on an external drive.
Don't create the image on the drive you are cloning.
Notes:
1 Clonezilla (CZ) ver. 2.2.3.10-amd64 put the image in the USB Drive and did not change the partition to root.
Looks like CZ ver. 2.2.5 works ok. It didn't make my partition drive root protected after image creation.
2 If there is an image in the same device partiton, CZ will offer the restore option with the save option.
3 CZ won't recognize an image or directory name with spaces in it.
4 Some motherboards/operating systems have to have acpi=off entered at boot time.
5 The drive must be unmounted to create an image of the drive. That's why it's important to boot from a USB/CD.
6 CZ copies the files, not any of the empty space. The Linux command dd copies empty space and files.
7 Drive Size:
Before Restoring format the USB drive/microSD with one partition.
If there is a small 500mb partition, CZ will say it's to small and fail to restore.
I restored using an image of a 16gb TBos to a 64gb USB thumbdrive.
If the destination drive is somewhat smaller than the image source, CZ will alert you to that issue. You can go
into expert mode and select -icds and at the next window select -k1. This will work as long as you know that the files will fit on the destination drive.
It will take 90 minutes or more because of the partition resizing. You don't want to do that unless you have too.
Example: say you have a 3.1gb microSD and a 29.4gb microSD. It's not going to restore, period. Nothing works. The destination has to be equal to or larger.
no way around it. So, do OS setup on the smallest drive, maybe a 16gb and then always restore to a 32gb or larger drive.
Flash the OS on the smaller microSD, update it, install all applications, and configure what you want.
Then create the CZ image using the smaller microSD. That way the image will fit on the larger drives.
Remember to use gparted to create only one partition and formated on the target to be restored.
8 Sync failure: If it fails to sync, just ignore that. I used the microSD and it booted just fine. Don't know yet what that Sync Issue is yet. Checking Inodes maybe.
Fix:
1 may use gparted to create ext4 microSD....one partition.
2 Use CZ Zesty and use restore>expertMode>-icsd>-k1 The -icsd and -k1 didn't work for me on any of my microSD.
3 When fscync fails do ctl/alt/delete to cancel before it trys to fix inodes.
4 I used a 16gb microSd to create image. Then restored onto a 32gb microSD with one partition formated using gparted.
5 CZ doesn't handle microSD very well. They shrink in size over time.
6 May have to restore again. microSD can be stuburn.
I bootup on a sandisk usb 16gb 3.0. Updated, installed all my apps, and fully configured. CZ image created in 3 minutes.
Reason is I can flash any drive larger than a 16gb one. Then use gparted to resize the partition fully.
The problem is some microSD chips can shrink in size and cause the problems.
Creating images is very easy, but restoring can give problems. Right now using a USB flash drive restored smoothly and fsyncing was successful.
Overview using a bootable USB:
1 Create a bootable USB.
2 Load cloning program>clonezilla,partimage on bootable USB.
3 Create restorable image of any drive with any OS.
Notes: Remember when creating cloned image to do check image, to verify it's good for restoring. CZ will tell you if it is a restorable image.
Make 2 images in case of corruption.
Yumi:
https://www.pendrivelinux.com/yumi-multi...b-creator/
Yumi Notes:
1 Yumi works in linux with wine installed. It is the easiest to work with but limited.
2 May have to use windows to get yumi to format the usb to fat32 the first time.
Dang! Still need a windows. At least only once the first time.
Then you can use yumi in linux to load iso files. Yumi shows the usb as ntfs even though it is fat32.
I tried formating the usb fat32 with gparted but it wouldn't boot. Must need yumi to format it.
3 Yumi is limited with live operating systems. Easy2boot does all.
4 Yumi will see iso and zip files. I would think iso would run faster.
5 No defragging required.
6 fat32 format is required. Don't know yet if ntfs will work.
Load clonezilla/partimage/gparted and you can burn backups of all devices.
7 Some Live ISOs will need to have acpi=off added to the boot commandline, if they don't boot.
8 If you have an application.img file, you can rename the .img to .iso and copy it to yumi/easy2boot and use it.
Note: Easier to just use YUMI in windows to format the usb drive.
This may eliminate the need for a windows running YUMI to format fat32
I. Format your USB Flash Drive to use a Single Partition in linux:
Open a terminal and type sudo su
Type fdisk -l (and note which device is your USB Drive)
Type fdisk /dev/sdx (replacing x with your actual usb device)
Type d (to delete the existing partition)
Type n (to create a new partition)
Type p (for primary partition)
Type 1 (to create the first partition)
Press Enter (to use the first cylinder)
Press Enter again (to use the default value as the last cylinder)
Type a (for active)
Type 1 (to mark the first partition active "bootable")
Type t (for partition type)
Type c (to use fat32 partition)
Type w (to write the changes and close fdisk)
II. Create a Fat32 Filesystem on the USB Flash Drive:
Type umount /dev/sdx1 (to unmount the mounted partition)
Type mkfs.vfat -F 32 -n MULTIBOOT /dev/sdx1 (to format the partition as fat32)
Remove and reinsert your USB flash drive, or remount it
III. Install WINE:
To install WINE from within an Ubuntu operating environment, open a terminal and type sudo apt install wine and press enter. Once WINE is installed, launch YUMI as you normally would by simply clicking the YUMI-2.0.5.4.exe. Then load the ISO files.
CloneZilla/easy2boot Setup:
Remember: Some Live ISOs will need to have acpi=off added to the boot commandline, if they don't boot.
Commandline found at the bottom of the Live OS boot menu. Type acpi=off at the end.
Install your favorite OS on the Tinkerboard's microSD or Desktop Computer System.
Update and install all needed apps and config them.
1 Download and Install easy2boot for windows/linux. Select the USB and install. http://www.easy2boot.com/
2 Download clonezilla live iso. http://clonezilla.org/downloads.php
3 Copy the clonezilla.iso to the utilities. Copy linuxLive.iso to linux or gpartedLive.iso or windows10.iso to the windows folder.
4 Boot up with the usb drive that you installed/formatted with easy2boot.
5 Navigate to the utilities and select clonezilla.
6 Contiguous: When you delete any files in the usb you have to run the contiguous command on the easy2boot
usb drive. It will defrag the usb drive. The usb drive must not be fragmented.
Clonezilla steps:
Clonezilla (CZ) ver. 2.2.3.10-amd64
Important: Before Restoring use gparted to create one partition on the target and format it.
Take the TBos MicroSD to the other desktop and plug it into the usb. Use another internal or external drive to store the image to be created.
1 Run and select Clonezilla Default When ask to use .isoask, ignor it and let boot.
2 Enter ok for Engish, Don't touch keymap
3 Start-CZ Device-image work with disks or partitions using images
4 Select local_dev (USB, HDrive, SSD), Assign where CZ image will be saved/read for restoring It will be
mounted as Temporary /home/partimag.
5 Select sdb or sdc, Don't use the device you will be creating an image for.
6 Select / top_directory_in_the_local_device
7 Select Beginner mode: accept the default option
8 Select Save Disk saves local disk as image. If image is found, CZ will offer the restore option also.
9 Name the saved image, Remember: Don't use spaces or CZ will not recognize it.
10 Select the local disk to save, It will create an image of the device you chose and all of it's partitions and the MasterBootRecord (MBR).
11 If using Clonezilla zesty, it will make the mount /media/ owned by root.
You can change it with su or sudo chown -R username /media/driveMountName or /media/*
Then you can move/delete/copy images to the partition.
The Programmers make it root owned for security reasons. I don't have this problem anymore since I create the image on an external drive.
Don't create the image on the drive you are cloning.
Notes:
1 Clonezilla (CZ) ver. 2.2.3.10-amd64 put the image in the USB Drive and did not change the partition to root.
Looks like CZ ver. 2.2.5 works ok. It didn't make my partition drive root protected after image creation.
2 If there is an image in the same device partiton, CZ will offer the restore option with the save option.
3 CZ won't recognize an image or directory name with spaces in it.
4 Some motherboards/operating systems have to have acpi=off entered at boot time.
5 The drive must be unmounted to create an image of the drive. That's why it's important to boot from a USB/CD.
6 CZ copies the files, not any of the empty space. The Linux command dd copies empty space and files.
7 Drive Size:
Before Restoring format the USB drive/microSD with one partition.
If there is a small 500mb partition, CZ will say it's to small and fail to restore.
I restored using an image of a 16gb TBos to a 64gb USB thumbdrive.
If the destination drive is somewhat smaller than the image source, CZ will alert you to that issue. You can go
into expert mode and select -icds and at the next window select -k1. This will work as long as you know that the files will fit on the destination drive.
It will take 90 minutes or more because of the partition resizing. You don't want to do that unless you have too.
Example: say you have a 3.1gb microSD and a 29.4gb microSD. It's not going to restore, period. Nothing works. The destination has to be equal to or larger.
no way around it. So, do OS setup on the smallest drive, maybe a 16gb and then always restore to a 32gb or larger drive.
Flash the OS on the smaller microSD, update it, install all applications, and configure what you want.
Then create the CZ image using the smaller microSD. That way the image will fit on the larger drives.
Remember to use gparted to create only one partition and formated on the target to be restored.
8 Sync failure: If it fails to sync, just ignore that. I used the microSD and it booted just fine. Don't know yet what that Sync Issue is yet. Checking Inodes maybe.
Fix:
1 may use gparted to create ext4 microSD....one partition.
2 Use CZ Zesty and use restore>expertMode>-icsd>-k1 The -icsd and -k1 didn't work for me on any of my microSD.
3 When fscync fails do ctl/alt/delete to cancel before it trys to fix inodes.
4 I used a 16gb microSd to create image. Then restored onto a 32gb microSD with one partition formated using gparted.
5 CZ doesn't handle microSD very well. They shrink in size over time.
6 May have to restore again. microSD can be stuburn.
I bootup on a sandisk usb 16gb 3.0. Updated, installed all my apps, and fully configured. CZ image created in 3 minutes.
Reason is I can flash any drive larger than a 16gb one. Then use gparted to resize the partition fully.
The problem is some microSD chips can shrink in size and cause the problems.
Creating images is very easy, but restoring can give problems. Right now using a USB flash drive restored smoothly and fsyncing was successful.
Bootup with USB Drive:
Download tinker-os and flash to your SD card with etcher program.
Do the same with your desired usb-memory or usb-SSD or usb-HD that you want host tinker-os.
Shutdown your tinkerboard.
Turn on your tinkerboard booting only from SD card and no conected usb-disk.
Now on microSD tinker-os...
Code:
sudo pcmanfm
On the microSD go to.../boot/ and create old-extlinux folder and copy your current /boot/extlinux/extlinux.conf inside.
Open with leafpad /boot/extlinux/extlinux.conf
Edit extlinux.conf this way...
label kernel-4.4
kernel /zImage
fdt /rk3288-miniarm.dtb
# booting from SD...
# append earlyprintk quiet splash plymouth.ignore-serial-consoles console=tty1 rw init=/sbin/init
# booting from usb...
append earlyprintk quiet splash plymouth.ignore-serial-consoles root=/dev/sda2 console=tty1 rw init=/sbin/init
Save and exit.
Shutdown your tinkerboard.
Plug in on your tinkerboard your usb-SSD and turn on your tinkerboard with the SD-card in SD slot.
SD is mandatory to booting tinkerboard.
Now you are booting from SD-card and running tinker-os from usb-SSD or usb-HD or usb-memory.
Easy2boot:
For Linux version:
http://www.easy2boot.com/make-an-easy2bo...ing-linux/ howto
http://www.easy2boot.com/download/altern...oad-sites/ Download sites
1 Download and unzip the Easy2Boot file to a folder on your internal linux hard disk - use unrar or 7Zip to extract the files (sudo apt-get install 7zip).
2 Terminal \_ISO\docs\linux_utils folder (contains utilities and scripts)
3 Make all files executable (sudo chmod 777 *)
4 Type sudo ./fmt.sh or ./fmt_ntfs.sh (this requires the bash shell - if you are using the sh shell you will get errors - or try sudo bash ./fmt.sh)
Note: be sure to select the correct partition such as sdb1 or you will get a 'MISSING MBR HELPER' error message when you boot!). OS that don't use sudo may not work. Can try find/replace sudo in script file.
You can copy any other OS iso file to easy2boot usb.
Copy ubuntu.iso to the linux folder in the ISO folder.
Copy windows.iso to the the windows folder.
Copy utility applications to the utility folder.
When you delete any files in the usb you have to run the contiguous command on the easy2boot usb drive.
It will defrag the usb drive. The usb drive must not be fragmented.
There are other programs that will make bootable usbs. I like this one. You can drop an iso real quick and boot it. YUMI is good.
Remember the acpi=off issue with some motherboards that won't boot.
gpartedLive.iso is another one to add to the easy2boot utilities folder.
Defrag or Contiguous:
No need to defrag e2b usb drives.
https://rmprepusb.blogspot.com/2014/06/e...g-iso.html
Copy the largest iso on the e2b usb into the _ISO folder and rename it CONTIG.ISO.
It must not be larger than 3.999 gigs. Doesn't matter what data is in the ISO file.
Any defragged ISO file will be copied to CONTIG.ISO and run.
Does run faster if defragged as below: May not work with non-Debian OS.
udefrag is a 32-bit linux utility for NTFS drives.
To run udefrag for NTFS drives under Ubuntu 64-bit:
sudo dpkg --add-architecture i386 sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
1 (change to _ISO/docs/linux_utils folder)
2 sudo chmod 777 *
3 sudo udefrag -om /dev/sdX1 (where sdX1 is your NTFS USB partition)
Note: udefrag would not work on the TinkerboardOS v2.0.4
Almost was able to be rid of the need for windows. Maybe there is another way to defrag the usb with linux.
CloneZilla Live CD help:
You can also burn the CZ to a cd using k3b and boot it.
https://www.wikihow.com/Use-Clonezilla
https://www.techrepublic.com/blog/window...lonezilla/
https://sourceforge.net/p/clonezilla/bugs/168/
http://clonezilla.org/show-live-doc-cont...disk_image
I had worked on this method of cloning any OS System for some time now and solved some main issues.
It works very good, I am so glad not having to configure systems over and over. Saves a lot of time.
It looks like a lot to do, but once you create images and restore drives you will see it is very easy.
There is a forum for Clonezilla for help to solve any error issues. This will make you weak in configuring because you won't be doing it so often.
Always write solutions and configuration instructions in a text file so no time is wasted trying to figure something out later on. It's called an engineering book.
Best to have an engineering text file. You can do searches in it.
If you only want to use clonezilla live, simply download it and burn it to a cd/dvd drive and boot it.
https://clonezilla.org/
https://www.backup-utility.com/articles/...-4348.html
http://www.geekyprojects.com/storage/how...ler-drive/
Clonezilla steps:
Clonezilla (CZ) ver. 2.2.3.10-amd64 or for Intel
Important: Before Restoring use gparted to create one partition on the target and format it.
Take the TBos MicroSD to the other desktop and plug it into the usb. Use another internal or external drive to store the image to be created.
1 Run and select Clonezilla Default When ask to use .isoask, ignor it and let boot.
2 Enter ok for Engish, Don't touch keymap
3 Start-CZ Device-image work with disks or partitions using images
4 Select local_dev (USB, HDrive, SSD), Assign where CZ image will be saved/read for restoring It will be
mounted as Temporary /home/partimag.
5 Select sdb or sdc, Don't use the device you will be creating an image for.
6 Select / top_directory_in_the_local_device
7 Select Beginner mode: accept the default option
8 Select Save Disk saves local disk as image. If image is found, CZ will offer the restore option also.
9 Name the saved image, Remember: Don't use spaces or CZ will not recognize it.
10 Select the local disk to save, It will create an image of the device you chose and all of it's partitions and the MasterBootRecord (MBR).
11 If using Clonezilla zesty, it will make the mount /media/ owned by root.
You can change it with su or sudo chown -R username /media/driveMountName or /media/*
Then you can move/delete/copy images to the partition.
The Programmers make it root owned for security reasons. I don't have this problem anymore since I create the image on an external drive.
Don't create the image on the drive you are cloning.
Notes:
1 Clonezilla (CZ) ver. 2.2.3.10-amd64 put the image in the USB Drive and did not change the partition to root.
Looks like CZ ver. 2.2.5 works ok. It didn't make my partition drive root protected after image creation.
2 If there is an image in the same device partiton, CZ will offer the restore option with the save option.
3 CZ won't recognize an image or directory name with spaces in it.
4 Some motherboards/operating systems have to have acpi=off entered at boot time.
5 The drive must be unmounted to create an image of the drive. That's why it's important to boot from a USB/CD.
6 CZ copies the files, not any of the empty space. The Linux command dd copies empty space and files.
7 Drive Size:
Before Restoring format the USB drive/microSD with one partition.
If there is a small 500mb partition, CZ will say it's to small and fail to restore.
I restored using an image of a 16gb TBos to a 64gb USB thumbdrive.
If the destination drive is somewhat smaller than the image source, CZ will alert you to that issue. You can go
into expert mode and select -icds and at the next window select -k1. This will work as long as you know that the files will fit on the destination drive.
It will take 90 minutes or more because of the partition resizing. You don't want to do that unless you have too.
Example: say you have a 3.1gb microSD and a 29.4gb microSD. It's not going to restore, period. Nothing works. The destination has to be equal to or larger.
no way around it. So, do OS setup on the smallest drive, maybe a 16gb and then always restore to a 32gb or larger drive.
Flash the OS on the smaller microSD, update it, install all applications, and configure what you want.
Then create the CZ image using the smaller microSD. That way the image will fit on the larger drives.
Remember to use gparted to create only one partition and formated on the target to be restored.
8 Sync failure: If it fails to sync, just ignore that. I used the microSD and it booted just fine. Don't know yet what that Sync Issue is yet. Checking Inodes maybe.
Fix:
1 may use gparted to create ext4 microSD....one partition.
2 Use CZ Zesty and use restore>expertMode>-icsd>-k1 The -icsd and -k1 didn't work for me on any of my microSD.
3 When fscync fails do ctl/alt/delete to cancel before it trys to fix inodes.
4 I used a 16gb microSd to create image. Then restored onto a 32gb microSD with one partition formated using gparted.
5 CZ doesn't handle microSD very well. They shrink in size over time.
6 May have to restore again. microSD can be stuburn.
I bootup on a sandisk usb 16gb 3.0. Updated, installed all my apps, and fully configured. CZ image created in 3 minutes.
Reason is I can flash any drive larger than a 16gb one. Then use gparted to resize the partition fully.
The problem is some microSD chips can shrink in size and cause the problems.
Creating images is very easy, but restoring can give problems. Right now using a USB flash drive restored smoothly and fsyncing was successful.
Overview using a bootable USB:
1 Create a bootable USB.
2 Load cloning program>clonezilla,partimage on bootable USB.
3 Create restorable image of any drive with any OS.
Notes: Remember when creating cloned image to do check image, to verify it's good for restoring. CZ will tell you if it is a restorable image.
Make 2 images in case of corruption.
Yumi:
https://www.pendrivelinux.com/yumi-multi...b-creator/
Yumi Notes:
1 Yumi works in linux with wine installed. It is the easiest to work with but limited.
2 May have to use windows to get yumi to format the usb to fat32 the first time.
Dang! Still need a windows. At least only once the first time.
Then you can use yumi in linux to load iso files. Yumi shows the usb as ntfs even though it is fat32.
I tried formating the usb fat32 with gparted but it wouldn't boot. Must need yumi to format it.
3 Yumi is limited with live operating systems. Easy2boot does all.
4 Yumi will see iso and zip files. I would think iso would run faster.
5 No defragging required.
6 fat32 format is required. Don't know yet if ntfs will work.
Load clonezilla/partimage/gparted and you can burn backups of all devices.
7 Some Live ISOs will need to have acpi=off added to the boot commandline, if they don't boot.
8 If you have an application.img file, you can rename the .img to .iso and copy it to yumi/easy2boot and use it.
Note: Easier to just use YUMI in windows to format the usb drive.
This may eliminate the need for a windows running YUMI to format fat32
I. Format your USB Flash Drive to use a Single Partition in linux:
Open a terminal and type sudo su
Type fdisk -l (and note which device is your USB Drive)
Type fdisk /dev/sdx (replacing x with your actual usb device)
Type d (to delete the existing partition)
Type n (to create a new partition)
Type p (for primary partition)
Type 1 (to create the first partition)
Press Enter (to use the first cylinder)
Press Enter again (to use the default value as the last cylinder)
Type a (for active)
Type 1 (to mark the first partition active "bootable")
Type t (for partition type)
Type c (to use fat32 partition)
Type w (to write the changes and close fdisk)
II. Create a Fat32 Filesystem on the USB Flash Drive:
Type umount /dev/sdx1 (to unmount the mounted partition)
Type mkfs.vfat -F 32 -n MULTIBOOT /dev/sdx1 (to format the partition as fat32)
Remove and reinsert your USB flash drive, or remount it
III. Install WINE:
To install WINE from within an Ubuntu operating environment, open a terminal and type sudo apt install wine and press enter. Once WINE is installed, launch YUMI as you normally would by simply clicking the YUMI-2.0.5.4.exe. Then load the ISO files.
CloneZilla/easy2boot Setup:
Remember: Some Live ISOs will need to have acpi=off added to the boot commandline, if they don't boot.
Commandline found at the bottom of the Live OS boot menu. Type acpi=off at the end.
Install your favorite OS on the Tinkerboard's microSD or Desktop Computer System.
Update and install all needed apps and config them.
1 Download and Install easy2boot for windows/linux. Select the USB and install. http://www.easy2boot.com/
2 Download clonezilla live iso. http://clonezilla.org/downloads.php
3 Copy the clonezilla.iso to the utilities. Copy linuxLive.iso to linux or gpartedLive.iso or windows10.iso to the windows folder.
4 Boot up with the usb drive that you installed/formatted with easy2boot.
5 Navigate to the utilities and select clonezilla.
6 Contiguous: When you delete any files in the usb you have to run the contiguous command on the easy2boot
usb drive. It will defrag the usb drive. The usb drive must not be fragmented.
Clonezilla steps:
Clonezilla (CZ) ver. 2.2.3.10-amd64
Important: Before Restoring use gparted to create one partition on the target and format it.
Take the TBos MicroSD to the other desktop and plug it into the usb. Use another internal or external drive to store the image to be created.
1 Run and select Clonezilla Default When ask to use .isoask, ignor it and let boot.
2 Enter ok for Engish, Don't touch keymap
3 Start-CZ Device-image work with disks or partitions using images
4 Select local_dev (USB, HDrive, SSD), Assign where CZ image will be saved/read for restoring It will be
mounted as Temporary /home/partimag.
5 Select sdb or sdc, Don't use the device you will be creating an image for.
6 Select / top_directory_in_the_local_device
7 Select Beginner mode: accept the default option
8 Select Save Disk saves local disk as image. If image is found, CZ will offer the restore option also.
9 Name the saved image, Remember: Don't use spaces or CZ will not recognize it.
10 Select the local disk to save, It will create an image of the device you chose and all of it's partitions and the MasterBootRecord (MBR).
11 If using Clonezilla zesty, it will make the mount /media/ owned by root.
You can change it with su or sudo chown -R username /media/driveMountName or /media/*
Then you can move/delete/copy images to the partition.
The Programmers make it root owned for security reasons. I don't have this problem anymore since I create the image on an external drive.
Don't create the image on the drive you are cloning.
Notes:
1 Clonezilla (CZ) ver. 2.2.3.10-amd64 put the image in the USB Drive and did not change the partition to root.
Looks like CZ ver. 2.2.5 works ok. It didn't make my partition drive root protected after image creation.
2 If there is an image in the same device partiton, CZ will offer the restore option with the save option.
3 CZ won't recognize an image or directory name with spaces in it.
4 Some motherboards/operating systems have to have acpi=off entered at boot time.
5 The drive must be unmounted to create an image of the drive. That's why it's important to boot from a USB/CD.
6 CZ copies the files, not any of the empty space. The Linux command dd copies empty space and files.
7 Drive Size:
Before Restoring format the USB drive/microSD with one partition.
If there is a small 500mb partition, CZ will say it's to small and fail to restore.
I restored using an image of a 16gb TBos to a 64gb USB thumbdrive.
If the destination drive is somewhat smaller than the image source, CZ will alert you to that issue. You can go
into expert mode and select -icds and at the next window select -k1. This will work as long as you know that the files will fit on the destination drive.
It will take 90 minutes or more because of the partition resizing. You don't want to do that unless you have too.
Example: say you have a 3.1gb microSD and a 29.4gb microSD. It's not going to restore, period. Nothing works. The destination has to be equal to or larger.
no way around it. So, do OS setup on the smallest drive, maybe a 16gb and then always restore to a 32gb or larger drive.
Flash the OS on the smaller microSD, update it, install all applications, and configure what you want.
Then create the CZ image using the smaller microSD. That way the image will fit on the larger drives.
Remember to use gparted to create only one partition and formated on the target to be restored.
8 Sync failure: If it fails to sync, just ignore that. I used the microSD and it booted just fine. Don't know yet what that Sync Issue is yet. Checking Inodes maybe.
Fix:
1 may use gparted to create ext4 microSD....one partition.
2 Use CZ Zesty and use restore>expertMode>-icsd>-k1 The -icsd and -k1 didn't work for me on any of my microSD.
3 When fscync fails do ctl/alt/delete to cancel before it trys to fix inodes.
4 I used a 16gb microSd to create image. Then restored onto a 32gb microSD with one partition formated using gparted.
5 CZ doesn't handle microSD very well. They shrink in size over time.
6 May have to restore again. microSD can be stuburn.
I bootup on a sandisk usb 16gb 3.0. Updated, installed all my apps, and fully configured. CZ image created in 3 minutes.
Reason is I can flash any drive larger than a 16gb one. Then use gparted to resize the partition fully.
The problem is some microSD chips can shrink in size and cause the problems.
Creating images is very easy, but restoring can give problems. Right now using a USB flash drive restored smoothly and fsyncing was successful.
Bootup with USB Drive:
Download tinker-os and flash to your SD card with etcher program.
Do the same with your desired usb-memory or usb-SSD or usb-HD that you want host tinker-os.
Shutdown your tinkerboard.
Turn on your tinkerboard booting only from SD card and no conected usb-disk.
Now on microSD tinker-os...
Code:
sudo pcmanfm
On the microSD go to.../boot/ and create old-extlinux folder and copy your current /boot/extlinux/extlinux.conf inside.
Open with leafpad /boot/extlinux/extlinux.conf
Edit extlinux.conf this way...
label kernel-4.4
kernel /zImage
fdt /rk3288-miniarm.dtb
# booting from SD...
# append earlyprintk quiet splash plymouth.ignore-serial-consoles console=tty1 rw init=/sbin/init
# booting from usb...
append earlyprintk quiet splash plymouth.ignore-serial-consoles root=/dev/sda2 console=tty1 rw init=/sbin/init
Save and exit.
Shutdown your tinkerboard.
Plug in on your tinkerboard your usb-SSD and turn on your tinkerboard with the SD-card in SD slot.
SD is mandatory to booting tinkerboard.
Now you are booting from SD-card and running tinker-os from usb-SSD or usb-HD or usb-memory.
Easy2boot:
For Linux version:
http://www.easy2boot.com/make-an-easy2bo...ing-linux/ howto
http://www.easy2boot.com/download/altern...oad-sites/ Download sites
1 Download and unzip the Easy2Boot file to a folder on your internal linux hard disk - use unrar or 7Zip to extract the files (sudo apt-get install 7zip).
2 Terminal \_ISO\docs\linux_utils folder (contains utilities and scripts)
3 Make all files executable (sudo chmod 777 *)
4 Type sudo ./fmt.sh or ./fmt_ntfs.sh (this requires the bash shell - if you are using the sh shell you will get errors - or try sudo bash ./fmt.sh)
Note: be sure to select the correct partition such as sdb1 or you will get a 'MISSING MBR HELPER' error message when you boot!). OS that don't use sudo may not work. Can try find/replace sudo in script file.
You can copy any other OS iso file to easy2boot usb.
Copy ubuntu.iso to the linux folder in the ISO folder.
Copy windows.iso to the the windows folder.
Copy utility applications to the utility folder.
When you delete any files in the usb you have to run the contiguous command on the easy2boot usb drive.
It will defrag the usb drive. The usb drive must not be fragmented.
There are other programs that will make bootable usbs. I like this one. You can drop an iso real quick and boot it. YUMI is good.
Remember the acpi=off issue with some motherboards that won't boot.
gpartedLive.iso is another one to add to the easy2boot utilities folder.
Defrag or Contiguous:
No need to defrag e2b usb drives.
https://rmprepusb.blogspot.com/2014/06/e...g-iso.html
Copy the largest iso on the e2b usb into the _ISO folder and rename it CONTIG.ISO.
It must not be larger than 3.999 gigs. Doesn't matter what data is in the ISO file.
Any defragged ISO file will be copied to CONTIG.ISO and run.
Does run faster if defragged as below: May not work with non-Debian OS.
udefrag is a 32-bit linux utility for NTFS drives.
To run udefrag for NTFS drives under Ubuntu 64-bit:
sudo dpkg --add-architecture i386 sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
1 (change to _ISO/docs/linux_utils folder)
2 sudo chmod 777 *
3 sudo udefrag -om /dev/sdX1 (where sdX1 is your NTFS USB partition)
Note: udefrag would not work on the TinkerboardOS v2.0.4
Almost was able to be rid of the need for windows. Maybe there is another way to defrag the usb with linux.
CloneZilla Live CD help:
You can also burn the CZ to a cd using k3b and boot it.
https://www.wikihow.com/Use-Clonezilla
https://www.techrepublic.com/blog/window...lonezilla/
https://sourceforge.net/p/clonezilla/bugs/168/
http://clonezilla.org/show-live-doc-cont...disk_image
![[-]](https://tinkerboarding.co.uk/forum/images/collapse.png)