Closed avoidwork closed 4 years ago
sure you have the path name correct? full path or relative path specified?
i am sure. i double checked when i noticed the logs, by copying the path from the UI into a terminal and verifying it was correct.
here's a screenshot. the odd thing from my pov is this issue has only surfaced when the host os is linux & the drive is mounted there; previously i've run it in hyper-v vm's with the drive offline in host os and passed through, without issue, and also via docker container.
I'm really just curious if you've seen this before, or have any idea where i might look for the cause/fix.
Hi,
I ran into this issue, and I'm still digging deeper into it at this time; curious if there's a known solution. The function
forcePostProcess
has very straight forward code, which is failing for me.The path is set to a folder on an exfat mount with wide open permissions, which other applications are using. Really don't know if it's a partition table issue, or something else. Any ideas?