-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operation not permitted #56
Comments
I'm having a comparable problem, tried to delete all files/folders from the FATX F partition, it shows 'operation not permitted' even though I'm root.
Actually, for some weird reason; when opening the folder in the GUI of Ubuntu, I was able to delete some of the files. Only "Marvel Nemesis - Rise Of The Imperfects" Maybe related to the "-" and "&" in the file path? |
Same problem here, some files like "c_drdmk1_bat1.wav" (KOTOR) refuse to be copied. Using another windows non-free app I get to copy those files to the F partition but I can observe that even that app has a drop in the MB/s that arrives to 0, but after 2 or 3 seconds, as I said, it gets to copy the file. It can arrive with large files of several GB to others of just 40 Kb. It is really a mystery. I even tried to slice those large files (under 3 and 2 GB) and recompose them on the F partition and for whatever reason, the fatal message appeared*. Any hints? *It appears more or less at the part correspondent to the bites wich pressumably active the error when the file is being copied without slicing , if the file is lets say, 3 gb and the problem arrives when 2,8 gb are copied then the slice number 1 and 2 will pass but not the third one, acitivating the error when 0,8 gb have been already copied, further forensics are impossible but lack of time If I partially copy one problematic file and then I retry without erasing it (with another name) same happens, wich makes me thing than it is like a cursed bit of the file, but it goes unnoticed when using other HDDs WITH another filesystems (fat32 for example) EDIT: the other program now says the file is corrupt too. I tried with ddrescue, no luck neither, so I guess that sometimes s*** happens and yo can do nothing about it, but it is clear to me that it is not a fatx error , so after MANY hours of research, I could say that this topic should be marked as solved, as it is a file problem, not a fatx one |
Below are the commands I ran:
I got error as below:
The text was updated successfully, but these errors were encountered: