I have recently started having a strange issue with Espionage version 3.7.4 on macOS Big Sur (version 11.7.10).
When I unlock a disk image, it unlocks but then immediately locks/unmounts the image. As far as I know, I have done nothing that would have caused the default behavior to change, but Big Sur has been a less-than-great upgrade, so who knows.
I can manually mount the image, but using the Espionage 3 interface it will not stay mounted.
Any ideas?
Thanks!
Scott
Hi Scott,
We did not test on Big Sur, and we also did not modify any code related to this, so it's possible something Apple did broke something.
Please try reverting to an older version (which is essentially the same as 3.7.4):
https://www.espionageapp.com/releases/Espionage3.7.3.dmg
Hi Greg,
Thank you for the reply and link to the previous version. I installed it, but the problem persists.
Scott
If the problem persists with the old version, I'm not sure what to tell you. It sounds like there could be some other software installed on your system that's interfering with Espionage, unmounting the images that it's mounting.
If you email support@taoeffect.com you can try to schedule a remote session with our tech team to troubleshoot more.
Hello Scott, did you try to create a new folder and see if it behaves the same?
Cheers
Zsolt
I created a new folder. It worked.
I then I attempted to decrypt the problem folder, but that failed leaving an empty "_Rescued Items" folder. I was able to manually mount the old sparsebundle and copy the data to a new location. Then I dragged the new folder into Espionage and let it set up a new encrypted folder; this worked. The new folder now mounts within Espionage as it should. I am a little concerned that perhaps I might be missing some recently added files... I will have to check a recent backup just to make sure that everything is there and the failed decryption did not whack anything.
I still find it rather odd that there was a problem in the first place. Is there an error log that I can check?
Scott
Hello Scott, I'm glad this did the trick. It is not 100% nice solution as we do not know what exactly the problem with the original folder was. Usually it is some kind of a permission problem. But the sudden unmount was never reported before. Failing to recover properly that yes.
But I can see that you understand it quite well, so I guess we do not need to be worried.
If you have any specific question, please let me know.
And no, there are no error logs, we do write some stuff into console, but I never found anything useful there. You might want to search for diskutil entries, as that is the process doing the mount and unmount part.
Cheers
Zsolt