I've seen this myself before. I've never gotten around to fixing it though since I've not used my Pogoplug in a while...
Categories: Remote Access Software (Mac)
Hello,
I have a problem with the Pogoplug software: When I try to copy files from my Mac via Drag&Drop to the installed Pogoplug attached HDD, I receive a Finder copy error number -36.
When I try to copy the same files to the WFS enabled connections (fads1acf47) destination folder, everything works fine without any problems.
I found out, that the -36 error not every time happens when I copy, and not ever with the same files. For example: 'text.txt', 'Bildschirmfoto_100_200_20100722.png' works fine; 'text.indd', 'text.ai' don't work.
My Pogoplug attached HDD is a Mac OS X 10.6 Extended Journaled HDD, I also tried the not journaled version with the same error -36 result.
The Pogoplug itself is a Seagate DockStar.
I hope someone can give me a hand with that strange problem...
Thanks in advance,
Jan
Having the same problem with 10.6.4 and extended journaled usb drive. Copies the same files fine through the pogo's web interface.
Just tried it on OS 10.6.2 and the finder copy using the drives mounted with the pogo app works flawlessly. SO- if your backups are crippled like mine, you can create a small partition on your boot drive (or boot from another drive) with 10.6.2 installed and then do your copy/backup. Yes, inconvenient, but a work-around nonetheless.
Update- Macbook Pro running 10.6.4 copies fine. So I moved the MacPro on 10.6.4 over to wifi and sure enough it copies just fine- without the error -36. Still haven't gotten the Mini mount the drives in the finder. :\
I'm also getting this Error code -36 when trying to copy files from Finder (Mac Pro w/OS 10.6.4) to the Pogoplug (Biz w/2.5.2 firmware + Pogoplug Drive 2.1.2). Uploading via web interface works fine but you cannot upload folders. Would be a nice feature to upload a ZIP file via web and have the 'option' of having Pogoplug unZIP the file automatically in the same directory after upload completes.
Here is the error given:
The Finder can't complete the operation because some data in "Folder Name" can't be read or written.
(Error code -36)
I have been trying a new version of the desktop client for a week or so.
It seems to have cleared up most issues.
Threlly said: I have been trying a new version of the desktop client for a week or so. It seems to have cleared up most issues.What is the new version you are running?
No, I got it in agreement with the dev team as I was helping them as best I could to try and resolve the -36 issue.
I don't want to post it without their agreement.
It might be worth a request to the dev team.
Wow, pretty big version bump from current 2.1.2. Any idea what other fixes/improvements are included?
The client interface is exactly the same as the current version, so I'm presuming any major changes are under the hood.
All I can say at this time is I am not experiencing any -36 errors.
It's 2.4.9.42
This is for the Drive application, right? Any ETA for this update?
Not that I'm aware of, I only received it as part of my efforts to help the team resolve the issue.
Like I said earlier, a mail to the dev team may be in order.
I just got a Pogoplug this week and am seeing the same problem often in Finder.
I suspect that it may be only files with extended attributes exhibited this problem for me. (It's those files where you'd see the at-sign (@) at the end of file permissions when you do an 'ls -l' command on a Mac OS X terminal.)
In Terminal, when I copy using 'cp' with the '-rX' option (to prevent copying extended attributes) I can get past this problem. e.g.
cp -rX -v Awesome.app /Volumes/MyPogoPlugHardDrive/mystuff/MyAwesomeApplications/
'xattr' can also be used to remove extended file permissions. However I found it tedious because I think it requires the name of the extended permission you want to remove.
I am having this problem (along with myriad others) and I am approaching the viewpoint that the Pogoplug is an unusable device.
I gave up on the Pogo software for the "myriad" of problems. It always seemed that once I finally got an issue fixed another would pop up, or it was constant disappearing of drives or contents of drives or not be able to access them if the internet was down. IF CE would have only included SMB... So I'm now running ARCH Linux with smb and haven't had a single issue. I'm no geek but was able to follow the very detailed and thorough guides to get it up and running on pink&gray.
http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray

RSS


