Install Linux OS to a USB stick or SD card
There are several Open Source tools for this purpose over the internet lets have a look at some here.

Fusbi is a unetbootin clone with minor tweaks which, for example, enable you to more easily select SD cards as a target device.
UNetbootin
http://unetbootin.sourceforge.net/
see https://help.ubuntu.com/community/Installation/FromUSBStick
This utility automates pretty much the entire process and is available for both linux and windos. It also supports lots of Linux distributions so that you simply have to choose the one you wish from the drop down menu and it takes care of locating it and downloading and installing it.
(These instructions are more Windows Oriented. Linux users can probably determine what the relevant UI conventions I am referring to on their system)
- Download the ISO you wish to install.
- Download Unetbootin.
- Back up everything on your flash drive. While this program usually isn’t harmful to the data on a flash drive, paranoia is a very good thing in this sort of situation.
- install Unetbootin dependencies. On ubuntu it should beĀ :
sudo aptitude install mtools p7zip-full
- Run Unetbootin and select the ISO option, then click the ‘browse’ or ‘…’ button to select the ISO file itself. Select which drive you desire to turn into a Live USB installation thingy.
- Click ‘Next’ and go find some way to amuse yourself in the few minutes it takes for the program to do its thing.
- Once it is done it will ask if you wish to Reboot Now or Exit. In the unlikely event you prepared this on an EeePC running WinXP then by all means Reboot. Otherwise, that would be silly and you should just select the ‘Exit’ option.
- Huzzah! You should now have a working USB Live install thingy.
In Unetbootin as well as in Fusbi you have to pay attention to set the bootable partition in the partition editor (gparted or qparted in linux) with flags boot and lba. Otherwise the device would fail to boot.
The device would still fail to boot if there is no support in the computer BIOS for booting from USB (most computers nowadays do have it though) or from MemoryCard controller (only a few devices have this capability). You can figure it out in the BIOS boot up sequence.
Often UNetbootin and Fusbi fail to write the MBR on the device. This results in the system not booting and hanging with a black screen and a blinking cursor. This IS DEFINITELY an MBR problem. If you are playing with an Ubuntu derivative please give usb-creator a try, it has always managed to smoothly do its work so far.
Doublecheck also if the USB/MemoryCard device has the write protecting lock switch on, in case disable it.
Ubuntu usb-creator
This is a simple utility designed to make bootable USB desktop images from
Ubuntu CDs. It also works with all *buntu derivates.
Differently from UNetbootin and Fusbi it always manages to set the correct MBR to the USB device for it to boot correctly.
You can install it with
sudo apt-get install usb-creator
LiveUSB
Use http://klik.atekon.de/liveusb/
- add the PPA for your system – see https://launchpad.net/~probono/+archive. On Hardy, I added the following line to my sources.list
deb http://ppa.launchpad.net/probono/ubuntu hardy main
- Install the liveusb package
sudo apt-get update sudo apt-get install liveusb
- Mount your iso file to /cdrom
sudo mount -o loop ubuntu-eee-804.iso /cdrom/
- Run liveusb and follow the instructions
- Now your LiveCD is burned on the USB key, install Ubuntu and follow the rest of the instructions on this page.
How to configure a USB stick manually
see http://wiki.eeeuser.com/ubuntu
- In a running Ubuntu, Kubuntu or Xubuntu environment, install the “syslinux” and “mtools” packages. Open up a terminal and write:
sudo apt-get install syslinux mtools
- Download the script:
wget http://download.ubuntu-fr-secours.org/isotostick.sh
- Make the script excutable:
chmod +x isotostick.sh
- OPTIONAL: format the drive as FAT32
sudo mkfs.vfat -F 32 -n ubuntueee /dev/sdX1
- or alternatively as ext2 (some report success only after doing this):
sudo mkfs.ext2 /dev/sdX1
- Before running the script, the usb key partition must be marked as bootable or the script complains “Partition isn’t marked bootable!”
- Replace /dev/sdX with the device node of usbdrive (example: sdb and not sdb1)
sudo parted /dev/sdX set 1 boot on
- Then run the script, replace /dev/sdX1 with the partition where you want to put the image.:
sudo ./isotostick.sh image.iso /dev/sdX1
- Finally, make it bootable using syslinux. For FAT32:
sudo syslinux /dev/sdX1
- for ext2:
sudo extlinux [directory where device is mounted] --install
- According to the Fedora 8 release notes, this is not a destructive process and any data you currently have on your USB stick is preserved.
- Shutdown the Eee PC and remove the battery for a few seconds before attempting to start the Eee PC again. Some 4G 701 (non-surf) devices fail to obtain link-status with the ethernet port unless power is completely removed. (You may need to do this again after using the USB live stick to install ubuntu on your system)
- Insert the USB stick in the Eee, and reboot it. You should be able to use the Esc key during the boot sequence to bring up a boot menu, but you have to be quick! Or you can use F2 to access the BIOS, and change the hard drive sequence to put the USB stick first.
Boot->Hard Disk Drives (not Boot Priority!) and make [USB:whatever] the top one.
This is not “sticky”, it will revert to normal after one boot.
- Then Ubuntu/Kubuntu will boot, and you can complete the installation process in the usual way. Remember to format the disk manually, and leave the two very small partitions alone. The large one will already be formatted Ext2, but should be reformatted and set to be mounted as /. The small one (1.3GB) will be Ext3, and should also be formatted as Ext2 and be set to mount as /home. But your partitioning needs may vary.
- During installation, in Kubuntu at least, some of the dialogue screens are too large to be displayed properly. This has also been known to affect desktop users whose graphics card has defaulted to 640*480 or similar. To move any window around, ALT-LeftMouse with cursor anywhere on the window, and drag as required.
- After completing this installation process, and rebooting your eee pc, your /etc/fstab file will have an incorrect entry for a cdrom drive. This is a problem, because it interferes with your ability to mount a usb drive (which will be assigned the same device name as the fictional cdrom drive). To remove the erroneous entry from your fstab file, open a terminal and
sudo gedit /etc/fstab
or for Kubuntu users,
kdesu kate /etc/fstab
and find the line that says
/dev/sdc1 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
and **delete** it (or comment it out). Hit save and close the text editor.
- You will also have an entry in your /etc/apt/sources.list file for your LiveCD. Synaptic doesn’t complain about it, but apt-get will, if this is a problem, open a terminal and
sudo gedit /etc/apt/sources.list
and find the line that says
deb cdrom:[Ubuntu 7.10 _Gutsy Gibbon_ - Release i386 (20071016)]/ gutsy main restricted
and **delete** it (or comment it out). Hit save and close the text editor.
Most information is taken from: http://wiki.geteasypeasy.com/Install:_from_a_Live_Ubuntu_image_on_a_USB_stick
Related posts:
- ext3 > ext2
- Enable larger persistent data for Linux Live on SolidState or USB devices
- rescuing lost partitions and partition data for linux
- ext2 > ext3
- problems mounting usb drive after installing from usb
- Chrooting: how to gain access to a bricked install
- how to install 32bit deb on 64bit system
Print This Post
|
Email This Post
Unetbootin is great I have used it may times, but it does not like spaces in the mount point for the USB drive.
When the stick is automounted it usually uses the internal name as a guide and my stick created a directory called ‘/media/usb 2.0′ or similar. When unetbootin tries to write to this folder it ended up choping off the filename after the space and creating a new folder /media/usb.
If you mount the usb stick manually first to a safe mount point without spaces everything works perfectly, and it seems to remember the setting in the future when automounting (in Jaunty)
BobCFC thank you for commenting!
Unfortunately that does not seem to be my case since there were no spaces in the mount point path. I guess the problem is in how Unetbootin handles Memory Cards.
I dont usually reply to posts but in this case. WOW
This article is very interesting, keep us posting..