Time Machine (Encrypted) Not Auto-Mounting on Boot with 10.14.4

I found another method and it works again with my mac.

Go to Applications -> Utilities -> Keychain Access.app , open it.

• Keychains, select "login"
• Category, select "All items"

After that sort list by click Kind column and find Kind "encrypted volume password", where have the name is your Volume name can not auto mount. Right click and Delete it. If have more than two, please remove all.

Then reboot.

After boot, if it do not auto mount and required input password, OPEN Disk Utility and mount it. When it asks password please type and click Always allow.

Done! You can reboot and see the result.

Thank you.

I do have the issue on my Mac mini 2018 with an external encrypted hdd formatted with journaled HFS+ for TM backup.

In addition to what is reported in this thread, i.e. no mount on reboot, I found my external TM Backup volume also dismounted when I returned to my MM after not using it for a couple of hours. I reported this issue to AppleCare. To date they have come up with two measures which improved the situation, after a complete reinstall of macOS. Firstly they asked me to delete all files in Library/Caches, Library/LaunchAgents, and Library/LaunchDaemons. In my environment, this reinstated the auto mount of my TM Backup volume. The second recommendation was to disable System Preferences > Energy Saver > 'Put hard disks to sleep when possible' which, plus a restart, kept my TM Backup volume mounted since 30 hours now...

@gdexpert:

I think it would be interesting to understand what makes you not experiencing the issue. Do you have the Energy Saver Hard Disk Sleep option on or off?

I ran into this problem with an external time machine drive and another external hard drive, both formatted as AFPS. I wrote a startup script following these steps to address the problem:

1) plug in your external hard drive and mount with the Disk Utility app (under Applications / Utilities) by selecting the drive from the list in the left side and clicking the Mount icon

2) open Terminal (under Applications / Utilities), type in "diskutil coreStorage list" and press enter

3) each APFS volume will have 4 entries, the first is a "Logical Volume Group", then a "Physical Volume", then a "Logical Volume Family", and finally a "Logical Volume". Copy the identifier following "Logical Volume", it's in the following format (where X can be a number or a letter) XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

4) open the Script Editor App (under Applications/Utilities) and click "New Document" or simply press Cmd + N

5) for each APFS drive you want to mount on startup, enter the following, using the volume identifier copied in step 3:

delay 15

do shell script "diskutil coreStorage unlockVolume XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -passphrase [volume password]"

[Note] to unlock multiple volumes, simply add " && " followed the above command (using the volume identifier from the second hard drive in step 3):

delay 15

do shell script "diskutil coreStorage unlockVolume XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -passphrase [volume password] && diskutil coreStorage unlockVolume XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -passphrase [volume password]"

6) save the script somewhere, then select File / Export; under "File Format" select "Application"; leave everything else blank and save the application somewhere

7) open the System Preferences app (click on the apple menu at the top left of your taskbar), then click on Users & Groups; select your user, then click on the Login Items tab; drag the application you saved in step 6 into the list

8) when you restart your computer, your hard drives should be automatically unlocked and mounted

Whenever apple comes out with another update, I would remove the script from your startup items and see if the issue has been fixed. If not, this should continue to work until Apple resolves the issue.

Hi,

same problem here. macOS 10.14.4 (18E226). Two external drives: one USB-Drive for Time Machine, one Thunderbold-Drive for "normal" Stuff.

What I have figured out so long:

• Both drives will not auto-mount after a start, but will mount fine via Diskutil
• Decrypt the drive: the drive will just fine auto-mount as before the update to 10.14.4
• Encrypt the same drive again: drive will not auto-mount (and yeah: de- / encrypt an 4 TB drive will take AGES... :-))
• BUT: If I boot and login WITHOUT the drives powered on, and power the drives on AFTER the login, the encrypted drives will just auto-mount normal

So, it seems that Apple has an issue here. I don't know, how this could be overseen in the beta-stage ... but it was. So, at the moment I will keep my drives Decryptes until Apple will come up with a solution. I can't trust the encryption-mechanism at this time...

C.

I got the missing in my ideas here, @removetxtforward

First, I had the same issued that is encrypted Time Machine Volume can not auto mount at startup / boot. So in the first-time boot into 10.14.4, I did not see the Time Machine Volume.

Second, I open the Disk Utility and then mount it, and it required me about Keychain password. I typed it, and clicked Always allow.

After that I reboot, Time Machine volume still not auto mount. So I have go to Disk Utility again and click mount, this time, it did not ask password Keychain again.

So, I finger out that is only add the UUID of Time Machine Volume to make it automount at startup/boot.

And then I followed the link https://discussions.apple.com/docs/DOC-7942 to add UUID into automount.

That is the a temp solution for this version 10.14.4. And it works with my Macbook Pro.

PS: this is the first version macOS I met this issue.

I had the same issue like you. So I found the solution for this, just add UUID to automount, follow this post https://discussions.apple.com/docs/DOC-7942

Hope it can help you, at this version.

Fix confirmed in 10.14.5 for an iMac Pro, both with an existing encrypted USB disk and a new encrypted USB disk.

I can confirm that after upgrading to 10.14.5 today, my encrypted drives now auto-mount at login just as they did prior to 10.14.4. Yay!

In my case, "Put hard disks to sleep when possible" is checked in Energy Saver.

Exactly the same here: since 10.14.4, one non-encrypted APFS drive automounts at startup, three Time Machine encrypted HFS+ drives don't. Sometimes one alerts pops up at a later time, asking to authenticate with my user password, to provide access to the drive encryption password stored in the keychain; I imagine this is when a Time Machine backup is initiated. Other than that, I have to open Disk Utility where the drives are shown but their names greyed out. Clicking the Mount button, the drive encryption password was asked the first time IIRC; opting then for this password to be remembered (there was a checkbox for that in the dialog), all the other times after that all that needs to be done is click the Mount button. Still, this needs to be done for each and every drive each time the Mac is rebooted. Probably that doesn't matter, but my Mac internal drive is encrypted too.

I'm having this problem, too. But, to verify, I went ahead and decrypted my Time Machine backup drive (took a couple of days but backups happen during decryption so you're covered if you want to take this route) and it mounted just like normal after a reboot.

So Apple's update has broken encrypted Time Machine backup drive automounting. I'm going to re-encrypt later on and see if creating an /etc/fstab file solves the problem.

I have a similar problem, except that sometimes I get prompted to enter the password for the disk, but when I enter it, it says it's already unlocked and prompts me to open Disk Utility to mount it. When I open Disk Utility, I can see the drive and that it's not mounted. I click the "Mount" button, and it mounts just fine. It just doesn't mount automatically when plugged in or after a reboot.

All I can suggest is to make sure everyone having this problem provides feedback to Apple since they do not monitor these discussions closely. By all means include a link to this discussion so they can see the extent of the problem. If you have a developer ID, you should also submit a bug there, as Apple pays more attention to those. Here's the link to give feedback: https://www.apple.com/feedback/macos.html