File vault a second disk (besides boot disk)

I booted from 1TB to manage vault users. I deleted my account. fdesetup list now is empty. I reset the keychain on the SSD so there are no entries in there. Since there is no account in the encrypted disk and no keychain I should be able to login with my regular account and not have it deny access. There must be somewhere else the account and password is being stored. Again, this all started when I got this screen below and check "remember this password... Before checking this screen I could login and after os x came up it then asked for disk password, which works fine. Now I have to login as Admin, enter disk password, then switch/login user as myself.

Yep, that's my next step. It is only 54% encrypted. So I'll wait for it to finish.

Hi Linc,

I decrypted, rebooted, then re-encrypted. When re-encrypting it never asked for users to add to encrypt password, only a disk password. Probably did not ask for users because the 1TB encrypted drive is not the boot device. And, after re encrypting I have the same issue with my account, it will not login. I have to login as Admin, enter the disk password, then switch/login with my account. Somthing is stuck in either the user profile or keychain inside the 1TB vault. I never had this issue until I checked the box to save the disk password in my keychain. It would appear even unencrypting the drive did not clear this out. When I reboot into the 1TB so I can run fdesetup status It says "Fault is on. Master keychain appears to be installed". I may just be left with hasle of logining in twice to finally get vaulted 1TB drive up before I can login.

Hi Linc,

The keychain issue could just be a coincidence to the whole drive access issue in timing of how far the encryption process was. The 1TB drive takes about 28 hours to encrypt. Last week when I first started the encryption process I was able to login with regular account (I rebooted before encryption was finished) after starting the encryption process without access denied due to internal error. My 1TB drive has nearly 700GB on it and it could very well be that the user account home drive path, which is on the 1TB (3 years ago I pointed the SSD boot drive user account, via advanced options, to the 1TB drive where all my user data is and certainly would not fit on the 256gb SSD) was not yet encrypted and thus I was able to login. Now that the entire 1TB drive IS encrypted the user account home drive path is not available until the drive can be unlocked. Login as admin, which is entirely stored on SSD boot, allows me to unlock the encrypted 1TB drive, then login as my account and load home path. Just a guess.

Since there are 2 disks the solution is to mount non booted vault disk before login process. Here is a link on how to: https://github.com/jridgewell/unlock

Would have to modify the script to NOT store the disk pw in system keychain. Something similar to this script to prompt to unlock the disk before login process.