mjhjmtu

My problem is similar to this previous StackExchange question: I connected my Android phone to my Linux computer (running the latest version of Debian) with a USB cable, which automatically initiated an MTP connection, and tried copying some files to an SD card. I got some error messages, and I believe one of the folders became corrupted.

In the Amaze file manager app, the folder that I believe became corrupted was no longer listed. Instead, there was a 0-byte file of the same name. When I tried to delete the file, nothing happened: I could select the file and click the delete button, but nothing happened.

When I accessed the parent folder through the Linux command line, neither the 0-byte file nor the folder was listed when I ran ls -la. Further, when I removed the SD card and plugged it directly into my computer, I still could not see the corrupted file with ls. The stock Samsung file manager did not list the file. The Solid Explorer file manager app did list the file, but when I attempted to delete it within the app, the delete operation failed.

I was tempted to just ignore the corrupted folder/file. However, when I tried to copy over the correct folder, it doesn't work: either the folder does not copy at all, or when the copy completes, there is an extra copy of the folder whose name contains one character less than the original folder name.

To elaborate on the second case (which is usually what happens): The original folder is called "R.E.M.". After copying that folder to the SD card and view its contents in Linux, I see two folders with identical contents: one named "R.E.M" (note the lack of the final period) and the other named "R.E.M.". In the Amaze file manager app, only the first folder is listed. If I try to delete either one of those folders in Linux, the other folder automatically deletes itself.

I think I need to just delete this corrupted folder/file, but I just don't know how to.

In the previous StackExchange post mentioned above, someone suggested using fsck. It looks like fsck finds no problems. I hope I did it correctly; here is the output:

~ $ sudo umount /dev/sdc1
~ $ sudo /sbin/fsck /dev/sdc1
fsck from util-linux 2.29.2
exfatfsck 1.2.5
Checking file system on /dev/sdc1.
File system version 1.0
Sector size 512 bytes
Cluster size 128 KB
Volume size 59 GB
Used space 30 GB
Available space 30 GB
Totally 504 directories and 3888 files.
File system checking finished. No errors found.

Another suggestion on that other post was to run on a Windows machine. I haven't tried that yet, but will try that tomorrow when I have access to one.