Difference between revisions of "USB flash installation media"

From ArchWiki
Jump to navigation Jump to search
(→‎BIOS and UEFI bootable USB: changed link from the core utils page to the dd man page as coreutils is under consideration for deletion.)
(→‎In macOS: Changing M to m as the former results in dd: bs: illegal numeri value in Catalina)
 
(49 intermediate revisions by 22 users not shown)
Line 1: Line 1:
[[Category:Getting and installing Arch]]
+
[[Category:Installation process]]
 
[[ar:USB flash installation media]]
 
[[ar:USB flash installation media]]
 
[[bg:USB flash installation media]]
 
[[bg:USB flash installation media]]
Line 8: Line 8:
 
[[ja:USB インストールメディア]]
 
[[ja:USB インストールメディア]]
 
[[pt:USB flash installation media]]
 
[[pt:USB flash installation media]]
[[ro:Instalare prin USB]]
 
 
[[ru:USB flash installation media]]
 
[[ru:USB flash installation media]]
 
[[zh-hans:USB flash installation media]]
 
[[zh-hans:USB flash installation media]]
Line 24: Line 23:
 
== BIOS and UEFI bootable USB ==
 
== BIOS and UEFI bootable USB ==
  
=== Using dd ===
+
=== Using automatic tools ===
 +
 
 +
==== In GNU/Linux ====
 +
 
 +
===== Using dd =====
 +
 
 
{{Note|This method is recommended due to its simplicity. If it does not work, switch to the alternative method [[#Using manual formatting]] below.}}
 
{{Note|This method is recommended due to its simplicity. If it does not work, switch to the alternative method [[#Using manual formatting]] below.}}
  
{{Warning|This will irrevocably destroy all data on {{ic|/dev/'''sdx'''}}. To restore the USB drive as an empty, usable storage device after using the Arch ISO image, the iso9660 filesystem signature needs to be removed by running {{ic|wipefs --all /dev/'''sdx'''}} as root, before [[repartition]]ing and [[reformat]]ing the USB drive.}}
+
{{Warning|This will irrevocably destroy all data on {{ic|/dev/'''sdx'''}}. To restore the USB drive as an empty, usable storage device after using the Arch ISO image, the ISO 9660 filesystem signature needs to be removed by running {{ic|wipefs --all /dev/'''sdx'''}} as root, before [[repartition]]ing and [[reformat]]ing the USB drive.}}
 
 
==== In GNU/Linux ====
 
  
 
{{Tip|Find out the name of your USB drive with {{ic|lsblk}}. Make sure that it is '''not''' mounted.}}
 
{{Tip|Find out the name of your USB drive with {{ic|lsblk}}. Make sure that it is '''not''' mounted.}}
Line 35: Line 37:
 
Run the following command, replacing {{ic|/dev/'''sdx'''}} with your drive, e.g. {{ic|/dev/sdb}}. (Do '''not''' append a partition number, so do '''not''' use something like {{ic|/dev/sdb'''1'''}})
 
Run the following command, replacing {{ic|/dev/'''sdx'''}} with your drive, e.g. {{ic|/dev/sdb}}. (Do '''not''' append a partition number, so do '''not''' use something like {{ic|/dev/sdb'''1'''}})
  
  # dd bs=4M if=/path/to/archlinux.iso of=/dev/'''sdx''' status=progress oflag=sync
+
  # dd bs=4M if=path/to/archlinux.iso of=/dev/'''sdx''' status=progress oflag=sync
 +
 
 +
See {{man|1|dd}} for more information about [[dd]]. See {{man|1|dd|DESCRIPTION}} for more information about {{ic|1=oflag=sync}}.
 +
 
 +
{{Tip|If the UEFI version of the USB's Arch ISO hangs or is unable to load, try repeating the [[dd]] media creation process on the same USB drive one or more times.}}
 +
 
 +
===== Using etcher =====
 +
 
 +
[https://etcher.io/ Etcher] is a OS image flasher built with node.js and Electron, capable of flashing an SDCard or USB drive. It protects you from accidentally writing to your hard-drives and ensures every byte of data was written correctly. There are 6 related packages in the AUR.
  
See {{man|1|dd}} for more information about {{ic|dd}}. See {{man|1|dd|DESCRIPTION}} for more information about {{ic|<nowiki>oflag=sync</nowiki>}}.
+
===== Using Kindd =====
 +
 
 +
[https://github.com/LinArcX/Kindd Kindd] is a Qt based graphical frontend for dd. It is available as {{AUR|kindd}}.
  
 
==== In Windows ====
 
==== In Windows ====
  
===== Using Rufus =====  
+
===== Using Rufus =====
[https://rufus.akeo.ie/ Rufus] is a multi-purpose USB iso writer. Simply select the Arch Linux ISO, the USB drive you want to create the bootable Arch Linux onto and click start.
 
  
Since Rufus does not care if the drive is properly formatted or not and provides a GUI it may be the easiest and most robust tool to use.
+
[https://rufus.akeo.ie/ Rufus] is a multi-purpose USB ISO writer. It provides a graphical user interface and does not care if the drive is properly formatted or not.
  
{{Note|Be sure to select '''DD image''' mode from the dropdown menu or the image will be transferred incorrectly.}}
+
Simply select the Arch Linux ISO, the USB drive you want to create the bootable Arch Linux onto and click ''START''.
 +
 
 +
{{Note|If the USB drive does not boot properly using the default ISO Image mode, '''DD Image mode''' should be used instead.
 +
* For Rufus version ≥ 3.0 select ''GPT'' from the ''Partition scheme'' drop-down menu. After clicking ''START'' you will get the mode selection dialog, select ''DD Image mode''.
 +
* For Rufus version < 3.0 select ''DD Image'' mode from the drop-down menu on the bottom.
 +
}}
 +
 
 +
{{Tip|To add [https://github.com/pbatard/rufus/issues/691 an additional partition for persistent storage] use the slider to choose the persistent partition's size. When using the persistent partition feature, make sure to select ''MBR'' in the ''Partition scheme'' drop-down menu and ''BIOS or UEFI'' in ''Target System'', otherwise the drive will not be usable for both BIOS and UEFI booting.}}
  
 
===== Using USBwriter =====
 
===== Using USBwriter =====
  
This method does not require any workaround and is as straightforward as {{ic|dd}} under Linux. Just download the Arch Linux ISO, and with local administrator rights use the [http://sourceforge.net/p/usbwriter/wiki/Documentation/ USBwriter] utility to write to your USB flash memory.
+
This method does not require any workaround and is as straightforward as {{ic|dd}} under Linux. Just download the Arch Linux ISO, and with local administrator rights use the [https://sourceforge.net/p/usbwriter/wiki/Documentation/ USBwriter] utility to write to your USB flash memory.
  
 
===== Using win32diskimager =====
 
===== Using win32diskimager =====
Line 58: Line 76:
 
===== Using Cygwin =====
 
===== Using Cygwin =====
  
Make sure your [http://www.cygwin.com/ Cygwin] installation contains the {{ic|dd}} package.
+
Make sure your [https://www.cygwin.com/ Cygwin] installation contains the {{ic|dd}} package.
  
 
{{Tip|If you do not want to install Cygwin, you can download {{ic|dd}} for Windows from [http://www.chrysocome.net/dd here]. See the next section for more information.}}
 
{{Tip|If you do not want to install Cygwin, you can download {{ic|dd}} for Windows from [http://www.chrysocome.net/dd here]. See the next section for more information.}}
Line 92: Line 110:
 
If your Arch Linux ISO is elsewhere you may need to state the full path, for convenience you may wish to put the Arch Linux ISO into the same folder as the dd executable. The basic format of the command will look like this.
 
If your Arch Linux ISO is elsewhere you may need to state the full path, for convenience you may wish to put the Arch Linux ISO into the same folder as the dd executable. The basic format of the command will look like this.
  
  # dd if=''archlinux-2017-XX-YY-x86_64.iso'' od=\\.\''x'': bs=4M
+
  # dd if=''archlinux-''version''-x86_64.iso'' od=\\.\''x'': bs=4M
  
 
{{Note|The Windows drive letters are linked to a partition. To allow selecting the entire disk, ''dd for Windows'' provides the {{ic|od}} parameter, which is used in the commands above. Note however that this parameter is specific to ''dd for Windows'' and cannot be found in other implementations of ''dd''.}}
 
{{Note|The Windows drive letters are linked to a partition. To allow selecting the entire disk, ''dd for Windows'' provides the {{ic|od}} parameter, which is used in the commands above. Note however that this parameter is specific to ''dd for Windows'' and cannot be found in other implementations of ''dd''.}}
Line 100: Line 118:
 
Simply replace the various null spots (indicated by an "x") with the correct date and correct drive letter. Here is a complete example.
 
Simply replace the various null spots (indicated by an "x") with the correct date and correct drive letter. Here is a complete example.
  
  # dd if=ISOs\archlinux-2017.04.01-x86_64.iso od=\\.\d: bs=4M
+
  # dd if=ISOs\archlinux-''version''-x86_64.iso od=\\.\d: bs=4M
  
{{Accuracy|The following note may be invalid, the [http://www.chrysocome.net/dd upstream documentation] does not mention anything related to ''PhysicalDrive''.}}
+
{{Accuracy|The following note may be invalid, the [http://www.chrysocome.net/dd upstream documentation] does not mention anything related to ''PhysicalDrive''.|section=dd for windows}}
  
 
{{Note|Alternatively, replace the drive letter with {{ic|\\.\PhysicalDrive''X''}}, where {{ic|''X''}} is the physical drive number (starts from 0). Example:
 
{{Note|Alternatively, replace the drive letter with {{ic|\\.\PhysicalDrive''X''}}, where {{ic|''X''}} is the physical drive number (starts from 0). Example:
{{bc|1=# dd if=ISOs\archlinux-2017.04.01-x86_64.iso of=\\.\PhysicalDrive1 bs=4M}}
+
{{bc|1=# dd if=ISOs\archlinux-''version''-x86_64.iso of=\\.\PhysicalDrive1 bs=4M}}
 
You can find out the physical drive number by typing {{ic|wmic diskdrive list brief}} at the command prompt or with {{ic|dd --list}}
 
You can find out the physical drive number by typing {{ic|wmic diskdrive list brief}} at the command prompt or with {{ic|dd --list}}
 
Any Explorer window must be closed or dd will report an error.}}
 
Any Explorer window must be closed or dd will report an error.}}
Line 122: Line 140:
  
 
Now copy the ISO image file to the device. The {{ic|dd}} command is similar to its Linux counterpart, but notice the 'r' before 'disk' for raw mode which makes the transfer much faster:
 
Now copy the ISO image file to the device. The {{ic|dd}} command is similar to its Linux counterpart, but notice the 'r' before 'disk' for raw mode which makes the transfer much faster:
 +
 +
{{Accuracy|1=It does not seem clear whether there should be {{ic|1=bs=1M}} or {{ic|1=bs=1m}}. [https://wiki.archlinux.org/index.php?title=USB_flash_installation_media&diff=544886&oldid=543750][https://wiki.archlinux.org/index.php?title=USB_flash_installation_media&diff=next&oldid=578856]|section=Repeated editions, back and forth}}
  
 
  # dd if=path/to/arch.iso of=/dev/'''r'''diskX bs=1m
 
  # dd if=path/to/arch.iso of=/dev/'''r'''diskX bs=1m
  
Note {{ic|diskX}} here should not include the {{ic|s1}} suffix, or else the USB device will only be bootable in UEFI mode and not legacy. After completion, macOS may complain that "The disk you inserted was not readable by this computer". Select 'Ignore'. The USB device will be bootable.
+
This command will run silently. To view progress, send SIGINFO by pressing {{ic|Ctrl+t}}. Note {{ic|diskX}} here should not include the {{ic|s1}} suffix, or else the USB device will only be bootable in UEFI mode and not legacy. After completion, macOS may complain that "The disk you inserted was not readable by this computer". Select 'Ignore'. The USB device will be bootable.
 +
 
 +
==== In Android ====
 +
 
 +
===== EtchDroid =====
 +
 
 +
[https://etchdroid.depau.eu/ EtchDroid] is a OS image flasher for Android. It works without root permissions on Android 5 to Android 8. According to bug reports it doesn't always work on Android 9 and Android 4.4.
 +
 
 +
To create an Arch Linux installer, download the ISO image file on your Android device. Plug the USB drive to your device, using a USB-OTG adapter if needed. Open EtchDroid, select "Flash raw image", select your Arch ISO, then select your USB drive. Grant the USB API permission and confirm.
 +
 
 +
Keep your phone on a table while it's writing the image: a lot of USB-OTG adapters are a bit wobbly and you might unplug it by mistake.
  
 
=== Using manual formatting===
 
=== Using manual formatting===
Line 133: Line 163:
 
This method is more complicated than writing the image directly with {{ic|dd}}, but it does keep the flash drive usable for data storage (that is, the ISO is installed in a specific partition within the already [[Partitioning|partitioned device]] without altering other partitions).
 
This method is more complicated than writing the image directly with {{ic|dd}}, but it does keep the flash drive usable for data storage (that is, the ISO is installed in a specific partition within the already [[Partitioning|partitioned device]] without altering other partitions).
  
{{Note|Here, we will denote the targeted partition as {{ic|/dev/sd'''Xn'''}}. In any of the following commands, adjust '''X''' and '''n''' according to your system.}}
+
{{Note|Here, we will denote the targeted partition as {{ic|/dev/sd'''Xn'''}}. In any of the following commands, adjust '''X''' and '''n''' according to your system.}}
  
* Make sure that the {{Pkg|syslinux}} package is installed on the system.  
+
* If not done yet, create a [[partition table]] on {{ic|/dev/sd'''X'''}}.
 +
* If not done yet, create a partition on the device. The partition {{ic|/dev/sd'''Xn'''}} must be formatted to [[FAT32]].
 +
* Mount the ISO image, mount the FAT32 filesystem located in the USB flash device, and copy the contents of the ISO image to it. Then unmount the ISO image, but keep the FAT32 partition mounted (this may be used in subsequent steps). For example:
  
* If not done yet, create the partition table and/or partition on the device before continuing. The partition {{ic|/dev/sd'''Xn'''}} must be formatted to [[FAT32]].
 
 
* Mount the ISO image, mount the FAT32 filesystem located in the USB flash device, and copy the contents of the ISO image to it. Then unmount the ISO image, but keep the FAT32 partition mounted (this will be used in subsequent steps). Eg:
 
 
  # mkdir -p /mnt/{iso,usb}
 
  # mkdir -p /mnt/{iso,usb}
  # mount -o loop archlinux-2017.04.01-x86_64.iso /mnt/iso
+
  # mount -o loop archlinux-''version''-x86_64.iso /mnt/iso
 
  # mount /dev/sd'''Xn''' /mnt/usb
 
  # mount /dev/sd'''Xn''' /mnt/usb
 
  # cp -a /mnt/iso/* /mnt/usb
 
  # cp -a /mnt/iso/* /mnt/usb
Line 147: Line 176:
 
  # umount /mnt/iso
 
  # umount /mnt/iso
  
To boot either a label or an [[UUID]] to select the partition to boot from is required. By default the label {{ic|ARCH_2017'''XX'''}} (with the appropriate release month) is used. Thus, the partition’s label has to be set accordingly, for example using ''gparted''. Alternatively, you can change this behaviour by altering the lines ending by {{ic|1=archisolabel=ARCH_2017'''XX'''}} in the file {{ic|/mnt/usb/arch/boot/syslinux/archiso_sys.cfg}} (for BIOS boot), and in {{ic|/mnt/usb/loader/entries/archiso-x86_64.conf}} (for UEFI boot). To use an UUID instead, replace those portions of lines with {{ic|1=archiso''device''=/dev/disk/by-uuid/'''YOUR-UUID'''}}. The UUID can be retrieved with {{ic|1=blkid -o value -s UUID /dev/sd'''Xn'''}}.
+
To boot either a label or an [[UUID]] to select the partition to boot from is required. By default the label {{ic|ARCH_''YYYYMM''}} (with the appropriate release year and month) is used. Thus, the [[Persistent block device naming#by-label|file system’s label]] has to be set accordingly, for example using ''gparted''. Alternatively, you can change this behaviour by altering the lines ending by {{ic|1=archisolabel=ARCH_''YYYYMM''}} in the file {{ic|/mnt/usb/arch/boot/syslinux/archiso_sys.cfg}} (for BIOS boot), and in {{ic|/mnt/usb/loader/entries/archiso-x86_64.conf}} (for UEFI boot). To use an UUID instead, replace those portions of lines with {{ic|1=archiso''device''=/dev/disk/by-uuid/'''YOUR-UUID'''}}. The UUID can be retrieved with {{ic|1=blkid -o value -s UUID /dev/sd'''Xn'''}}.
  
{{Warning|Mismatching labels or wrong UUID prevents booting from the created medium.}}
+
{{Warning|Mismatching labels or wrong UUID prevents booting from the created medium.}}
  
Syslinux is already preinstalled in ''/mnt/usb/arch/boot/syslinux''. Install it completely to that folder by following [[Syslinux#Manual install]]. Instructions are reproduced here for convenience.
+
Syslinux files for BIOS systems are already copied to {{ic|/mnt/usb/arch/boot/syslinux}}. Install the {{Pkg|syslinux}} package and follow [[Syslinux#Manual install]] instructions to make the partition bootable.
* Overwrite the existing Syslinux modules ({{ic|*.c32}} files) present in the USB (from the ISO) with the ones from the syslinux package (found in ''/usr/lib/syslinux/bios''). This is necessary to avoid boot failure because of a possible version mismatch.
 
# cp /usr/lib/syslinux/bios/*.c32 /mnt/usb/arch/boot/syslinux
 
* Run:
 
# extlinux --install /mnt/usb/arch/boot/syslinux
 
* Unmount the partition ({{ic|umount /mnt/usb}}).
 
 
 
* Mark the partition as active (or “bootable”).
 
  
 
==== In Windows ====
 
==== In Windows ====
Line 164: Line 186:
 
{{Note|
 
{{Note|
 
* For manual formatting, do not use any '''Bootable USB Creator utility''' for creating the UEFI bootable USB. For manual formatting, do not use ''dd for Windows'' to dd the ISO to the USB drive either.
 
* For manual formatting, do not use any '''Bootable USB Creator utility''' for creating the UEFI bootable USB. For manual formatting, do not use ''dd for Windows'' to dd the ISO to the USB drive either.
 
 
* In the below commands, '''X:''' is assumed to be the USB flash drive in Windows.
 
* In the below commands, '''X:''' is assumed to be the USB flash drive in Windows.
 
 
* Windows uses backward slash {{ic|\}} as path-separator, so the same is used in the below commands.
 
* Windows uses backward slash {{ic|\}} as path-separator, so the same is used in the below commands.
 
 
* All commands should be run in Windows command prompt '''as administrator'''.
 
* All commands should be run in Windows command prompt '''as administrator'''.
 
 
* {{ic|>}} denotes the Windows command prompt.
 
* {{ic|>}} denotes the Windows command prompt.
 
}}
 
}}
  
* Partition and format the USB drive using [http://rufus.akeo.ie/ Rufus USB partitioner]. Select partition scheme option as '''MBR for BIOS and UEFI''' and File system as '''FAT32'''. Uncheck "Create a bootable disk using ISO image" and "Create extended label and icon files" options.
+
* Partition and format the USB drive using [https://rufus.akeo.ie/ Rufus USB partitioner]. Select partition scheme option as '''MBR for BIOS and UEFI''' and File system as '''FAT32'''. Uncheck "Create a bootable disk using ISO image" and "Create extended label and icon files" options.
 
 
 
* Change the '''Volume Label''' of the USB flash drive {{ic|X:}} to match the LABEL mentioned in the {{ic|1=archisolabel=}} part in {{ic|<ISO>\loader\entries\archiso-x86_64.conf}}. This step is required for Official ISO ([[Archiso]]). This step can be also performed using Rufus, during the prior "partition and format" step.
 
* Change the '''Volume Label''' of the USB flash drive {{ic|X:}} to match the LABEL mentioned in the {{ic|1=archisolabel=}} part in {{ic|<ISO>\loader\entries\archiso-x86_64.conf}}. This step is required for Official ISO ([[Archiso]]). This step can be also performed using Rufus, during the prior "partition and format" step.
 
+
* Extract the ISO (similar to extracting ZIP archive) to the USB flash drive using [https://www.7-zip.org/ 7-Zip].  
* Extract the ISO (similar to extracting ZIP archive) to the USB flash drive (using [http://7-zip.org/ 7-Zip].  
 
 
 
 
* Download official Syslinux 6.xx binaries (zip file) from https://www.kernel.org/pub/linux/utils/boot/syslinux/  and extract it. The version of Syslinux should be the same version used in the ISO image.
 
* Download official Syslinux 6.xx binaries (zip file) from https://www.kernel.org/pub/linux/utils/boot/syslinux/  and extract it. The version of Syslinux should be the same version used in the ISO image.
  
Line 195: Line 210:
 
{{Note|
 
{{Note|
 
* The above step installs Syslinux's {{ic|ldlinux.sys}} to the VBR of the USB partition, sets the partition as "active/boot" in the MBR partition table and writes the MBR boot code to the 1st 440-byte boot code region of the USB.
 
* The above step installs Syslinux's {{ic|ldlinux.sys}} to the VBR of the USB partition, sets the partition as "active/boot" in the MBR partition table and writes the MBR boot code to the 1st 440-byte boot code region of the USB.
 
 
* The {{ic|-d}} switch expects a path with forward slash path-separator like in *unix systems.
 
* The {{ic|-d}} switch expects a path with forward slash path-separator like in *unix systems.
 
}}
 
}}
Line 204: Line 218:
  
 
==== Using a multiboot USB drive ====
 
==== Using a multiboot USB drive ====
 +
 
This allows booting multiple ISOs from a single USB device, including the archiso. Updating an existing USB drive to a more recent ISO is simpler than for most other methods. See [[Multiboot USB drive]].
 
This allows booting multiple ISOs from a single USB device, including the archiso. Updating an existing USB drive to a more recent ISO is simpler than for most other methods. See [[Multiboot USB drive]].
  
 
==== Using GNOME Disk Utility ====
 
==== Using GNOME Disk Utility ====
Linux distributions running GNOME can easily make a live CD through {{Pkg|nautilus}} and {{Pkg|gnome-disk-utility}}.  Simply right-click on the .iso file, and select "Open With Disk Image Writer." When GNOME Disk Utility opens, specify the flash drive from the "Destination" drop-down menu and click "Start Restoring."
+
 
 +
Linux distributions running GNOME can easily make a live CD through {{Pkg|nautilus}} and {{Pkg|gnome-disk-utility}}.  Simply right-click on the ''.iso'' file, and select ''Open With Disk Image Writer''.  When GNOME Disk Utility opens, specify the flash drive from the ''Destination'' drop-down menu and click ''Start Restoring''.
  
 
==== Making a USB-ZIP drive ====
 
==== Making a USB-ZIP drive ====
 +
 
For some old BIOS systems, only booting from USB-ZIP drives is supported. This method allows you to still boot from a USB-HDD drive.
 
For some old BIOS systems, only booting from USB-ZIP drives is supported. This method allows you to still boot from a USB-HDD drive.
 +
 
{{Warning|This will destroy all information on your USB flash drive!}}
 
{{Warning|This will destroy all information on your USB flash drive!}}
  
Line 216: Line 234:
 
* Find your usb drive with {{ic|lsblk}}.
 
* Find your usb drive with {{ic|lsblk}}.
 
* Type {{ic|mkdiskimage -4 /dev/sd'''x''' 0 64 32}} (replace x with the letter of your drive). This will take a while.
 
* Type {{ic|mkdiskimage -4 /dev/sd'''x''' 0 64 32}} (replace x with the letter of your drive). This will take a while.
 +
 
From here continue with the manual formatting method. The partition will be {{ic|/dev/sd'''x'''4}} due to the way ZIP drives work.
 
From here continue with the manual formatting method. The partition will be {{ic|/dev/sd'''x'''4}} due to the way ZIP drives work.
  
Line 221: Line 240:
  
 
==== Using UNetbootin ====
 
==== Using UNetbootin ====
UNetbootin can be used on any Linux distribution or Windows to copy your iso to a USB device. However, Unetbootin overwrites syslinux.cfg, so it creates a USB device that does not boot properly. For this reason, '''Unetbootin is not recommended''' -- please use {{ic|dd}} or one of the other methods discussed in this topic.
+
 
 +
UNetbootin can be used on any Linux distribution or Windows to copy your iso to a USB device. However, Unetbootin overwrites {{ic|syslinux.cfg}}, so it creates a USB device that does not boot properly. For this reason, '''Unetbootin is not recommended''' -- please use {{ic|dd}} or one of the other methods discussed in this topic.
 +
 
 
{{Warning|UNetbootin writes over the default {{ic|syslinux.cfg}}; this must be restored before the USB device will boot properly.}}
 
{{Warning|UNetbootin writes over the default {{ic|syslinux.cfg}}; this must be restored before the USB device will boot properly.}}
  
Line 270: Line 291:
 
{{Merge|Multiboot USB drive#Using Syslinux and memdisk|This is the same method, only Syslinux is installed from Windows. Considering that [[multiboot USB drive]] can be used to boot an installation media and it is already linked from the Related articles box at the top, maybe this section should be merged there?}}
 
{{Merge|Multiboot USB drive#Using Syslinux and memdisk|This is the same method, only Syslinux is installed from Windows. Considering that [[multiboot USB drive]] can be used to boot an installation media and it is already linked from the Related articles box at the top, maybe this section should be merged there?}}
  
This method uses [[Syslinux]] and a [[Ramdisk]] ([http://www.syslinux.org/wiki/index.php/MEMDISK MEMDISK]) to load the entire Arch Linux ISO image into RAM. Since this will be running entirely from system memory, you will need to make sure the system you will be installing this on has an adequate amount. A minimum amount of RAM between 500 MB and 1 GB should suffice for a MEMDISK based, Arch Linux install.
+
This method uses [[Syslinux]] and a [[Ramdisk]] ([https://wiki.syslinux.org/wiki/index.php/MEMDISK MEMDISK]) to load the entire Arch Linux ISO image into RAM. Since this will be running entirely from system memory, you will need to make sure the system you will be installing this on has an adequate amount. A minimum amount of RAM between 500 MB and 1 GB should suffice for a MEMDISK based, Arch Linux install.
  
 
For more information on Arch Linux system requirements as well as those for MEMDISK see the [[Installation guide]] and [http://www.etherboot.org/wiki/bootingmemdisk#preliminaries here]. For reference, here is the [https://bbs.archlinux.org/viewtopic.php?id=135266 preceding forum thread].
 
For more information on Arch Linux system requirements as well as those for MEMDISK see the [[Installation guide]] and [http://www.etherboot.org/wiki/bootingmemdisk#preliminaries here]. For reference, here is the [https://bbs.archlinux.org/viewtopic.php?id=135266 preceding forum thread].
Line 279: Line 300:
  
 
Begin by formatting the USB flash drive as '''FAT32'''. Then create the following folders on the newly formatted drive.
 
Begin by formatting the USB flash drive as '''FAT32'''. Then create the following folders on the newly formatted drive.
 +
 
* {{ic|Boot}}
 
* {{ic|Boot}}
 
** {{ic|Boot/ISOs}}
 
** {{ic|Boot/ISOs}}
Line 285: Line 307:
 
===== Copy the needed files to the USB flash drive =====
 
===== Copy the needed files to the USB flash drive =====
  
Next copy the ISO that you would like to boot to the {{ic|Boot/ISOs}} folder. After that, extract from the following files from the latest release of {{pkg|syslinux}} from [http://www.kernel.org/pub/linux/utils/boot/syslinux/ here] and copy them into the following folders.
+
Next copy the ISO that you would like to boot to the {{ic|Boot/ISOs}} folder. After that, extract from the following files from the latest release of {{pkg|syslinux}} from [https://www.kernel.org/pub/linux/utils/boot/syslinux/ here] and copy them into the following folders.
 
* {{ic|./win32/syslinux.exe}} to the Desktop or Downloads folder on your system.
 
* {{ic|./win32/syslinux.exe}} to the Desktop or Downloads folder on your system.
 
* {{ic|./memdisk/memdisk}} to the {{ic|Settings}} folder on your USB flash drive.
 
* {{ic|./memdisk/memdisk}} to the {{ic|Settings}} folder on your USB flash drive.
Line 292: Line 314:
  
 
After copying the needed files, navigate to the USB flash drive, /boot/Settings and create a {{ic|syslinux.cfg}} file.
 
After copying the needed files, navigate to the USB flash drive, /boot/Settings and create a {{ic|syslinux.cfg}} file.
{{Warning|On the {{ic|INITRD}} line, be sure to use the name of the ISO file that you copied to your {{ic|ISOs}} folder!}}
+
 
 +
{{Warning|On the {{ic|INITRD}} line, be sure to use the name of the ISO file that you copied to your {{ic|ISOs}} folder.}}
 +
 
 
{{hc|/Boot/Settings/syslinux.cfg|2=
 
{{hc|/Boot/Settings/syslinux.cfg|2=
 
DEFAULT arch_iso
 
DEFAULT arch_iso
Line 299: Line 323:
 
         MENU LABEL Arch Setup
 
         MENU LABEL Arch Setup
 
         LINUX memdisk
 
         LINUX memdisk
         INITRD /Boot/ISOs/archlinux-2017.04.01-x86_64.iso
+
         INITRD /Boot/ISOs/archlinux-''version''-x86_64.iso
         APPEND iso}}
+
         APPEND iso
 +
}}
 +
 
 
For more information on Syslinux see the [[Syslinux|Arch Wiki article]].
 
For more information on Syslinux see the [[Syslinux|Arch Wiki article]].
  
Line 306: Line 332:
  
 
Finally, create a {{ic|*.bat}} file where {{ic|syslinux.exe}} is located and run it ("Run as administrator" if you are on Vista or Windows 7):
 
Finally, create a {{ic|*.bat}} file where {{ic|syslinux.exe}} is located and run it ("Run as administrator" if you are on Vista or Windows 7):
 +
 
{{hc|C:\Documents and Settings\username\Desktop\install.bat|
 
{{hc|C:\Documents and Settings\username\Desktop\install.bat|
 
@echo off
 
@echo off
syslinux.exe -m -a -d /Boot/Settings X:}}
+
syslinux.exe -m -a -d /Boot/Settings X:
 +
}}
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
* If you get the "device did not show up after 30 seconds" error due to the {{ic|/dev/disk/by-label/ARCH_XXXXYY}} not mounting, try renaming your USB media to {{ic|ARCH_XXXXYY}} (e.g. {{ic|ARCH_201501}}).
+
* If you get the "device did not show up after 30 seconds" error due to the {{ic|/dev/disk/by-label/ARCH_''YYYYMM''}} not mounting, try renaming your USB media to {{ic|ARCH_''YYYYMM''}} (e.g. {{ic|ARCH_201501}}).
 
 
 
* If you get errors, try using another USB device. There are case scenarios in which it solved all issues.
 
* If you get errors, try using another USB device. There are case scenarios in which it solved all issues.
  
Line 320: Line 347:
 
* [https://wiki.gentoo.org/wiki/LiveUSB/HOWTO Gentoo wiki - LiveUSB/HOWTO]
 
* [https://wiki.gentoo.org/wiki/LiveUSB/HOWTO Gentoo wiki - LiveUSB/HOWTO]
 
* [https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB Fedora wiki - How to create and use Live USB]
 
* [https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB Fedora wiki - How to create and use Live USB]
* [http://en.opensuse.org/SDB:Live_USB_stick openSUSE wiki - SDB:Live USB stick]
+
* [https://en.opensuse.org/SDB:Live_USB_stick openSUSE wiki - SDB:Live USB stick]

Latest revision as of 15:24, 31 October 2019

This page discusses various multi-platform methods on how to create an Arch Linux Installer USB drive (also referred to as "flash drive", "USB stick", "USB key", etc) for booting in BIOS and UEFI systems. The result will be a LiveUSB (LiveCD-like) system that can be used for installing Arch Linux, system maintenance or for recovery purposes, and that, because of the nature of SquashFS, will discard all changes once the computer shuts down.

If you would like to run a full install of Arch Linux from a USB drive (i.e. with persistent settings), see Installing Arch Linux on a USB key. If you would like to use your bootable Arch Linux USB stick as a rescue USB, see Change root.

BIOS and UEFI bootable USB

Using automatic tools

In GNU/Linux

Using dd
Note: This method is recommended due to its simplicity. If it does not work, switch to the alternative method #Using manual formatting below.
Warning: This will irrevocably destroy all data on /dev/sdx. To restore the USB drive as an empty, usable storage device after using the Arch ISO image, the ISO 9660 filesystem signature needs to be removed by running wipefs --all /dev/sdx as root, before repartitioning and reformating the USB drive.
Tip: Find out the name of your USB drive with lsblk. Make sure that it is not mounted.

Run the following command, replacing /dev/sdx with your drive, e.g. /dev/sdb. (Do not append a partition number, so do not use something like /dev/sdb1)

# dd bs=4M if=path/to/archlinux.iso of=/dev/sdx status=progress oflag=sync

See dd(1) for more information about dd. See dd(1) for more information about oflag=sync.

Tip: If the UEFI version of the USB's Arch ISO hangs or is unable to load, try repeating the dd media creation process on the same USB drive one or more times.
Using etcher

Etcher is a OS image flasher built with node.js and Electron, capable of flashing an SDCard or USB drive. It protects you from accidentally writing to your hard-drives and ensures every byte of data was written correctly. There are 6 related packages in the AUR.

Using Kindd

Kindd is a Qt based graphical frontend for dd. It is available as kinddAUR.

In Windows

Using Rufus

Rufus is a multi-purpose USB ISO writer. It provides a graphical user interface and does not care if the drive is properly formatted or not.

Simply select the Arch Linux ISO, the USB drive you want to create the bootable Arch Linux onto and click START.

Note: If the USB drive does not boot properly using the default ISO Image mode, DD Image mode should be used instead.
  • For Rufus version ≥ 3.0 select GPT from the Partition scheme drop-down menu. After clicking START you will get the mode selection dialog, select DD Image mode.
  • For Rufus version < 3.0 select DD Image mode from the drop-down menu on the bottom.
Tip: To add an additional partition for persistent storage use the slider to choose the persistent partition's size. When using the persistent partition feature, make sure to select MBR in the Partition scheme drop-down menu and BIOS or UEFI in Target System, otherwise the drive will not be usable for both BIOS and UEFI booting.
Using USBwriter

This method does not require any workaround and is as straightforward as dd under Linux. Just download the Arch Linux ISO, and with local administrator rights use the USBwriter utility to write to your USB flash memory.

Using win32diskimager

win32diskimager is another graphical USB iso writing tool for Windows. Simply select your iso image and the target USB drive letter (you may have to format it first to assign it a drive letter), and click Write.

Using Cygwin

Make sure your Cygwin installation contains the dd package.

Tip: If you do not want to install Cygwin, you can download dd for Windows from here. See the next section for more information.

Place your image file in your home directory:

C:\cygwin\home\John\

Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:

dd if=image.iso of=\\.\x: bs=4M

where image.iso is the path to the iso image file within the cygwin directory and \\.\x: is your USB flash drive where x is the windows designated letter, e.g. \\.\d:.

On Cygwin 6.0, find out the correct partition with:

cat /proc/partitions

and write the ISO image with the information from the output. Example:

Warning: This will irrevocably delete all files on your USB flash drive, so make sure you do not have any important files on the flash drive before doing this.
dd if=image.iso of=/dev/sdb bs=4M
dd for Windows

A GPL licensed dd version for Windows is available at http://www.chrysocome.net/dd. The advantage of this over Cygwin is a smaller download. Use it as shown in instructions for Cygwin above.

To begin, download the latest version of dd for Windows. Once downloaded, extract the archive's contents into Downloads or elsewhere.

Now, launch your command prompt as an administrator. Next, change directory (cd) into the Downloads directory.

If your Arch Linux ISO is elsewhere you may need to state the full path, for convenience you may wish to put the Arch Linux ISO into the same folder as the dd executable. The basic format of the command will look like this.

# dd if=archlinux-version-x86_64.iso od=\\.\x: bs=4M
Note: The Windows drive letters are linked to a partition. To allow selecting the entire disk, dd for Windows provides the od parameter, which is used in the commands above. Note however that this parameter is specific to dd for Windows and cannot be found in other implementations of dd.
Warning: Because the od is used, all partitions on the selected disk will be destroyed. Be absolutely sure that you are directing dd to the correct drive before executing.

Simply replace the various null spots (indicated by an "x") with the correct date and correct drive letter. Here is a complete example.

# dd if=ISOs\archlinux-version-x86_64.iso od=\\.\d: bs=4M

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: The following note may be invalid, the upstream documentation does not mention anything related to PhysicalDrive. (Discuss in Talk:USB flash installation media#dd for windows)
Note: Alternatively, replace the drive letter with \\.\PhysicalDriveX, where X is the physical drive number (starts from 0). Example:
# dd if=ISOs\archlinux-version-x86_64.iso of=\\.\PhysicalDrive1 bs=4M

You can find out the physical drive number by typing wmic diskdrive list brief at the command prompt or with dd --list

Any Explorer window must be closed or dd will report an error.

In macOS

First, you need to identify the USB device. Open /Applications/Utilities/Terminal and list all storage devices with the command:

$ diskutil list

Your USB device will appear as something like /dev/disk2 (external, physical). Verify that this is the device you want to erase by checking its name and size and then use its identifier for the commands below instead of /dev/diskX.

A USB device is normally auto-mounted in macOS, and you have to unmount (not eject) it before block-writing to it with dd. In Terminal, do:

$ diskutil unmountDisk /dev/diskX

Now copy the ISO image file to the device. The dd command is similar to its Linux counterpart, but notice the 'r' before 'disk' for raw mode which makes the transfer much faster:

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: It does not seem clear whether there should be bs=1M or bs=1m. [1][2] (Discuss in Talk:USB flash installation media#Repeated editions, back and forth)
# dd if=path/to/arch.iso of=/dev/rdiskX bs=1m

This command will run silently. To view progress, send SIGINFO by pressing Ctrl+t. Note diskX here should not include the s1 suffix, or else the USB device will only be bootable in UEFI mode and not legacy. After completion, macOS may complain that "The disk you inserted was not readable by this computer". Select 'Ignore'. The USB device will be bootable.

In Android

EtchDroid

EtchDroid is a OS image flasher for Android. It works without root permissions on Android 5 to Android 8. According to bug reports it doesn't always work on Android 9 and Android 4.4.

To create an Arch Linux installer, download the ISO image file on your Android device. Plug the USB drive to your device, using a USB-OTG adapter if needed. Open EtchDroid, select "Flash raw image", select your Arch ISO, then select your USB drive. Grant the USB API permission and confirm.

Keep your phone on a table while it's writing the image: a lot of USB-OTG adapters are a bit wobbly and you might unplug it by mistake.

Using manual formatting

In GNU/Linux

This method is more complicated than writing the image directly with dd, but it does keep the flash drive usable for data storage (that is, the ISO is installed in a specific partition within the already partitioned device without altering other partitions).

Note: Here, we will denote the targeted partition as /dev/sdXn. In any of the following commands, adjust X and n according to your system.
  • If not done yet, create a partition table on /dev/sdX.
  • If not done yet, create a partition on the device. The partition /dev/sdXn must be formatted to FAT32.
  • Mount the ISO image, mount the FAT32 filesystem located in the USB flash device, and copy the contents of the ISO image to it. Then unmount the ISO image, but keep the FAT32 partition mounted (this may be used in subsequent steps). For example:
# mkdir -p /mnt/{iso,usb}
# mount -o loop archlinux-version-x86_64.iso /mnt/iso
# mount /dev/sdXn /mnt/usb
# cp -a /mnt/iso/* /mnt/usb
# sync
# umount /mnt/iso

To boot either a label or an UUID to select the partition to boot from is required. By default the label ARCH_YYYYMM (with the appropriate release year and month) is used. Thus, the file system’s label has to be set accordingly, for example using gparted. Alternatively, you can change this behaviour by altering the lines ending by archisolabel=ARCH_YYYYMM in the file /mnt/usb/arch/boot/syslinux/archiso_sys.cfg (for BIOS boot), and in /mnt/usb/loader/entries/archiso-x86_64.conf (for UEFI boot). To use an UUID instead, replace those portions of lines with archisodevice=/dev/disk/by-uuid/YOUR-UUID. The UUID can be retrieved with blkid -o value -s UUID /dev/sdXn.

Warning: Mismatching labels or wrong UUID prevents booting from the created medium.

Syslinux files for BIOS systems are already copied to /mnt/usb/arch/boot/syslinux. Install the syslinux package and follow Syslinux#Manual install instructions to make the partition bootable.

In Windows

Note:
  • For manual formatting, do not use any Bootable USB Creator utility for creating the UEFI bootable USB. For manual formatting, do not use dd for Windows to dd the ISO to the USB drive either.
  • In the below commands, X: is assumed to be the USB flash drive in Windows.
  • Windows uses backward slash \ as path-separator, so the same is used in the below commands.
  • All commands should be run in Windows command prompt as administrator.
  • > denotes the Windows command prompt.
  • Partition and format the USB drive using Rufus USB partitioner. Select partition scheme option as MBR for BIOS and UEFI and File system as FAT32. Uncheck "Create a bootable disk using ISO image" and "Create extended label and icon files" options.
  • Change the Volume Label of the USB flash drive X: to match the LABEL mentioned in the archisolabel= part in <ISO>\loader\entries\archiso-x86_64.conf. This step is required for Official ISO (Archiso). This step can be also performed using Rufus, during the prior "partition and format" step.
  • Extract the ISO (similar to extracting ZIP archive) to the USB flash drive using 7-Zip.
  • Download official Syslinux 6.xx binaries (zip file) from https://www.kernel.org/pub/linux/utils/boot/syslinux/ and extract it. The version of Syslinux should be the same version used in the ISO image.
  • Run the following command (in Windows cmd prompt, as admin):
> cd bios\
> for /r %Y in (*.c32) do copy "%Y" "X:\arch\boot\syslinux\" /y
> copy mbr\*.bin X:\arch\boot\syslinux\ /y
  • Install Syslinux to the USB by running (use win64\syslinux64.exe for x64 Windows):
> cd bios\
> win32\syslinux.exe -d /arch/boot/syslinux -i -a -m X:
Note:
  • The above step installs Syslinux's ldlinux.sys to the VBR of the USB partition, sets the partition as "active/boot" in the MBR partition table and writes the MBR boot code to the 1st 440-byte boot code region of the USB.
  • The -d switch expects a path with forward slash path-separator like in *unix systems.

Other methods for BIOS systems

In GNU/Linux

Using a multiboot USB drive

This allows booting multiple ISOs from a single USB device, including the archiso. Updating an existing USB drive to a more recent ISO is simpler than for most other methods. See Multiboot USB drive.

Using GNOME Disk Utility

Linux distributions running GNOME can easily make a live CD through nautilus and gnome-disk-utility. Simply right-click on the .iso file, and select Open With Disk Image Writer. When GNOME Disk Utility opens, specify the flash drive from the Destination drop-down menu and click Start Restoring.

Making a USB-ZIP drive

For some old BIOS systems, only booting from USB-ZIP drives is supported. This method allows you to still boot from a USB-HDD drive.

Warning: This will destroy all information on your USB flash drive!
  • Download syslinux and mtools from the official repositories.
  • Find your usb drive with lsblk.
  • Type mkdiskimage -4 /dev/sdx 0 64 32 (replace x with the letter of your drive). This will take a while.

From here continue with the manual formatting method. The partition will be /dev/sdx4 due to the way ZIP drives work.

Note: Do not format the drive as FAT32; keep it as FAT16.

Using UNetbootin

UNetbootin can be used on any Linux distribution or Windows to copy your iso to a USB device. However, Unetbootin overwrites syslinux.cfg, so it creates a USB device that does not boot properly. For this reason, Unetbootin is not recommended -- please use dd or one of the other methods discussed in this topic.

Warning: UNetbootin writes over the default syslinux.cfg; this must be restored before the USB device will boot properly.

Edit syslinux.cfg:

sysconfig.cfg
default menu.c32
prompt 0
menu title Archlinux Installer
timeout 100

label unetbootindefault
menu label Archlinux_x86_64
kernel /arch/boot/x86_64/vmlinuz
append initrd=/arch/boot/x86_64/archiso.img archisodevice=/dev/sdx1 ../../

In /dev/sdx1 you must replace x with the first free letter after the last letter in use on the system where you are installing Arch Linux (e.g. if you have two hard drives, use c.). You can make this change during the first phase of boot by pressing Tab when the menu is shown.

In Windows

The Flashnul way

flashnul is an utility to verify the functionality and maintenance of Flash-Memory (USB-Flash, IDE-Flash, SecureDigital, MMC, MemoryStick, SmartMedia, XD, CompactFlash etc).

From a command prompt, invoke flashnul with -p, and determine which device index is your USB drive, e.g.:

C:\>flashnul -p
Avaible physical drives:
Avaible logical disks:
C:\
D:\
E:\

When you have determined which device is the correct one, you can write the image to your drive, by invoking flashnul with the device index, -L, and the path to your image, e.g:

C:\>flashnul E: -L path\to\arch.iso

As long as you are really sure you want to write the data, type yes, then wait a bit for it to write. If you get an access denied error, close any Explorer windows you have open.

If under Vista or Win7, you should open the console as administrator, or else flashnul will fail to open the stick as a block device and will only be able to write via the drive handle windows provides

Note: Confirmed that you need to use drive letter as opposed to number. flashnul 1rc1, Windows 7 x64.

Loading the installation media from RAM

Merge-arrows-2.pngThis article or section is a candidate for merging with Multiboot USB drive#Using Syslinux and memdisk.Merge-arrows-2.png

Notes: This is the same method, only Syslinux is installed from Windows. Considering that multiboot USB drive can be used to boot an installation media and it is already linked from the Related articles box at the top, maybe this section should be merged there? (Discuss in Talk:USB flash installation media#)

This method uses Syslinux and a Ramdisk (MEMDISK) to load the entire Arch Linux ISO image into RAM. Since this will be running entirely from system memory, you will need to make sure the system you will be installing this on has an adequate amount. A minimum amount of RAM between 500 MB and 1 GB should suffice for a MEMDISK based, Arch Linux install.

For more information on Arch Linux system requirements as well as those for MEMDISK see the Installation guide and here. For reference, here is the preceding forum thread.

Tip: Once the installer has completed loading you can simply remove the USB stick and even use it on a different machine to start the process all over again. Utilizing MEMDISK also allows booting and installing Arch Linux to and from the same USB flash drive.
Preparing the USB flash drive

Begin by formatting the USB flash drive as FAT32. Then create the following folders on the newly formatted drive.

  • Boot
    • Boot/ISOs
    • Boot/Settings
Copy the needed files to the USB flash drive

Next copy the ISO that you would like to boot to the Boot/ISOs folder. After that, extract from the following files from the latest release of syslinux from here and copy them into the following folders.

  • ./win32/syslinux.exe to the Desktop or Downloads folder on your system.
  • ./memdisk/memdisk to the Settings folder on your USB flash drive.
Create the configuration file

After copying the needed files, navigate to the USB flash drive, /boot/Settings and create a syslinux.cfg file.

Warning: On the INITRD line, be sure to use the name of the ISO file that you copied to your ISOs folder.
/Boot/Settings/syslinux.cfg
DEFAULT arch_iso

LABEL arch_iso
        MENU LABEL Arch Setup
        LINUX memdisk
        INITRD /Boot/ISOs/archlinux-version-x86_64.iso
        APPEND iso

For more information on Syslinux see the Arch Wiki article.

Final steps

Finally, create a *.bat file where syslinux.exe is located and run it ("Run as administrator" if you are on Vista or Windows 7):

C:\Documents and Settings\username\Desktop\install.bat
@echo off
syslinux.exe -m -a -d /Boot/Settings X:

Troubleshooting

  • If you get the "device did not show up after 30 seconds" error due to the /dev/disk/by-label/ARCH_YYYYMM not mounting, try renaming your USB media to ARCH_YYYYMM (e.g. ARCH_201501).
  • If you get errors, try using another USB device. There are case scenarios in which it solved all issues.

See also