There is more problems.
The biggest is the one where the device expects certain FAT32 format with certain geometry and boot code.
It happens (very often) that this device is not readable by eCS, even DFSee will report i.e. geometry error.
If you "fix" it using DFSee and eCS is able to mount the drive, then it usually happens that due to changes the device itself is not able to mount (or see) the drive. I had this experience with Amazon Kindle 4.
So in my opinion the LVM + USB + FAT32 in eCS needs complete overhaul to see/mount even "strange" FAT32 formats on various external MSDs. Until then, eCS will never be fully usable for USB mass storages.
St.
Actually, this is not solely an eCS issue. This issue exists and persists in the Windows world as well. There are countless posts from people who have bought new SD cards for their phones, formatted them on a Windows machine, and watched (a) them be unusable on their phone or (b) experienced data loss or data corruption on their phones.
Now... for those who have formatted their cards on their phones, then inserted them into their Windows machine, they've noticed a variety of interesting issues as well. In my case, all sorts of corrupted files when I performed a simple copy. The only way that worked for me was to plug in my
entire phone, copy off the card to the Windows machine, install the new card in my phone, format the new card
in my phone using the phone's format utilities, and then copy to/through the phone to the SD card (ie: again, I could not copy directly to the card without causing corrupted data - or a situation where Windows "fixed" the card in a fashion where the phone now saw data corruption or could no longer use the card).
In all such cases, the only guaranteed method (and the
only method approved by many of the phone manufacturers) is to format the storage device in the device using it (in my example's case, the cell phone), connect the *entire* device to the computer via USB and do all transfers that way. Anything else risks (or nearly guarantees) data loss, data corruption or storage media that is no longer readable by the device (ie: cell phone, media player, etc).
The other issues? Yeah, the USB and MSD stuff does still need some work - but that's not related to this particular issue.