Recover files from an old Linux drive using your Mac

Updated September 2026 · dead laptops, retired servers, old external drives

There's a very specific moment when this guide matters: an old machine won't boot, the files exist only on its disk, and the only working computer in the house is a Mac. Good news — for the most common Linux setups, the Mac is enough.

Step 1: get the drive connected

Pull the drive and put it in a USB enclosure or dock (2.5" SATA enclosures cost ~15€; 3.5" drives need a powered dock; NVMe needs an NVMe enclosure). Plug it in and ignore macOS's "disk not readable" alert — that's expected, don't initialize anything.

Step 2: identify what you're looking at

Typical Linux disks have a small boot partition (FAT — macOS reads it, nothing useful inside) and one big root or home partition. What that big partition contains decides everything:

• Plain ext4 — desktop Ubuntu, Mint, Debian, Raspberry Pi OS: mounts directly. This is the majority of home machines.
• LVM (Ubuntu Server default, Fedora pre-33) — a container layer macOS can't open; you'll need a Linux VM to activate it.
• btrfs (Fedora 33+, openSUSE) — different filesystem entirely; ext4 tools don't apply.
• LUKS encrypted — nothing reads it without the passphrase and a Linux environment.

Omnimount's detector tells you which case you have the moment you plug the disk in.

Step 3: mount read-only and copy

For the ext4 case: mount read-only (you're rescuing, not editing), open the volume in Finder and copy what matters. Home directories live in /home/yourname. As the mount runs privileged you'll see every user's files regardless of their Linux permissions.

If the drive itself is dying

Clicking noises, disconnections, files that stall at 90%: stop copying file by file. Clone the whole drive to an image first — one sequential pass is the gentlest thing you can do to a failing disk — and rescue from the image afterwards. If the journal is dirty (machine died mid-write), run a filesystem check before trusting what you copy.