This doesn't seem to be an apfs volume (invalid superblock).

[CliveMcCarthy]

I get the message:

sudo apfs-fuse /dev/sdf /media/mac_apfs
This doesn't seem to be an apfs volume (invalid superblock).
Unable to load container.

From what I can tell /dev/sdf look like the apfs drive since it is the only drive without a model number and I recognize all the others.

Disk /dev/sdf: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model:                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Any suggestions, please.

[macdabby]

I came here looking for the same answer. I can confirm that this is the APFS drive . I have tried both /dev/sda and /dev/sda1

Disk /dev/sda: 3.64 TiB, 4000752599040 bytes, 7813969920 sectors
Disk model: My Passport 260D
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F45C5282-BB58-4160-B707-AC365EDCDF9C

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7813969879 7813967832  3.6T Apple APFS

[femoyano]

I came here with the same question as the above. In my case the mistake was that I had selected the first disk partition (in my case device /dev/sdb1, which was an EFI partition) but the APFS partition was the second (in my case device /dev/sdb2). In addition, it only worked after I added the option -v 1, which tells apfs-fuse to select the second volume, as described in the git page. The command was thus: sudo ./apfs-fuse -v 1 /dev/sdb2 /mountdir Note that I was then only able to access it as root. The uid and gid options didn't seem to change this.