I've got an fully encrypted USB drive (18,2 TiB, ~16TiB used, exFAT in the encrypted part) and the following issue:
Mounted in MacOS X (newest stable version of MacOS and VeraCrypt) it is not possible to create new folders and sometimes files, but not everytime. Error -50 is reported. Mounted in Windows 11 (newest stable patchlevel and newest VeraCrypt version) everything works fine.
I tried the first aid from the disk utility of MacOS -> no real issues, only a folder with length 0 is detected and removed - that is the folder, that was tried to be created.
chkdsk under windows won't start the scan -> somethin like "both of the start parameters are damaged, stopping scan".
For testing purposes I took antother 18,2 TiB drive and created a file container of the full size of the drive. In MacOS it qould have taken days, because it was not possible to choose quick format. So I created it with a Windows system (again exFAT as the fs in the container). With windows everything is fine, with MacOS it is not possible to mount that file. The error states no file system in the container. So I encrypted the drive completly, like the other one and copied the files from the not working one, to the new one (with MacOS). For the first couple of TiB it was possible to create new folders. After everything was copied, the same error (-50) occured.
Any ideas, what's wrong?
Best Regards
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great idea.
Of course I searched for the error, but there is nothing that solves the issue or find the cause.
Meanwhile I copied everything to antother USB device of the same size. Also verycrypt encrypted, but with a windows system. On mounting this device on a mac os system, it states, that there is no file system that can be mounted. I begin to belive, that there is a serious problem with verycrypt on mac :-(
Last edit: David Zacharias 2023-12-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey,
I've got an fully encrypted USB drive (18,2 TiB, ~16TiB used, exFAT in the encrypted part) and the following issue:
Mounted in MacOS X (newest stable version of MacOS and VeraCrypt) it is not possible to create new folders and sometimes files, but not everytime. Error -50 is reported. Mounted in Windows 11 (newest stable patchlevel and newest VeraCrypt version) everything works fine.
I tried the first aid from the disk utility of MacOS -> no real issues, only a folder with length 0 is detected and removed - that is the folder, that was tried to be created.
chkdsk under windows won't start the scan -> somethin like "both of the start parameters are damaged, stopping scan".
For testing purposes I took antother 18,2 TiB drive and created a file container of the full size of the drive. In MacOS it qould have taken days, because it was not possible to choose quick format. So I created it with a Windows system (again exFAT as the fs in the container). With windows everything is fine, with MacOS it is not possible to mount that file. The error states no file system in the container. So I encrypted the drive completly, like the other one and copied the files from the not working one, to the new one (with MacOS). For the first couple of TiB it was possible to create new folders. After everything was copied, the same error (-50) occured.
Any ideas, what's wrong?
Best Regards
David
Hi David,
Google search using the following syntax since there are many causes to error 50 in the Mac OS environment.
Great idea.
Of course I searched for the error, but there is nothing that solves the issue or find the cause.
Meanwhile I copied everything to antother USB device of the same size. Also verycrypt encrypted, but with a windows system. On mounting this device on a mac os system, it states, that there is no file system that can be mounted. I begin to belive, that there is a serious problem with verycrypt on mac :-(
Last edit: David Zacharias 2023-12-07
Hmm. Or exFAT on Mac is broken.
I will test some more without VeraCrypt encryption. Maybe it leads somewhere
Looks like an issue with MacOS Sonoma.
https://discussions.apple.com/thread/255173291?sortBy=best
and maybe related to this:
https://sourceforge.net/p/veracrypt/discussion/technical/thread/f1596c1ad4/