How to create and use Live USB

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Another graphical method: using UNetbootin: spelling)
m (Command line method: Using the livecd-iso-to-disk tool (Fedora only): italics)
(One intermediate revision by one user not shown)
Line 122: Line 122:
 
Note that the process will take some time and you will not see any information while it is running.
 
Note that the process will take some time and you will not see any information while it is running.
  
=== Command line method: Using the {{command|livecd-iso-to-disk}} tool (Fedora only) ===
+
=== Command line method: Using the ''livecd-iso-to-disk'' tool (Fedora only) ===
  
The {{command|livecd-iso-to-disk}} is the most capable and often most reliable method of writing a Fedora ISO image to a USB stick, but can only reliably be used from within Fedora. It does not work in Windows and is not supported (and will usually fail) in non-Fedora distributions. Please use the liveusb-creator tool, dd (or an equivalent tool), or a third-party tool such as unetbootin on other operating systems. It is also not a good idea to try and write a new Fedora release using the version of {{command|livecd-iso-to-disk}} in a much older Fedora release: it is best to only use a release a maximum of two versions older than the release you are trying to write.
+
The ''livecd-iso-to-disk'' is the most capable, non-destructive, and often most reliable method of writing a Fedora ISO image to a USB stick, but it can be used reliably only from within Fedora. It does not work in Windows and is not supported (and will usually fail) in non-Fedora distributions. Please use the ''liveusb-creator'' tool, ''dd'' (or an equivalent tool), or a third-party tool such as ''UNetbootin'' on other operating systems. It is also not a good idea to try and write a new Fedora release using the version of ''livecd-iso-to-disk'' in a much older Fedora release: It is best to only use a release a maximum of two versions older than the release you are trying to write.
 +
 
 +
Make sure the ''livecd-tools'' RPM is installed with the command
 +
 
 +
: {{Code|rpm -q livecd-tools}}.
  
Make sure the livecd-tools RPM is installed with the command {{command|rpm -q livecd-tools}}.
 
 
You will see the name of the RPM and a version number if it is installed, or no output if it is not installed.
 
You will see the name of the RPM and a version number if it is installed, or no output if it is not installed.
  
If "livecd-tools" is not installed, install it using this command, or PackageKit: {{command|su -c 'yum install livecd-tools'}}
+
If ''livecd-tools'' is not installed, install it using this command, or PackageKit:
  
Detailed usage information is available in the first pages of the [http://git.fedorahosted.org/cgit/livecd/tree/tools/livecd-iso-to-disk.sh#n27 livecd-iso-to-disk script], which you can also see by running {{command|su -c 'livecd-iso-to-disk --help'}}. Basic examples follow.
+
: {{Code|su -c 'yum install livecd-tools'}}
  
To make an existing USB stick bootable as a Fedora image without deleting any of the data on it, make sure that the USB drive is not mounted before executing the following, and give the root password when prompted: {{command|su -c "livecd-iso-to-disk Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"}}
+
Detailed usage information is available in the first pages of the [http://git.fedorahosted.org/cgit/livecd/tree/tools/livecd-iso-to-disk.sh#n27 livecd-iso-to-disk script], which you can also see by running this command:
 +
 
 +
: {{Code|su -c 'livecd-iso-to-disk --help'}}
 +
 
 +
Basic examples follow.
 +
 
 +
To make an existing USB stick bootable as a Fedora image—without deleting any of the data on it—make sure that the USB drive is not mounted before executing the following, and give the root password when prompted:
 +
 
 +
: {{Code|su -c "livecd-iso-to-disk Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"}}
  
 
See [[#Data persistence|Data persistence]] below for how to create Live USB devices with more than temporary storage of user files and settings.
 
See [[#Data persistence|Data persistence]] below for how to create Live USB devices with more than temporary storage of user files and settings.
  
 
In case it is not possible to boot from a disk created with the method shown above, before re-partitioning and re-formatting, often resetting the master boot record will enable booting:
 
In case it is not possible to boot from a disk created with the method shown above, before re-partitioning and re-formatting, often resetting the master boot record will enable booting:
{{command|su -c "livecd-iso-to-disk --reset-mbr Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"}}
 
  
{{admon/warning | CAUTION | The following method will erase all data on the USB drive!  Please read the instructions below ''carefully''.}}
+
: {{Code|su -c "livecd-iso-to-disk --reset-mbr Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"}}
If necessary, you can have {{command|livecd-iso-to-disk}} re-partition and re-format the target stick: {{command|su -c "livecd-iso-to-disk --format --msdos --reset-mbr Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"}}
+
 
 +
{{admon/warning | CAUTION: | Using the {{Code|--format}} option in the following command will erase all data on the USB drive!  Please read the instructions below ''carefully''.}}
 +
: If necessary, you can have ''livecd-iso-to-disk'' re-partition and re-format the target stick:
 +
 
 +
: {{Code|su -c "livecd-iso-to-disk --format --msdos --reset-mbr Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"}}
  
 
==== UEFI boot of USB sticks ====
 
==== UEFI boot of USB sticks ====
  
Whether a Fedora image written to a USB stick will be bootable natively via [[wikipedia:UEFI|UEFI]] is a somewhat complex question which depends on the Fedora release, the type of image (live or non-live), and the method used to write it. The {{command|--efi}} parameter to the {{command|livecd-iso-to-disk}} tool attempts to make a stick written with that tool natively UEFI bootable.
+
Whether a Fedora image written to a USB stick will be bootable natively via [[wikipedia:UEFI|UEFI]] is a somewhat complex question which depends on the Fedora release, the type of image (live or non-live), and the method used to write it. The {{Code|--efi}} parameter to the ''livecd-iso-to-disk'' tool attempts to make a stick written with that tool natively UEFI bootable.
  
As of {{FedoraVersion|long|17}}, all images written using the ''dd'' method should be UEFI-bootable, and all images written with {{command|livecd-iso-to-disk --format --reset-mbr --efi}} should also be UEFI-bootable. Use of {{command|--efi}} without {{command|--format}} and {{command|--reset-mbr}} can be considered a 'best effort', and may not produce a UEFI-bootable stick.
+
As of {{FedoraVersion|long|17}}, all images written using the ''dd'' method should be UEFI-bootable, and all images written with {{Code|livecd-iso-to-disk --format --reset-mbr --efi}} should also be UEFI-bootable. Use of {{Code|--efi}} without {{Code|--format}} and {{Code|--reset-mbr}} can be considered a 'best effort', and may not produce a UEFI-bootable stick.
  
 
==== Creating a USB stick from a running live environment ====
 
==== Creating a USB stick from a running live environment ====
  
If you are already running a live CD, DVD, or USB and want to convert that into a bootable USB stick, run the following command: {{command|su -c "livecd-iso-to-disk /run/initramfs/livedev /dev/sdX"}}
+
If you are already running a live CD, DVD, or USB and want to convert that into a bootable USB stick, run the following command:
 +
 
 +
: {{Code|su -c "livecd-iso-to-disk /run/initramfs/livedev /dev/sdX"}}
  
 
(For versions before Fedora 17, use {{Code|/dev/live}} instead of {{Code|/run/initramfs/livedev}}.)
 
(For versions before Fedora 17, use {{Code|/dev/live}} instead of {{Code|/run/initramfs/livedev}}.)
Line 161: Line 177:
 
Use the ''Graphical Method'' described above to do this easily. There is a graphical slider in the interface you can use to assign space on the target stick for persistent storage.
 
Use the ''Graphical Method'' described above to do this easily. There is a graphical slider in the interface you can use to assign space on the target stick for persistent storage.
  
If using the {{command|livecd-iso-to-disk}} tool, add the {{command|--overlay-size-mb}} parameter to add a persistent data storage area to the target stick. For example: {{command|su -c "livecd-iso-to-disk --overlay-size-mb 512 Fedora-16-x86_64-Live-Desktop.iso /dev/USBPARTITIONNAME"}}
+
If using the ''livecd-iso-to-disk'' tool, add the {{Code|--overlay-size-mb}} parameter to add a persistent data storage area to the target stick. For example:
  
where 512 is the desired size (in megabytes) of the overlay. The [[livecd-iso-to-disk]] tool will not accept an overlay size value greater than 4095 for VFAT, but for ext[234] filesystems it is only limited by the available space.  
+
: {{Code|su -c "livecd-iso-to-disk --overlay-size-mb 512 Fedora-16-x86_64-Live-Desktop.iso /dev/USBPARTITIONNAME"}}
 +
 
 +
where 512 is the desired size (in megabytes) of the overlay. The ''[[livecd-iso-to-disk]]'' tool will not accept an overlay size value greater than 4095 for VFAT, but for ext[234] filesystems it is only limited by the available space.  
 
{{anchor|limited overlay}}
 
{{anchor|limited overlay}}
 
{{admon/note | Limited Lifetime of Persistent Overlay | One very important note about using the "primary" persistent overlay for system changes is that due to the way it's currently implemented (as a [[wikipedia:Device mapper|Device-mapper]] copy-on-write snapshot), every single change to it (writes AND deletes) subtracts from its free space, so it will eventually be "used up" and your USB stick will no longer boot (see this [http://thread.gmane.org/gmane.linux.kernel.device-mapper.devel/14644 dm-devel discussion] and [[LiveOS_image#Overlay_recovery|this page]] for emergency recovery). Because of these limitations, it is advisable to use the system-level persistence sparingly, for configuration changes and important security updates only. Or, if you have sufficient disk space available, changes to the LiveOS root filesystem snapshot can be merged into a new copy of the root filesystem.  See [[LiveOS image#Merge overlay into new image|this page section]] for instructions.
 
{{admon/note | Limited Lifetime of Persistent Overlay | One very important note about using the "primary" persistent overlay for system changes is that due to the way it's currently implemented (as a [[wikipedia:Device mapper|Device-mapper]] copy-on-write snapshot), every single change to it (writes AND deletes) subtracts from its free space, so it will eventually be "used up" and your USB stick will no longer boot (see this [http://thread.gmane.org/gmane.linux.kernel.device-mapper.devel/14644 dm-devel discussion] and [[LiveOS_image#Overlay_recovery|this page]] for emergency recovery). Because of these limitations, it is advisable to use the system-level persistence sparingly, for configuration changes and important security updates only. Or, if you have sufficient disk space available, changes to the LiveOS root filesystem snapshot can be merged into a new copy of the root filesystem.  See [[LiveOS image#Merge overlay into new image|this page section]] for instructions.
Line 169: Line 187:
 
See [[#Mounting a Live USB filesystem|this section]] for mounting the root filesystem outside of a boot.
 
See [[#Mounting a Live USB filesystem|this section]] for mounting the root filesystem outside of a boot.
  
For normal, write-many storage, use the ''--home-size-mb'' option to create a home directory filesystem for personal files. Home.img can be re-used and loop mounted outside of the Live USB environment.}}
+
For normal, write-many storage, use the {{Code|--home-size-mb}} option to create a home directory filesystem for personal files. Home.img can be re-used and loop mounted outside of the Live USB environment.}}
The persistent overlay status may be queried by issuing this command on the live system: {{command|dmsetup status live-rw}}
+
The persistent overlay status may be queried by issuing this command on the live system:
 +
 
 +
: {{Code|dmsetup status live-rw}}
  
 
The returned value may look like this:
 
The returned value may look like this:

Revision as of 08:33, 13 December 2013

Artwork DesignService fedora-iso-usb.png

This page explains how to create and use Fedora USB media. A Live USB system stored on flash memory, sometimes called a stick, lets you boot any USB-bootable computer into a Fedora operating system environment without writing to that computer's hard disk. The Live USB stick can feature an area to store changes to the system, called a persistent overlay. It can also have a separate area to store user account information and data such as documents and downloaded files, with optional encryption for security and peace of mind. Finally, with a non-destructive installation, pre-existing files and excess storage space on the stick are accessible from the system. Essentially, you can carry your computer with you in your pocket, booting it on nearly any system you find yourself using.

With current Fedora releases you can also write the non-live Fedora installation images (the DVD and network installation images) to a USB stick, which many users find more convenient and faster than writing to an actual optical disc.

Note.png
Quick start
The process for most people is simple. Almost all USB sticks are provided by hardware manufacturers ready to use with this process. If you have any documents on your USB stick, it's not a bad idea to back them up before you start.

Then reboot your system and use your computer's built-in function to choose the USB boot device -- usually this is a special key you hold down at boot time, such as F12. Then enjoy!

If you are into technical details or want more information on alternative tools and advanced usage, please read on.

Contents


Important.png
Creating Live CD ISO image
A Live USB system is created from the same ISO image file that is used to create Live CD/DVD media. You can download ISO images for the official Fedora release from the Fedora download site. Consult How to create and use a Live CD for more information on creating your own customized ISO image file.

System Requirements

  • A working computer running GNU/Linux, Windows or MacOS.
  • A USB flash drive, also known as USB stick, thumb drive, pen drive, or jump drive, with 1 GB or more of storage space.
  • A Fedora ISO file, which you can download from http://fedoraproject.org/get-fedora.

Ability to boot from USB media

  • Not all computers can boot from USB media, due to different BIOS settings and system capabilities. If your computer cannot do so, this procedure will not be useful. If you are not sure and don't mind downloading and installing an image on your USB drive (possibly wiping its data), the only risk is wasting some time.
  • If your USB stick is not in working order, this procedure may fail. Watch for error messages during the process.

GNU/Linux instructions

Identifying your USB disk

The first step is to identify the name of the USB drive partition.

  • Insert the USB stick into a USB port.
  • Open a terminal and run dmesg.
  • You will see something like
[32656.573467] sd 8:0:0:0: [sdX] Attached SCSI removable disk

where sdX will be sdb, sdc, sdd, etc. Take note of this label as it is the name of the disk you will use. We'll call it sdX from now on.

Checking USB disk size

As noted before, the disk must have at least 1 GB of storage space. You can check this by running the df -h command. Look for a line like the following:

/dev/sdX1             3.9G  4.0K  3.9G   1% /media/usbdisk

and make sure the first column reads more than 1.0G.

You can also use a file manager like nautilus, by right clicking and selecting Properties:

Properties USB size.png

Writing the image

Graphical method: using liveusb-creator (Windows/Fedora only)

Fedora Live USB creator.png

Fedora USB sticks can be created using the liveusb-creator utility. Note that this utility is only capable of writing Live images.

You can use Add/Remove Programs and search for liveusb-creator, or use the command line:

su -c 'yum install liveusb-creator'

To start, run liveusb-creator on the command line or search liveusb-creator on the GNOME activities overview.

To use the tool, simply select a Fedora release to download from the drop-down box at top-right (or select an ISO you have already downloaded using the Browse button at top-left), select the USB stick to which you wish to write the image from the Target Device drop-down box, and hit the Create Live USB button.

Another graphical method: using UNetbootin

Warning (medium size).png
About UNetbootin
Following each release, Fedora support volunteers receive reports of problems with installation images created by UNetbootin. Using the most recent version of UNetbootin available has been known to improve results.
  1. There is no persistent storage for operating or user filesystem changes with this installation method for Fedora—any file changes on those filesystems will be lost on shutdown. (Files written to the USB device filesytem, mounted at /run/initramfs/live, are persistent.)
  2. It is easiest to start with an empty device filesystem—a device with another Live installation can leave files that interfere with the new installation.
While your results may vary, it is usually the case that the liveusb-creator, livecd-iso-to-disk, and dd methods give better results than UNetbootin. If you encounter problems with UNetbootin, please contact the UNetbootin developers, not the Fedora developers.

UNetbootin is a graphical, bootable USB image creator. Using it will allow you to preserve any data you have in the USB drive.

Unetbootin gtk3.png

  • Download UNetbootin latest version from http://unetbootin.sourceforge.net/ and install it.
  • You might have to type the root password when running it.
  • Click on Diskimage and search for the ISO file you downloaded.
  • Select Type: USB drive and choose sdX drive.
  • Press OK.
Note.png
Note
If you do not see sdX listed, you might have to reformat the drive, effectively loosing all your data on the drive:
su -c "umount /dev/sdX"
su -c "mkfs.vfat -I /dev/sdX"
.

Simple command line method: write the image directly

Warning (medium size).png
CAUTION
This will erase all data on the USB drive! Please read the instructions below carefully and make sure you write the right drive label (sdX).

To write the ISO file directly to the disk, run:

su -c "dd if=/Users/me/Downloads/Fedora-17-x86_64-DVD.iso of=/dev/sdX bs=8M"

Or, if you are running an Ubuntu-based distribution

sudo dd if=/Users/me/Downloads/Fedora-17-x86_64-DVD.iso of=/dev/sdX bs=8M

Note that the process will take some time and you will not see any information while it is running.

Command line method: Using the livecd-iso-to-disk tool (Fedora only)

The livecd-iso-to-disk is the most capable, non-destructive, and often most reliable method of writing a Fedora ISO image to a USB stick, but it can be used reliably only from within Fedora. It does not work in Windows and is not supported (and will usually fail) in non-Fedora distributions. Please use the liveusb-creator tool, dd (or an equivalent tool), or a third-party tool such as UNetbootin on other operating systems. It is also not a good idea to try and write a new Fedora release using the version of livecd-iso-to-disk in a much older Fedora release: It is best to only use a release a maximum of two versions older than the release you are trying to write.

Make sure the livecd-tools RPM is installed with the command

rpm -q livecd-tools.

You will see the name of the RPM and a version number if it is installed, or no output if it is not installed.

If livecd-tools is not installed, install it using this command, or PackageKit:

su -c 'yum install livecd-tools'

Detailed usage information is available in the first pages of the livecd-iso-to-disk script, which you can also see by running this command:

su -c 'livecd-iso-to-disk --help'

Basic examples follow.

To make an existing USB stick bootable as a Fedora image—without deleting any of the data on it—make sure that the USB drive is not mounted before executing the following, and give the root password when prompted:

su -c "livecd-iso-to-disk Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"

See Data persistence below for how to create Live USB devices with more than temporary storage of user files and settings.

In case it is not possible to boot from a disk created with the method shown above, before re-partitioning and re-formatting, often resetting the master boot record will enable booting:

su -c "livecd-iso-to-disk --reset-mbr Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"
Warning (medium size).png
CAUTION:
Using the --format option in the following command will erase all data on the USB drive! Please read the instructions below carefully.
If necessary, you can have livecd-iso-to-disk re-partition and re-format the target stick:
su -c "livecd-iso-to-disk --format --msdos --reset-mbr Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"

UEFI boot of USB sticks

Whether a Fedora image written to a USB stick will be bootable natively via UEFI is a somewhat complex question which depends on the Fedora release, the type of image (live or non-live), and the method used to write it. The --efi parameter to the livecd-iso-to-disk tool attempts to make a stick written with that tool natively UEFI bootable.

As of Fedora 17, all images written using the dd method should be UEFI-bootable, and all images written with livecd-iso-to-disk --format --reset-mbr --efi should also be UEFI-bootable. Use of --efi without --format and --reset-mbr can be considered a 'best effort', and may not produce a UEFI-bootable stick.

Creating a USB stick from a running live environment

If you are already running a live CD, DVD, or USB and want to convert that into a bootable USB stick, run the following command:

su -c "livecd-iso-to-disk /run/initramfs/livedev /dev/sdX"

(For versions before Fedora 17, use /dev/live instead of /run/initramfs/livedev.)

Data persistence

Data persistence means that your files and settings will remain even after you reboot your live system. You can perform updates just like a regular installation to your hard disk, except that kernel updates require manual intervention and overlay space may be insufficient. The primary use of this feature is booting a USB stick with your live image as well as the persistent changes. Note that you will need to have space on your target USB stick for the live image plus your overlay plus any other data you want on the stick.

Use the Graphical Method described above to do this easily. There is a graphical slider in the interface you can use to assign space on the target stick for persistent storage.

If using the livecd-iso-to-disk tool, add the --overlay-size-mb parameter to add a persistent data storage area to the target stick. For example:

su -c "livecd-iso-to-disk --overlay-size-mb 512 Fedora-16-x86_64-Live-Desktop.iso /dev/USBPARTITIONNAME"

where 512 is the desired size (in megabytes) of the overlay. The livecd-iso-to-disk tool will not accept an overlay size value greater than 4095 for VFAT, but for ext[234] filesystems it is only limited by the available space.

Note.png
Limited Lifetime of Persistent Overlay
One very important note about using the "primary" persistent overlay for system changes is that due to the way it's currently implemented (as a Device-mapper copy-on-write snapshot), every single change to it (writes AND deletes) subtracts from its free space, so it will eventually be "used up" and your USB stick will no longer boot (see this dm-devel discussion and this page for emergency recovery). Because of these limitations, it is advisable to use the system-level persistence sparingly, for configuration changes and important security updates only. Or, if you have sufficient disk space available, changes to the LiveOS root filesystem snapshot can be merged into a new copy of the root filesystem. See this page section for instructions.

See this section for mounting the root filesystem outside of a boot.

For normal, write-many storage, use the --home-size-mb option to create a home directory filesystem for personal files. Home.img can be re-used and loop mounted outside of the Live USB environment.

The persistent overlay status may be queried by issuing this command on the live system:

dmsetup status live-rw

The returned value may look like this:

live-rw: 0 8388608 snapshot 42296/204800 176

where the fraction after 'snapshot' for the logical volume is that of 512-byte sectors consumed in the overlay.

Windows instructions

Using liveusb-creator

Liveusb-creator.png

Fedora USB sticks can be created using the liveusb-creator utility. Note that this utility is only capable of writing Live images.

  • Download liveusb-creator from the site
  • Double click liveusb-creator

To use the tool, simply select a Fedora release to download from the drop-down box at top-right (or select an ISO you have already downloaded using the Browse button at top-left), select the USB stick to which you wish to write the image from the Target Device drop-down box, and hit the Create Live USB button.

Booting the image

Set USB as first boot device. Your BIOS may be different.
  • Power off the computer.
  • Plug the USB drive into a USB port.
  • Remove all other portable media, such as CD, DVD, or floppy disks.
  • Power on the computer.
  • If the computer is configured to automatically boot off of the USB drive, you will see a screen that says "Automatic boot in 10 seconds..." with a countdown.
  • If the computer starts to boot off the hard drive, you'll need to manually configure it to boot off the USB drive.
    • Wait for a safe point to reboot safely.
    • As the machine starts to reboot, watch carefully for instructions on which key to press (usually a function key or Escape) to enter the boot device selection menu, or "BIOS setup". Press and hold that key. If you miss the window of opportunity (often only a few seconds) then reboot and try again.
    • Use the BIOS setup menu to put your USB drive first in the boot sequence. It might be listed as a hard drive rather than a removable drive. Each hardware manufacturer has a slightly different method for doing so. Use caution! Your computer could become unbootable or lose functionality if you change any other settings. Though these settings can be reverted, you'll need to remember what you changed in order to do so.
    • Save the changes, exit, and the computer should boot the Live USB drive.

Troubleshooting

liveusb-creator problems

Partition isn't marked bootable!

If you get the following message, you need to mark the partition bootable.

$ su -c "livecd-iso-to-disk Fedora-1-x86_64-Live-Desktop.iso /dev/sdX"
Partition isn't marked bootable!
You can mark the partition as bootable with 
    $ /sbin/parted /dev/sdX
    (parted) toggle N boot
    (parted) quit
Cleaning up to exit...

To mark the partition bootable, run parted, and use the 'toggle X boot' command. For example:

$ parted /dev/sdX
GNU Parted 1.8.6
Using /dev/sdX
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                            
Model: Imation Flash Drive (scsi)
Disk /dev/sdX: 1062MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  1062MB  1062MB  primary  fat16             

(parted) toggle 1 boot
(parted) print                                                    
Model: Imation Flash Drive (scsi)
Disk /dev/sdX: 1062MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  1062MB  1062MB  primary  fat16        boot 

(parted) quit                                                             
Information: Don't forget to update /etc/fstab, if necessary.             

Partitions need a filesystem label!

If you get the following message, you need to label the partition.

$ su -c "livecd-iso-to-disk Fedora-16-x86_64-Live-Desktop.iso /dev/sdX"
Need to have a filesystem label or UUID for your USB device
Label can be set with /sbin/dosfslabel
Cleaning up to exit...

To label the partition:

su -c "dosfslabel /dev/sdX LIVE"

Partition has different physical/logical endings!

If you get this message from fdisk, you may need to reformat the flash drive, as described earlier in this guide.

MBR appears to be blank!

If your test boot reports a corrupted boot sector, or you get the following message, you need to install or reset the master boot record (MBR).

$ su -c "livecd-iso-to-disk Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"
MBR appears to be blank.
You can add an MBR to this device with
Cleaning up to exit...

To install or reset MBR:

$ su -c "livecd-iso-to-disk --reset-mbr Fedora-17-x86_64-Live-Desktop.iso /dev/sdX"

Issues using other Linux distributions

Ubuntu and derivative Linux distributions have a usb-creator program similar to Live USB Creator. This does not work with Fedora ISO images, it silently rejects them. usb-creator requires the ISO to have a Debian layout, with a /.disk/info file and a casper directory. Do not attempt to use this utility to write a Fedora ISO image.

The livecd-iso-to-disk script is not meant to be run from a non-Fedora system. Even if it happens to run and write a stick apparently successfully from some other distribution, the stick may well fail to boot. Use of livecd-iso-to-disk on any distribution other than Fedora is unsupported and not expected to work: please use an alternative method, such as dd described above.

Testing Live Image on USB

You can test your Live Image on USB using QEMU as shown in the screenshot below.

Screenshot qemu gtk3.png

For example, you could type the following commands:

su -c 'umount /dev/sdX1'
qemu -hda /dev/sdX -m 1024 -vga std

Mounting a Live USB filesystem

You can use the liveimage-mount script in the Package-x-generic-16.pnglivecd-tools package to mount an attached Live USB device or other LiveOS image, such as an ISO or Live CD. This is convenient when you want to copy in or out some file from the LiveOS filesystem on a Live USB, or just examine the files in a Live.iso or Live CD.

Kernel updates

If you have sufficient overlay space to accommodate a kernel update on a Live USB installation, the kernel and initramfs will be installed to the /boot directory. To put these into service they must be moved to the /syslinux directory of the installation partition. This is accessible from the running Live USB filesystem at either the /mnt/live or /run/initramfs/live mount point. The new initramfs (such as initramfs-3.3.2-6.fc16.x86_64.img) and kernel (such as vmlinuz-3.3.2-6.fc16.x86_64) should be moved to replace the /mnt/live/syslinux/initrd0.img and /mnt/live/syslinux/vmlinuz0 files, respectively.

  • Note: Beginning with Fedora 17 and updated Fedora 16, dracut no longer includes the dmsquash-live module by default. So one should include it in /etc/dracut.conf with, for example,
    # echo 'add_dracutmodules+=" dmsquash-live "' >> /etc/dracut.conf

The following commands will move the new kernel and initramfs files and create symbolic links to them, in case one later wants to perform a full install of the image to a hard disk.

bootpath=run/initramfs/live/syslinux
# bootpath=mnt/live/syslinux
new=3.3.2-6.fc16.x86_64

cd /
mv -f boot/vmlinuz-$new ${bootpath}/vmlinuz0
mv -f boot/initramfs-${new}.img ${bootpath}/initrd0.img

ln -fs -T ../${bootpath}/vmlinuz0 boot/vmlinuz-$new
ln -fs -T ../${bootpath}/initrd0.img boot/initramfs-${new}.img

See also

Red Hat Magazine | I am Fedora, and so can you!

References