I tried to replicate your problem with my own ntfs partition, in fact i too didnt had the write permissions on the ntfs partition,
The answer to why you are not able to mount the ntfs parition with write permissions lies in the FUSE library.
In the screenshot which you have pasted, it says you are trying to mount a ntfs block device using FUSE library.
First check if you have fuse-utils package installed on your system, if not install the fuse-utils package using apt-get
Then, remove the following lines from your /etc/fstab
/dev/sda2 /media/myMountPoint ntfs-3g quiet,defaults,rw 0 0
Now, we need to mount the ntfs block partition using fusermount command
Now, open the /etc/mtab with root priviliges, and add the following line
/dev/sda3 /media/D fuseblk rw,nosuid,nodev,allow_other,blksize=4096,default_permissions 0 0
replace with your partition and mount point and reboot the system.
Sorry for putting this in separate answer, i could not write all this as a comment. After the reboot, when i mounted my mountpoint, i was having write permissions, tell me if it works for you too.
This is more of an issue with exFAT, not FAT.
exFAT is the Microsoft-owned proprietary filesystem that Android (and any other device) need to license from Microsoft in order to support.
FAT (eg FAT32 + VFAT) is free to implement and implemented pretty much universally, including in Ubuntu.
One of the notable benefits of exFAT over FAT is its support for individual files larger than 4GB, an essential feature for video recording applications.
The most notable drawback, obviously, is its proprietary nature, giving a Microsoft tax to every device that implements the standard. It is an essential part of the SDXC standard, meaning that devices that support SD cards over 32GB have to pay money to Microsoft.
Edit: after reading the actual article, I realise now that the article itself suggests that vendors are paying to use even FAT (not exFAT). Sorry for assuming that was your own confusion.
However, the point muru made in his answer still stands: the free software implementations of FAT (including the implementation in Linux, the kernel used in Android) are not subject to Microsoft patents because they don't implement the patented algorithm for maintaining long filenames and 8/3 letter filenames side by side.
The article even admits it can only speculate, and I think it's probably wrong, for the above reasons. Or, at least, perhaps it does not have the full story: it's possible that these vendors are licensing other technology from Microsoft and the contract they have with Microsoft just happens to also bundle in some FAT technology even though they don't need a license for this.
Best Answer
No worries Ubuntu did not damage your USB drive. But we do not use poorly documented bit flags of a FAT32, FAT16, or NTFS filesystem. On Windows these flags indicate a possibly corrupted filesystem when we had not properly unmounted the drive or an I/O error had occured.
Those bits are located in a reserved entry of a FAT partition table. According to an internal Microsoft paper of 2004 the purpose of these bits are:
There was some discussion with the kernel file system developers some years ago on how to overcome this but I was unable to follow up the results. Apparently it did not make it into recent kernels.
As only a bit flag is involved but generally our data should be in perfect shape we can ignore the warning Windows issues on those drives we had previously used in Ubuntu.