It’s late, and I may return to edit this after some rest…
Short story long:
I ran FileVault on a Snow Leopard box for years until the SATA bus on which the FileVault sparseimage had been living started having trouble (the SATA bus, not the drive or volume).
After pulling the drive from the offending SATA bus, I’d decided I’d had enough of FileVault. I cloned all the unlocked sparseimage’s contents — my usual account directory — directly to the /Users/[BSM] directory where said sparseimage lived before. All contents are in place and everything is a cloned match to the contents from within that old sparseimage.
Login window, of course, relies on a setting toggled in the Security prefPane denoting whether the account is using a FileVault sparseimage or not. That flag for my account is still set to FileVault on, even as the account directory no longer is.
My guess is Login window looks to either a plist parameter or something involving, idk, a keychain. Whatever the case, after resolving this SATA bus issue, I’m limited on that volume to logging in to the system as System Admin/root.
This fix is probably really simple, but I can’t brain at this point and figured having a discussion thread for posterity will not only help out now, but also for other people in the future. Cheers.
Short story long:
I ran FileVault on a Snow Leopard box for years until the SATA bus on which the FileVault sparseimage had been living started having trouble (the SATA bus, not the drive or volume).
After pulling the drive from the offending SATA bus, I’d decided I’d had enough of FileVault. I cloned all the unlocked sparseimage’s contents — my usual account directory — directly to the /Users/[BSM] directory where said sparseimage lived before. All contents are in place and everything is a cloned match to the contents from within that old sparseimage.
Login window, of course, relies on a setting toggled in the Security prefPane denoting whether the account is using a FileVault sparseimage or not. That flag for my account is still set to FileVault on, even as the account directory no longer is.
My guess is Login window looks to either a plist parameter or something involving, idk, a keychain. Whatever the case, after resolving this SATA bus issue, I’m limited on that volume to logging in to the system as System Admin/root.
This fix is probably really simple, but I can’t brain at this point and figured having a discussion thread for posterity will not only help out now, but also for other people in the future. Cheers.