Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pillage]

Hello all,

I have a problem that just started recently. 2 weeks ago I was able to transfer files (jpgs and videos) from my MacBook Pro running 10.5.8 to the DNS-321. In the past, if a transfer stalls, a reboot of the NAS and reconnecting would fix it. Since last week, I have not been able to transfer files to the NAS regardless. When I start a copy, it would look like the copy would start but I would not see a progress bar. Finder would start locking up after a few minutes and my Mac would be generally unresponsive until I shut down the NAS. Then I can access my Mac again. If I try to disconnect/unmount the drive, I'll get a message that the drive is in use.

I access the NAS either via smb://IP/host or through Finder > Network. Both cause failures when transferring files (I've tried different types and sizes).  I've also tried the following methods to transfer the files: dragging and dropping, copying and pasting, cp and mv in command line. Each time this would cause the Mac to be unresponsive in Finder or Terminal. When I shut down the NAS, both Finder and Terminal start responding after a brief period. Upon reconnecting to the NAS, I will see the name of the file/s with zero data in it. There have been no problems copying from the NAS to the Mac.

I have tried copying files from a Windows 7 VM on the Mac, but this has not worked either. I am starting to think it's the Mac but cannot be certain. If anyone has encountered this problem, what did you do to resolve it? I've Googled this for days and have not found anything definitive.

Thanks for any thoughts.
- Charles

[pillage]

I think I got the problem solved. There was a stale Volume_1 mount that did not show up using the mount command. All subsequent mounts of Volume_1 from the NAS was actually mounted as Volume_1-1 but showed incorrectly in Finder as Volume_1. I had to go to the /Volumes directory to see the stale mount. After deleting the stale Volume_1, then reconnecting to the NAS, files copied over without a problem. Wish I found this sooner. After struggling with this for almost 2 weeks, I ordered a Synology NAS thinking the Mac just did not like playing with the DNS-321.

[sku]

I think I'm having the same issue. Could you please tell me how to access the /volumes directory on the Mac? Thanks.

[pillage]

Actually, this problem has not gone away. It looked like it was resolved when I removed the stale mount, but after that, I couldn't copy again the next day. I think it may have to do with the version of OS X. On my wife's Snow Leopard laptop (10.6.?), I never have any problems mounting the NAS and copying to it. It's only on my MBP running 10.5.8 that this is a really frustrating issue. Sorry for not posting a follow up. I'm thinking of upgrading my laptop to 10.6.x to fix this issue. It also just works on another Windows 7 system I just acquired. But right now, I'm just going to set up the Synology NAS I ordered when this issue started and use the DNS-321 as a backup.

[dkarim]

sku, to access the Volumes directory just open a terminal window and type in:
cd /Volumes

If you see more than just Volume_1, you could try unmounting the others by issuing a:
umount Volume_1-1

If it doesn't let you, you might have to login as superuser; the command is su

[sku]

thank you, dkarim, for your response.

i was able to figure out what caused the permissions error, which is probably of a different nature than that posted by pillage. prior to getting the error, i had reset all user accounts on the NAS, and doing so supposedly allowed any user to read/write to the NAS. but after i did that, i simply couldn't copy anything to most folders (yes, strangely, a couple of folders didn't have this problem). in the end, i decided to just re-create my former user account, and voila, i was able to copy files to the NAS again as well as delete files from it.

apparently, if you attempt to write to the NAS using a different user account, you'd get a permissions error, even if your new user account has read/write privileges. this is something d-link should look into and fix.