I've also tried simplistic things like rebooting, etc. I have enough space on my hard drive to support the decrypted files (the Sparse Disk Image Bundle is about 600 MB and I have about 600 GB available). I know I'm typing the right password (it prompts me again if I enter the wrong password). I have all file types turned on to show in Finder->Preferences->General->Show these items in the desktop. I can't see the disk being mounted in Finder, and thus can no longer access my critical files. However recently when I enter the correct password, nothing happens. Within that disk I have all sorts of important folders and files including tax information and other sensitive personal information. For years I've been able to decrypt it, and once done it mounts a disk on Finder. Sparse Disk Image Bundle won't mount disk after encryption I have an encrypted Sparse Disk Image Bundle. The first of these two assumptions has held true in my experience but the assumption that they will always be maintained, regression tested and improved has not. I use native apps when possible with the expectation that, unlike third-party apps which can come and go with the seasons, the native apps will always be available and will always be maintained and kept up to date with the changing environment and usage modes. This also seems true of certain other MacOS utility programs such as the native Contacts app, which responds incredibly slowly past a certain database size and seems like no one has been responsible for updating and regression testing it for more than a decade. I suspect that no one has been maintaining this utility at Apple for a long time. FAILS when source folder size is 71.1MB cannot create target file.WORKS when source folder size is 67.1MB or smaller, target file size is 65.7MB. Just today, I confirmed this and narrowed it down to this bracket experimentally: It started happening before I upgraded my computer and continues to happen on my new computer - neither of which were/are anywhere near their secondary storage capacity, so the only remaining possibility is that the file size crossed a threshold. This began happening just recently after more than a decade of using this feature to create an encrypted backup of my Quicken file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |