See and for a comparison and perspective on the use of those tools and why dd may be the least adapted one. using pv: # pv path/to/archlinux- version-x86_64.iso > /dev/disk/by-id/usb- My_flash_drive.using tee: # tee /dev/disk/by-id/usb- My_flash_drive.using dd: # dd bs=4M if= path/to/archlinux- version-x86_64.iso of=/dev/disk/by-id/usb- My_flash_drive conv=fsync oflag=direct status=progress.using cp(1): # cp path/to/archlinux- version-x86_64.iso /dev/disk/by-id/usb- My_flash_drive.using cat(1): # cat path/to/archlinux- version-x86_64.iso > /dev/disk/by-id/usb- My_flash_drive.(Do not append a partition number, so do not use something like /dev/disk/by-id/usb-Kingston_DataTraveler_2.0_408D5C1654FDB471E98BED5C-0:0 -part1 or /dev/sdb 1): Run the following command, replacing /dev/disk/by-id/usb- My_flash_drive with your drive, e.g. This method is recommended due to its simplicity and universal availability, since these tools are part of coreutils (pulled in by the base meta package).įind out the name of your USB drive with ls -l /dev/disk/by-id/usb-* and check with lsblk to make sure that it is not mounted. In GNU/Linux Using basic command line utilities This means the ISO cannot be written to a 4Kn Advanced Format drive using this method. Note: If, instead of a USB flash drive or an SD card, you want to write the ISO to a hard disk drive or a solid state drive, make sure the drive's logical sector size is not larger than 2048 bytes (the ISO 9660 sector size) and aligns to it.

Ventoy macos iso