[SOLVED] Transferring files from Linux to Windows, flashdrive usually ends up being corrupted
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Transferring files from Linux to Windows, flashdrive usually ends up being corrupted
I'm just wondering why this might be happening. I was transferring files from a phone to Linux computer to flash drive to windows computer and usually the drive ends up being broken, having to be "repaired" in Windows and then the files I transferred don't work.
Why might that be happening?
I hit the eject button in my file manager, and the drive doesn't say any warnings and when I remove it I get an error message.
Any thoughts? I'm using Debian LXDE with pcmanfm for file manager.
One problem I've run across with some USB flash drives is that they don't necessarily tell you when they are busy.
I've had no trouble with those that have an activity light - you just have to wait until the light goes out to know you can remove it.
The filesystem used on the device makes a difference too - don't use NTFS or most of the linux native filesystems. Both of these keep state in memory for the purpose of maintaining throughput, but doing that also allows the activity light to go out. With the Linux native filesystems, a dismount will force the state to the device. Unfortunately, some devices will turn out the light when the transfer is finished, not when the device has finished re-writing changed blocks.
Unplugging at that time can cause corruption.
The advantage FAT/FAT32 has is that no state is maintained in memory, and if you wait a couple of seconds after closing the updates and the light goes out the device SHOULD be clean.
For those with no activity light... wait another 5-10 seconds and it should have finished the updates and any internal activity as well.
As always, be sure the device is dismounted before removing it.
Slightly off topic, maybe, but you're doing this in the most convoluted way possible. To transfer files from an Android phone to any computer, use Airdroid. It's in the Google Play Store, and you install it on your phone, run it, and it will give you a URL, something like 192.168.1.45:8888. Put that URL into the address window of your browser, any browser, on any OS, and it will connect to your phone. You can transfer files in either direction, plus do lots of other things with your phone. No need for wires, flash drives, or anything else. You do need them both connected to the same network, of course.
You didn't mention he Windows version or age of the Windows computer. Some
XP era computers, running XP, have SDcard drives that really don't work well, particularly for larger ( > 1GB for that era) cards.