Fatal error during new project creation

Hi, I'm new to Unity and yesterday I installed Unity 2019 on my iMac (macOS Mojave 10.14.4 - 4.2 GHz Intel Core i7 - 32 GB of memory).
If I try to create a new project (2D or 3D) on the main drive everything is fine.
But if I try to create a new project (2D or 3D) on the external 2T disk I get an error: "Fatal Error! attempt to write a readonly database". I receive this message during the importing assets process, as shown in the screenshot below.
Can someone help me?
Thank you
(Please excuse my not perfect English.)

 

Make sure you can actually write to that drive. I'm no mac user so you might want to google it.

 

@xVergilx
Thanks for the reply. Of course, on the external driver I have my projects that I use with different applications.
I tried searching on google before asking the question but I didn't find anything.

 

Any solution? Who can help me?

 

It sounds like a permissions issue to me as well.

 

I tried to create the project on another type of external disk, but the error I get is always the same.
The error occurs when the file "TMP_SDF Internal SSD.shader" is processed. Could it help to find the solution?

 

Have you tried creating a new project on the internal drive and then transfering it to the external one?

 

I had already tried it and it works. In fact it was the only solution that could work. The fact remains that I cannot create projects on external disks. Maybe it's a Unity bug.

@xVergilx
Have you tried creating a new project on an external drive with Unity 2019? Can you do this test if you don't mind? So we can make a comparison with Windows and see if the error exists, thank you for your kindness.

 

I use Unity version 2019.1.1f1 Personal

 

I have the same setup and the same unity version, and I also get this error. Would love to find a solution...

 

I have a similar issue on Debian SID, but unity just stalls and doesn't give any errors, then the OS says that unity isn't responding. I read the log files and traced the issue to importing project settings assets. This are the last lines that unity logged:

Code (csharp):

1. Updating ProjectSettings/InputManager.asset - GUID: 00000000000000002000000000000000...
2. done. [Time: 3.326000 ms]
3. Updating ProjectSettings/TagManager.asset - GUID: 00000000000000003000000000000000...
4. done. [Time: 3.206000 ms]
5. Updating ProjectSettings/ProjectSettings.asset - GUID: 00000000000000004000000000000000...
6. done. [Time: 4.401000 ms]
7. Updating ProjectSettings/NavMeshAreas.asset - GUID: 00000000000000004100000000000000...
8. done. [Time: 2.743000 ms]
9. Updating ProjectSettings/Physics2DSettings.asset - GUID: 00000000000000005100000000000000...
10. done. [Time: 2.783000 ms]

I suspect it's trying to load the next asset but fails to do so, because the previous asset loaded successfully so that's not the problem.
I opened the project folder and navigated to ProjectSettings, that's when I noticed that VFXManager.asset wasn't a YAML formatted file. Perhaps this has something to do with it?