Updated November 2026. You’ve downloaded an ISO — Rocky Linux, OPNsense, some other operating system the networks would rather you rented by the hour — and you want a bootable USB stick. On a Mac, the most reliable way is still the command line and dd. No third-party downloader required, it is fast, and it consistently produces a bootable volume. The steps are the same on Apple Silicon and Intel.
A brief public-service announcement, because dd does not ask twice: this erases the target disk. The wrong disk number wipes that disk. Identify the stick by size and name, check the number twice, and back the Mac up first if there is anything on it you would rather keep.
1. Check the download
Hash the ISO and compare the result with the checksum the distro publishes. If they do not match, stop. You are about to write a corrupt or tampered image.
shasum -a 256 ~/Downloads/image.iso
2. Find the USB
Plug in the stick, open Terminal, and list external disks only:
diskutil list external
Identify /dev/diskN by its size and name. Write down N, then check it again. You want the whole disk (disk2, disk3, and so on), not a partition like disk3s2. Writing to a slice is how an earlier version of this post would fail you, and I do not intend to repeat that particular on-air blooper.
3. Unmount the whole disk (do not eject it)
macOS auto-mounts the stick’s partitions, and dd cannot open a disk that still has mounted volumes. That is the usual cause of Resource busy. Unmount the whole disk. Do not eject it — ejecting removes the device node you still need.
diskutil unmountDisk /dev/diskN
If it is still busy, Spotlight, Finder, or another app has it open, or macOS remounted it. Run unmountDisk again right before dd, or force it:
diskutil unmountDisk force /dev/diskN
4. Write the image
sudo dd if=~/Downloads/image.iso of=/dev/rdiskN bs=4m status=progress
A few details that actually matter:
- Use
rdiskN, the r-r-raw device. It is several times faster thandiskN. - Write to the whole disk (
/dev/rdiskN), never a partition (/dev/rdiskNs2). - macOS’s BSD
ddwants a lowercasemin the block size:bs=4m. Usebs=1mif you prefer. status=progressworks on macOS 13 Ventura and later. On older versions, leave it off and press Ctrl+T during the write to see progress.- When
ddfinishes, runsync.
sync
Example, with an OPNsense ISO in Downloads and the stick at /dev/disk3. Use the filename and disk number you actually have. That 3 is an example, not a suggestion.
sudo dd if=~/Downloads/OPNsense-dvd-amd64.iso of=/dev/rdisk3 bs=4m status=progress
sync
5. You probably do not need hdiutil
Modern Linux and BSD ISOs are hybrid images. Write them as-is. You only need hdiutil for an old ISO that is not hybrid:
hdiutil convert image.iso -format UDRW -o image.img
hdiutil adds .dmg to the name, so the file is image.img.dmg. Write that file with dd.
6. Verify the USB (optional, and worth it)
This should match the ISO’s hash from step 1. Read through dd as shown, rather than pointing head or cmp at the raw device directly, because the raw device only accepts block-aligned reads.
SIZE=$(stat -f%z ~/Downloads/image.iso)
sudo dd if=/dev/rdiskN bs=1m count=$(( (SIZE+1048575)/1048576 )) 2>/dev/null | head -c $SIZE | shasum -a 256
7. Eject
diskutil eject /dev/diskN
Gotchas
- “The disk you inserted was not readable by this computer” after the write is normal. macOS cannot read the Linux file system. Click Ignore or Eject, never Initialize.
sudo ddon/dev/rdiskNusually does not need Full Disk Access. Recent macOS may ask whether Terminal can access removable volumes — click Allow. If that was denied before, turn it back on in System Settings > Privacy & Security (Files and Folders, or Full Disk Access) for Terminal or iTerm.Operation not permittedorPermission deniedmeans you forgotsudoor missed that privacy prompt.Resource busymeans the disk is still mounted. Go back to step 3.- Booting differs by Mac. Intel Macs boot the USB by holding Option at startup. T2 Macs also need Startup Security Utility set to allow external boot. Apple Silicon Macs cannot boot x86 ISOs at all, so on those machines the stick is for other PCs. Only ARM64 installers like Asahi, or images you will run as UTM guests, apply there.
Prefer a GUI?
If you would rather not talk to dd directly, these will unmount, write, and (in Etcher’s case) verify for you:
- balenaEtcher is native on Apple Silicon. It unmounts the stick, writes it, and verifies it automatically.
- Raspberry Pi Imager also writes any
.imgor.isothrough “Use custom.”
That’s the show. Check the checksum, check the disk number twice, write to the raw whole disk, and eject. Stay wired.
