Skip to content
podkit

Mounting and Ejecting

Mounting makes an iPod’s filesystem accessible so podkit can read and write to it. Ejecting flushes pending writes and unmounts the volume safely before you disconnect the cable.

When mounting is handled automatically

In most cases you don’t need to think about mounting. When you run podkit sync, podkit expects the device to already be mounted. macOS mounts standard iPods automatically when you plug them in.

For iFlash-modified iPods (SD card storage replacements), macOS may refuse to automount the volume. In that case, podkit device add will detect this and guide you through mounting — see Adding a Device and the macOS Mounting Troubleshooting guide.

macOS

Mounting a registered device

If a registered device is not mounted (e.g. you dismissed the macOS dialog, or it’s an iFlash device you’ve mounted before), you can mount it with:

Terminal window
# Mount the default device
podkit device mount


# Mount a specific device
podkit device mount classic

podkit identifies the device by its volumeUuid and mounts it to the expected mount point.

Ejecting

Always eject your iPod before disconnecting the cable to avoid database corruption:

Terminal window
# Eject the default device
podkit device eject


# Eject a specific device
podkit device eject nano

Ejecting flushes all pending writes and unmounts the volume.

Auto-eject after sync

Use --eject to automatically eject the device when a sync completes:

Terminal window
podkit sync --eject
podkit sync --device nano --eject

This is convenient for a plug-sync-unplug workflow.

iFlash devices

iFlash-modified iPods use SD cards in place of the original hard drive. macOS refuses to automatically mount large FAT32 volumes above an undocumented size threshold, so these devices often don’t mount on their own.

When you run podkit device add myipod without specifying a path, podkit scans for both mounted and unmounted devices. If it finds an unmounted iFlash device, it will:

  1. Assess the device (block size, capacity, USB model) before attempting anything
  2. Show you what it found
  3. Attempt diskutil mount (works for normal unmounted devices)
  4. If that fails, explain why and tell you to re-run with sudo
Found iPod: TERAPOD (1.0 TB) — not mounted
  Model:   iPod Classic 5th generation
  Storage: iFlash confirmed — 2048-byte block size; Capacity exceeds iPod Classic maximum


Attempting to mount...
macOS cannot automatically mount this device.


iFlash confirmed by:
  • 2048-byte block size: 2048
    iFlash adapters emulate optical media sectors; standard iPod HDDs use 512-byte sectors
  • Capacity exceeds iPod Classic maximum: 1.0 TB
    Original iPod Classic maximum was 160 GB


macOS refuses to mount large FAT32 volumes through its normal mechanisms.
Elevated privileges are required to mount this device directly.


Run:  sudo podkit device add myipod

Re-running with sudo uses mount -t msdos directly, which bypasses macOS’s automount restrictions.

For the full iFlash troubleshooting guide — including manual workarounds and a shell alias — see macOS Mounting Troubleshooting.

Linux

Linux support for mount and eject commands is not yet implemented. While podkit’s core sync functionality works on Linux, the podkit device mount and podkit device eject commands are not available.

In the meantime, use standard Linux tools:

Terminal window
# Mount
udisksctl mount -b /dev/sdX1
# or
sudo mount /dev/sdX1 /mnt/ipod


# Unmount
udisksctl unmount -b /dev/sdX1
# or
sudo umount /mnt/ipod

See Also