rsync hanging while copying files to USB flash drive

[luggw1]

I'm attempting to backup my photos (and some other files) to a 64 GB flash drive that I can store off-site for safe keeping. I am using rsync -avS <source> <dest on USB drive> to write the files. I've done this successfully with other data to this same device, but the photos seem to be giving rsync trouble. It gets to the same point (same file) in the process each time and hangs. CTRL C successfully kills it. FWIW, it's writing the files from a FAT32 partition on the HDD to a FAT32 partition on the USB device, so I'm getting a "rsync: chgrp <filename> failed: Operation not permitted (1) for each file, but the files are being written successfully.

When I press CTRL C, I see the "rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632) [sender=3.1.1]" error and then it spits out a large collection of the aforementioned chgrp warnings. As far as I can tell, these are not for files that have already been written. Then at the end is another "rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.1]" error.

Also, I have an external HDD attached that I use for regular backups and I use exactly the same command to write exactly the same files to it (also to a FAT32 partition). It doesn't have any trouble with the process and runs through to completion. It's almost as if the USB stick is going to sleep in the middle of the process.

Can anyone provide me some insight on how to fix this problem?
Thanks.
Bill Lugg

[Qqmike]

Sorry, I've not used rsync. Maybe some tips in here to look at, like excluding that suspect file, permissions (e.g., change group? "rsync: chgrp <filename> failed"), or formatting:
http://ubuntuforums.org/showthread.php?t=2208374&page=2
May want to start at Page 1, but Code 20 popped up on Page 2.

Someone did say that

When I press CTRL C, I see the "rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632) [sender=3.1.1]" error

was caused by pressing Ctrl+C (and so is not critical, per se).

[luggw1]

Sorry, I've not used rsync. Maybe some tips in here to look at, like excluding that suspect file, permissions (e.g., change group? "rsync: chgrp <filename> failed"), or formatting:
http://ubuntuforums.org/showthread.php?t=2208374&page=2
May want to start at Page 1, but Code 20 popped up on Page 2.

Someone did say that

was caused by pressing Ctrl+C (and so is not critical, per se).

Pressing Ctrl+C isn't the issue, but another pointer in the link seems to have contained the solution to my problem. I noticed that one of the posters was using rsync and found that -rtui were sufficient options to do a similar backup. I tried that and got a successful run, no warnings and a clean log written.

Thanks for the link.
Bill Lugg

[Qqmike]

Glad you got it, luggw1, nice detective work. (Btw, I realize Ctrl+C wasn't the problem--it addressed only the 632 error, not the other things that were going on.)

Thanks for the feedback, other users here may encounter the same issue sometime as it seems many people are using rsync lately. If you want, you can mark your thread Solved (at the top of the page, near Post #1, on the right side, I think, there is Thread Tools--a drop-down list, where mark thread solved is listed).