I run a dual-boot system on an SSD while I keep my project files & media on a separate NTFS drive. I previously ran Mint and had no troubles working on my projects being stored this way with VS Code. I installed OpenSUSE about a week ago and just got round to try working on a project but when I try to build a Rust project I’m stuck with the following error message;
/drives/Storage/Data/Projects/Bevy/voxel_prototype> cargo build
Compiling proc-macro2 v1.0.93
error: failed to run custom build command for `proc-macro2 v1.0.93`
Caused by:
could not execute process `/drives/Storage/Data/Projects/Bevy/voxel_prototype/target/debug/build/proc-macro2-d0e6f1b52a04fc2f/build-script-build` (never executed)
Caused by:
Permission denied (os error 13)
warning: build failed, waiting for other jobs to finish...
Attempting to change the permissions through the UI or with chmod has no effect, even though logging showed the expected files were being worked on.
Here is the drive’s entry in fstab, I’ve verified that my user & group are indeed 1000. I’ve tried changing from defaults to the extra following options, as well as adding -3g to ntfs. I’ve rebooted at several stages throughout the process to properly unmount & mount the drive when I make changes to fstab.
I’ve already disabled Window’s fast boot as part of keeping rEFInd running properly, but I have booted back into windows to double check that it is disabled.
I’ve tried running chkdisk while in Windows and ntfsfix while in Linux, but neither helped.
I’ve run out of google results to try, any help would be greatly appreciated, thanks.
Better not use non-Linux file systems for Linux tasks. Only use them for direct exchange with non-Linux systems.
AFAIK non-Linux file systems are always mounted without any execute permissions set for all files. Basic safety.
I see this message about not being able to execute. You talk about no write access, I do not see that in what you post.
Indeed, all owning UID, GUID and permissions set for the files in non-Linux file systems are simulated. They are set on mount through the options like uid=1000,gid=1000but they can not be changed.
BTW, IMO the defaults is only used as a placeholder when one does not have any options. You have options here, thus it is superfluous and may be confusing.
I have the drive on NTFS since I want Windows to be able to read-write to the drive as it is general storage for media, notes, and the like.
Prior to OpenSUSE I ran Mint Cinnamon, which had no issue executing the same files from the same drive. I kept root in a separate partition and installed over that, the only difference being that it is now BTRFS rather than ext4.
My mistake, I began writing this when I had an issue saving files, but revised the draft after I fixed that myself but forgot to change the title.
I wasn’t certain that I’d included all the necessary options that might come with defaults since I’m learning as I go.
The solution for me was to boot into Windows and do a full shutdown by holding shift when pressing shut down.
Disabling fast boot & running powercfg /h off wasn’t enough it seems.