Menu

help: hdiutil attach failed -- no mountable filesystems found

2016-12-13
2019-10-23
  • Kirk Holmes

    Kirk Holmes - 2016-12-13

    I have been using a volume for a month or so and suddenly began getting the hdiutil error message that no mountable filesystem could be found. Searching Google, it seems to be a common problem with TrueCrypt and related products. I can not find a way around it. I tried mounting as read only and that did not work.

    I am running on a Macbook with Seirra OS.

    Has anyone gotten around this problem?

     
  • Alexandre Takacs

    Having a fairly similar issue, but we a frshly formated (aka encrypted) drive. Did you manage to solve this ?

     
  • Felix Franz

    Felix Franz - 2017-11-12

    Try selecting "Do not mount" in VeryCrypt and then mount the disk manually. Open terminal:

    diskutil list
    /dev/disk5 (disk image):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            VERACRYPT               +10.2 MB    disk5
    
    diskutil mount /dev/disk5
    Volume VERACRYPT on /dev/disk5 mounted
    

    There seems to be a problem with FAT32 and exFAT filesystems. After manually mounting the volume, I created a new with HFS+. I was able to mount it without any problems. I'm using Mac OSX High Sierra.

     
  • nszceta

    nszceta - 2017-11-26

    Missing slot can be the problem.

    veracrypt --slot=1 --mount path_to_encrypted [optional_mount_point]
    

    Please comment if this worked for you.

     

    Last edit: nszceta 2017-11-26
  • Adjacent

    Adjacent - 2017-12-17

    I'm having the same issue. On macbook running High Sierra. Using latest veracrypt. My computer crashed while the device (SD card) was mounted. When it rebooted, tried to mount it and got that error. Tried to solutions mentioned in this thread. Tried manually mounting it, got "cannot mount" error. Tried the veracrypt command, says "Command not found." on terminal. Would hate to lose these important files. :(

     
  • Mark Ruys

    Mark Ruys - 2018-01-06

    In the preferences I have Mount volumes as read-only enabled. When I create a new volume, I have to make sure it's mounted read/write or else this "hdiutil attach failed -- no mountable filesystems found" message pops up after creation of a new volume.

     
  • Aleksandr Khomenko

    This issue have a solution. When you mount encrypted container you have to previously make a directory in /Volumes and mount container into it.  See at picture
    
     

    Last edit: Aleksandr Khomenko 2018-01-23
  • Sharon

    Sharon - 2018-06-14

    I have same error
    I can mount on windows but not on my new mac
    other containers can be mount regulary
    Only one is now working :(

     
  • Person

    Person - 2018-09-30

    I used to get this whenever an external HD lost connection while mounted. What worked for me: Make sure you are NOT trying to mount the volume as read-only, since that prevents the operating system from doing whatever it needs to do to fix the file system after a hot disconnect, thus making the disk unmountable. Mounting as read/write fixed it for me – after that you may continue mounting it as read-only.

     

    Last edit: Person 2018-09-30
  • 8ctavian

    8ctavian - 2019-04-14

    Hi, I don't know if any of the previous posters resolved their problem but I couldn't.
    Working on a macbook Pro, 10.4.1 mojave, I have a 2T encrypted HD drive with a normal partition and a hidden one.
    I was copying files from another HD to this one when both got disconnected and veracrypt closed. Next thing I know is that I couldn't mount any of the partitions and getting that error " hdiutil attach failed -- no mountable filesystems found". No matter what.
    The encryption was created using MAC OS Extended. I tried to mount it on Windows PC, with no avail.
    One poster above mentioned not to mount the HD and using terminal but i didn't understand his command lines, if someone could explain.
    Thanks to anyone willing to help

     
  • Murat Dedeoglu

    Murat Dedeoglu - 2019-10-23

    Try formatting disk exfat,fat or macosx filesystem. if you select none it doesn't work.

     

Log in to post a comment.