T29: SL "an unexpected error occurred" with .pkg files

[ducksoft]

After updating to 4.1.7-T29 I reset to Factory Default, added a couple of test users and test shares, and started to copy data back to the NAS. I hit two .pkg files (one from Adobe, one from Edirol, there maybe others) that produce the error message:

"The operation can't be completed because an unexpected error occurred (error code -50)"

I tried a few combinations of the Advanced AFP Permission settings for the share (ie disabled the feature, set Group rights and Everyone rights to Disabled, etc) but consistently get the same err msg.

I've seen this issue reported before - was it addressed in 4.1.7-T29 ? Note this is NOT an Aperture or iPhoto library.

Regards

Tim

[sphardy]

@Ducksoft - a few questions:

How/where did you back these up packages?
How are you trying to copy the data back to your NAS?
If you are able, can you look inside one of the packages and see if these are any folders that begin with '.Apple'?

[ducksoft]

How/where did you back these up packages?

The files were originally downloaded, then have been copied back and forth between ReadyNAS and an internal Mac HDD.

How are you trying to copy the data back to your NAS?

Drag and drop between two Finder windows.

If you are able, can you look inside one of the packages and see if these are any folders that begin with '.Apple'?

Using Finder to Show Package Contents, then File | Find, "File visibility" = Invisible, I see many .AppleDouble folders.

Regards

Tim

[sphardy]

Using Finder to Show Package Contents, then File | Find, "File visibility" = Invisible, I see many .AppleDouble folders.

I believe this is the root of the problem - any file which begins '.Apple'is a reserved name and so cannot be copied back to the NAS. I don't have a solution - am still looking. But you have confirmed that this scenario occurs with more applications than just iPhoto.

I'll post back if I figure any way forward - but maybe Netgear will come up with something

EDIT: One thought - as this is caused by AFP access to the NAS, maybe copying the packages back via CIFs will workaround the issue

EDIT2: From what I can see, this creation of .AppleDouble folders by some applications is a 'feature' of those applications so that networks shares can be supported. Other than to use an non-AFP protocol to copy back the packages, the only other documented 'solution' I can find is to delete these folders from the package - not something everyone will be comfortable with.

I've tried searching for a netatalk forum to post some questions, but there doesn't appear to be an active forum available. Also I'm having difficulty accessing the mailing lists advertised on the netatalk site.

I'd like to request that netgear investigate this and post recommendations of how to overcome the issue. It appears to be caused by applications not expecting to access network shares over AFP (I'm sure Mac OS X server deals with this somehow) conflicting with netatalk with both creating files with the same name. As such I don't think the netatalk team would consider this a bug, but there has to be a workaround where transfer over AFP is possible without havign to manually delete files in the original package.

[Chewbacca]

Anyone have a link to a pkg file we can look into?

I checked adobe and edirol's site but couldnt find any.

Thanks

[sphardy]

Not really - my libraries are many GB and reference GB's of photos on my NAS

I just tried to create a small test library in iPhoto to try to give you something - but found no .AppleDouble folders. Looking through my problem libraries I've now noticed that only photos imported up until aroudn November 2008 seem to have these .AppleDouble folders, which would probably co-incide with an upgrade to iPhoto '09 (believe I upgraded in January '09, probably importing photos from December 2008)

I have read that Apple is moving away from this technique of resource forks in separate files - seems they may have done that with iLife '09

[ducksoft]

I've copied my entire "install" share (where I keep installation images / packages for various OS) from the backup HDD to the NAS and found 31 files that refused to copy with the same error message. On checking a random 5 or 10 using the Show Package Contents technique I found that they contained the .AppleDouble folder. Some files I downloaded again from suppliers and as they did not contain .AppleDouble folder I guess these folders were added to the package during the past 9 months as I moved files back and forth between NAS and backup HDD whilst try to survive the ReadyNAS/SL compatibility issues.

I choose not to circumvent AFP protocol by using CIFS to transfer them. I hope NetGear will fix this just like its possible to copy the packages with .AppleDouble folders amongst for example main HDD and backup HDD without the err msg.

Regards

Tim

[Chewbacca]

ducksoft: Any way you can get me a link to where you downloaded one of those pkg files or you can send me one that you are having a issue with?

[ducksoft]

"Rrrrrrromph!" : It seems to be triggered by just having a .AppleDouble folder in the pkg. Can you just create one yourself and give it a try?

After going back to manufacturers site and downloading again, the .pkg files did not contain the .AppleDouble folders so I strongly suspect they were created whilst copying the .pkg files back and forth with a prior version ReadyNAS firmware interacting with AFP protocol.

Regards

Tim

[idm]

Is it possible that the pkg was copied to the NAS via AFP/netatalk (creating .AppleDouble folder/s), backed up to external USB (apparently just a wrapper for cp) and then the USB was plugged into a Mac and the file copied back to the Mac (*without* AFP, but with all the .AppleDouble folders)?

Another variation might involve copying the pkg to the NAS via AFP and then using rsync to copy it back to a Mac.

I imagine this could also occur by copying the pkg to NAS via AFP and then using HTTP/s to copy it back to a Mac.

I suspect something similar could happen with CIFS/samba (with ._ files rather than .AppleDouble folders) but I don't use that services (to avoid exactly this problem of different services using different mechanisms to store resource forks).

I've also found that there are problems when files require the contents of the similarly named file in the .AppleDouble folder (aka resource fork), for example, certain kinds of img/dmg won't mount.

This can be solved by moving the file and folder back onto the NAS (via USB or rsync) and then accessing via AFP/netatalk. Or by only ever using AFP/netatalk to access it. Or by using utilities to reconstruct the complete file (though this is clunky and unreliable)

regards

Ian

[schalliol]

Since I was told I should factory default, I did and now I am having trouble copying my files back because of this -50 error. Based on above, is there any solution you're aware of that works well, and what was done? Thanks!

[devs]

I'm also having this issue guys and wondered if a solution was ever found?

Thanks.

[ducksoft]

I switched to using iSCSI and bought a Mac mini server to share out the filespace. The AFP protocol in my setup is therefore implemented by Apple. The NAS is only using iSCSI.

I got tired of the community supported AFP packages (used by NAS vendors) which seemed to have a hard time keeping up with Apple.

Tim