I do find /media/masi/FAT32/ -type f -name '._*' -deletebut I get find: cannot delete '/media/masi/FAT32/._booklet.pdf': Read-only file systemI do not know how to work with such situations when working in ext4 but searching fat32. There are no permissions/owners in fat32. So I would like to change that all read-write all files in the memory card. However, not sure if it can be done here. It can also be a file system consistency problem but not sure. I just noticed many .dotFiles in the system, which seems to be backup files because I did not use the option described here before. I do ls -la /media/masi/drwxr-xr-x 29 masi masi 32768 1 1970 FAT32I do mount -o remount, rw /media/masi/FAT32/ but I getmount: mount point /media/masi/FAT32/ does not occurCommand dmesg | grep FAT32 gives blank. Command lsblk also does not show the memory. Profiling the memory in Nautilus of Debian 8.25 where I see the main node correctly but subnodes not; in terminal, I can however search the tree but not sure how good it isSorry, could not display all the contents of handouts.noindex: Error  when getting information for file  '/media/masi/FAT32/handouts.noindex/Yp@3.': Input/output errorMemory: Transcend JetDrive Lite 130 128 GB (for Macbook Air 2013-mid)Hardware: Macbook Air 2013-mid and Dell PC i3 2013OS: Ubuntu 16.04 and Debian 8.5
How to Solve this Read-only file system error?
filesystems;find
The access to a VFAT partition often gets implicitly set to read-only when there are access/read errors. In order to check and solve these try the following steps. Be aware to use the right device, else you can damage your system!Try to save valuable data from the drive by copying it to some other drive or your home directory.Unmount the drive.Check for problems with sudo fsck.vfat /dev/...If fsck reports errors, try to repair them: sudo fsck.vfat -a /dev/....For more thorough checks see also the -t and -V options, as well as -f to try saving the content of damaged files.After fsck has finished you can remove and reconnect the drive and try again to access it.If that doesn't help, try to format the drive: sudo mkfs.vfat /dev/....If that still doesn't help, or the problem reoccurs, the drive may be damaged badly and should be discarded.