Creating files containing ext2/3/4 filesystems for persistence
Test using QEMU under linux
Restore E2B partitions under Linux
How to make an E2B USB drive using linux
First ensure your USB drive has two Primary Partitions. I suggest:
Ptn1: Primary Active (Max 128GB) - will be formatted by script
Ptn2: Primary FAT32 (max 32GB)
Use GParted or a similar partitioning tool.
The .sh scripts provided will format an existing partition, then it will copy the E2B files onto it and then run bootlace to install grub4dos:
Download and unzip the Easy2Boot .ZIP file to a folder on your internal linux hard disk - use unrar or 7Zip to extract the files (sudo apt-get install 7zip).
Open a Terminal session at the \_ISO\docs\linux_utils folder (contains utilities and scripts)
Use chmod to make the files in linux_utils executable (sudo chmod 777 *)
Type ./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 sdb1or you will get a 'MISSING MBR HELPER' error message when you boot!).
You can install E2B to an existing partition on a USB drive using the /_ISO/docs/linux_utils/fmt.sh (FAT32) or fmt_ntfs.sh (NTFS) linux bash shell script which is included in the Easy2Boot download files (v1.83+).
Note: if you get a 'permission denied' error, precede the command with sudo.
unrar x Easy2Boot.zip (or unzip Easy2Boot*.zip -d Easy2Boot/)
sudo su -
cd _ISO/docs/linux_utils (or cd Easy2Boot/_ISO/docs/linux_utils)
sudo chmod 777 * (or chmod u+x *)
sudo bash ./fmt.sh (or sudo bash ./fmt_ntfs.sh)
For a 64-bit system, you will need to install i386 support (use the add-32-bit-support.sh script or see below).
See here for details on agFM. Updating is done in the same way.
Copying payload files
After you have run the E2B format .sh script, you should copy your payload files onto the USB drive.
Tip: Never download an ISO directly on to the USB drive because the file may be heavily fragmented (due to multiple download threads being used). Always download the ISO to your internal hard disk first and then copy it to the USB drive.
See here for details of where to copy your payload files.
After copying payload files, make sure that all files are contiguous (see below).
If you have problems making files contiguous when the drive becomes full, you may find it quicker to use this method:
1. Delete the 500MB \_ISO\CONTIG.ISO file from the download folder (to improve the copy speed)
2. Add all your ISO files, etc., into the download folder structure
3. Run fmt.sh or fmt_ntfs.sh to make a new E2B drive
4. Defrag the drive (usually not necessary because the drive is freshly formatted)
Making files contiguous
Most ISOs and all persistence files need to be contiguous for best and fastest use.
Windows .VHD and .WIM files don't need to be contiguous.
Note that if you are using large ISOs, you will need a much larger drive because at least as much contiguous free space is needed (e.g. a non-contiguous 3GB ISO on an 8GB NTFS drive cannot be made contiguous because there is not enough free space!).
Fig. 1 FILE4 cannot be de-fragmented due to insufficient contiguous free space. The free clusters must first be consolidated (e.g. by using Windows Defraggler).
Note: NTFS volumes will usually have directory files ($MFT) at the 3GB point - these files cannot be moved.
Defragging a volume, or making files contiguous on a volume, may not always be successful due to lack of contiguous free space.
(change to _ISO/docs/linux_utils folder)sudo chmod 777 *
sudo ./udefrag -om /dev/sdX1 (where sdX1 is your NTFS USB partition) - use -qvm instead of -om for quicker optimisation.
Tip: If you have problems making files contiguous, copy your ISO files into the source download E2B folder structure on your internal linux hard disk first, and then run the fmt_ntfs.sh script to copy all the files to the USB drive.
Untested to defrag whole NTFS partition:
Type "su" and enter password for root when prompted.
Type "fsck -t ntfs --kerneldefrag /dev/sdX1" without quotes. Replace "sdX1" with the drive letter of your E2B disk.
The linux scripts only format a pre-existing partition on your USB drive.
For best bootability/compatibility with all systems, your E2B USB drive should contain 2 PRIMARY PARTITIONS.
The second primary partition can be very small and unformatted or it can be larger and formatted - it just needs to be there!
Some BIOSes will not boot from a USB Flash drive correctly unless there are two or more primary partitions. If there is only one Primary partition, some BIOSes will attempt to boot from the USB drive as a floppy disk or super-floppy or ZIP drive and grub4dos will fail to boot correctly.
Also, for best compatibility, you should ensure that the E2B partition is marked as 'Active' (has the boot flag set) and that grub4dos is installed to both the MBR (LBA0) and the Partition Boot Record of the E2B partition (PBR).
The presence of valid EFI boot files can prevent some BIOSes from booting to the E2B grub4dos menu - they will always try to EFI-boot instead!
If you are booting a linux ISO and it cannot be made contiguous, E2B will use a similar technique to MultiSystem, XBOOT or YUMI and try to boot from the ISO using known linux cheat code parameters ('isoboot'). However, only some linux distros are supported and this method may not work on new releases because new versions seem to always change the boot parameters!
[SHIFT]+[ENTER] - If you hold down the SHIFT key before you press the ENTER key, E2B will only use isoboot to attempt to boot a linux ISO.
Use a .isoboot file extension if you always want to boot an ISO using ISOBOOT (E2B v1.A8+).
Creating files containing ext2/3/4 filesystems for persistence
Linux LiveCD ISOs + persistence can be made using .mnu files. See here for more details.
For persistence, you often need to create a persistence file which is formatted internally as an ext2/3/4 filesystem (instructions are always inside the .mnu file). To do this under linux AND have it contiguous (which is required for E2B) - see the thread here.
Use cd to get to the directory where you have mounted the USB drive - e.g. /media/USBDrive, then create a file as follows (example uses 1GB mint-rw, volume name is normally casper-rw):
dd if=/dev/zero of=mint-rw bs=1M count=1024
mkfs -t ext2 mint-rw -L casper-rw
or for ext3 (recommended because ext2 can be easily corrupted!):
mkfs.ext3 -F mint-rw -L casper-rw
Making a sparse file using dd may be faster (untested), try this...
"/dev/sdc" is the usb device as listed by fdisk, 512 is the amount of memory to allocate.
Note that QEMU may prevent or delay normal file writes during or after use. After using QEMU, run sync and check that any changes you have made to the E2B drive have actually occured by dismounting and removing the E2B USB drive and re-connecting it again - then check the file contents.
Unfortunately, there is no linux equivalent of the MakePartImage.cmd Windows script which makes .imgPTN files.
You can run Windows from a Virtual Machine under linux and use the MakePartImage scripts from within Windows.
If you want to try UEFI-booting to linux ISOs add the agFM files to the second FAT32 partition.
Restore E2B partition after booting to Linux from a .imgPTN file (E2B v1.A9+)
If you have switched to a .imgPTN file and booted to Linux, you can run the Restore_E2B.sh script to restore the E2B partitions.
1. Type Ctrl+Alt+t at the desktop to get a terminal window
2. cd to the /e2b/ folder on the USB drive - e.g. cd /cdrom/e2b (type lsblk to find the USB drive's mountpoint)
3. Type sudo bash Restore_E2B.sh
4. Enter the device path of the USB drive - e.g. /dev/sdb
IMPORTANT: Very little checking is done by the script - make sure you select the correct drive!
Under Ubuntu, the command can be shortened to sudo bash /cdrom/e2b/Restore_E2B.sh
If necessary, you may have to type these commands instead to make the file executable...
sudo cp Restore_E2B.sh /home/
sudo chmod u+x Restore_E2B.sh
sudo bash /home/Restore_E2B.sh
Under linux, the USB drive contents will not appear to change until you unplug&reinsert or reboot (you can try sudo partx -u /dev/sdX but it may not work if the drive is mounted and locked).
When you reboot from the USB drive, the MBR E2B menu system will load.
If you have an older version of a .imgPTN file which does not contain the Restore_E2B.sh script, you can copy the file to the /e2b folder on the USB drive after you have switched it in.
These must be made using Windows to run the MakePartImage.cmd script.
However, you can mount these files under linux using a command like:
mount -o loop arch.imgPTN /mnt
Once mounted, you can modify the contents as desired, before unmount and sync is used.