Cannot copy/quickview files/photos in CF cards

Question

I use Canon EOS 7D with a Sandisk 32G CF card (60MB/s) for my photography. I remembered Mountain Lion was able to copy all of my photos from the CF card, but Marvericks won't do that: It simply ejects the CF card automatically and copies nothing! The following dialog shows up after it fails.
I'm sure the CF card is in good condition because (1) I've erased the CF card using Disk Utility & the camera's formatting menu many many times; (2) I can use my PC (Win7 OS) to copy them, but I don't want to switch back and forth from Mac to Win7; (3) My cable and card reader works well.
I DO NEED SOMEONE TO LOOK INTO THIS PROBLEM!!!
Here is some logs from the system. (OS X version: 10.9.2)
May  3 02:30:00 tonys-MacBook-Pro.local fseventsd[67]: check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x102b6d3d8)
May  3 02:30:00 tonys-MacBook-Pro.local fseventsd[67]: log dir: /Volumes/UNTITLED/.fseventsd getting new uuid: A74AB496-FDC1-40EE-9273-70A4DBBA21D1
May  3 02:30:08 tonys-MacBook-Pro.local filecoordinationd[199]: NSFileCoordinator received a message and couldn't parse it. Details: <dictionary: 0x7fc9b3417740> { count = 2, contents =
                    "parameters" => <dictionary: 0x7fc9b341c290> { count = 0, contents =
                    "kind" => <string: 0x7fc9b3417810> { length = 15, contents = "providerCheckin" }
May  3 02:30:08 tonys-MacBook-Pro.local Finder[229]: NSFileCoordinator: Sending of a providerCheckin message was interrupted. Details: Connection interrupted
May  3 02:30:15 tonys-MacBook-Pro kernel[0]: disk1s1: media is not present.
May  3 02:30:15 --- last message repeated 7 times ---
May  3 02:30:15 tonys-MacBook-Pro kernel[0]: disk1s1: I/O error.
May  3 02:30:15 tonys-MacBook-Pro kernel[0]: disk1s1: media is not present.
May  3 02:30:15 --- last message repeated 10 times ---
May  3 02:30:15 tonys-MacBook-Pro kernel[0]: msdosfs_fat_uninit_vol: error 6 from msdosfs_fat_cache_flush
May  3 02:30:15 tonys-MacBook-Pro.local fseventsd[67]: disk logger: failed to open output file /Volumes/UNTITLED/.fseventsd/000000000657e30c (No such file or directory). mount point /Volumes/UNTITLED/.fseventsd
May  3 02:30:15 --- last message repeated 1 time ---
May  3 02:30:15 tonys-MacBook-Pro.local fseventsd[67]: failed to unlink old log file /Volumes/UNTITLED/.fseventsd/000000000657e30c (No such file or directory)
May  3 02:30:15 --- last message repeated 1 time ---
May  3 02:30:15 tonys-MacBook-Pro.local fseventsd[67]: unmounting: failed to remove log dir /Volumes/UNTITLED/.fseventsd (No such file or directory)
May  3 02:30:17 tonys-MacBook-Pro.local sandboxd[117] ([856]): mdworker(856) deny file-read-xattr /Users/tony/Desktop/UNTITLED (pre-plugin fstype:hfs fsflag:480D000 flags:250000005E diag:0 isXCode:0 uti:public.folder plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 221531360)
May  3 02:30:23 tonys-MacBook-Pro.local fseventsd[67]: check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x102b6d3d8)
May  3 02:30:23 tonys-MacBook-Pro.local fseventsd[67]: log dir: /Volumes/UNTITLED/.fseventsd getting new uuid: BB6337BB-85AA-49FA-8006-4833349790D2

Answer 1

My initial thought is that error -36 is a general "I/O error".  For drives that is usually due to one or more bad blocks on the disk.  It's only a problem if you attempt to access those bad blocks.  If they aren't accessed the disk behaves normally, i.e, you can read/write everything except the data in those bad blocks.  Of course it is an indication that the disk really needs to be replaced.
So my thought is that those cards you are using are behaving the same way.  You can access all the stuff except what's on the bad blocks.  This is what you did by selectively copying the stuff off the card.  It's good that you were able to salvage as much as you could off it.  Like a hard drive, it means it's time to replace that card.
That's my theory anyway.