Member Avatar for welsbywrites

Greetings!
New machine, updated to 10.5.5. I've bought LaCie Ethernet disk mini - 1Tb drive w 10/100/Gbit and USB - which is plugged in to my 10/100 network so that I can share it between 2-3 Macs. A friend has this drive which works well on similar small network, so I thought it was a good bet.

LaCie IPConfigurator used DHCP to assign IP address and then took me to drive "front end" (browser based) to create shares, user etc. Shares set up as All types, ie Windows / Apple / HTTP / FTP. I'm no expert, so thought All the best choice. Everything shows OK in the status page, so Logout.

Restart, and use Finder/Go/Connect to Server, which shows up afp://192.168.07. But when I try to collect that, I get a message: "The Finder cannot complete the operation because some data in afp://192.168.07 could not be read or written. (Error code -36).

Tried 2-3 times to connect, no joy. Ran configurator again, deleted shares and user, created new, still no good. GO sees the IP address, but then gives same error message.

HELP! I need to put 300G of photos and artwork on the drive for a big project, so it is all accessible in one place.

TIA

Ken

  • 4 Contributors
  • 5 Replies
  • 357 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by redage

Dani AI

Generated

A short, practical summary and next steps based on the thread: reports a LaCie Ethernet NAS that the Mac can see on the LAN but which fails during Finder transfers (the Finder reports an I/O/copy error). , and have already flagged useful leads (IP formatting, trying SMB, and checking share/protocol settings). The fastest way to isolate the problem is to determine whether the issue is the network, the NAS firmware/permissions, or the drive format itself — and to back up before any destructive step.

First tests (non-destructive)

  • Attach the LaCie directly by USB to a Mac and copy a handful of files. If the same failures appear, treat it as a drive/format problem. Run Disk Utility Verify/Repair on the disk and copy again.
  • If the USB copy works, the problem is network/protocol: test mounting via AFP and SMB separately, and use a small batch of files to reproduce the error.

Practical fixes that often work

  • If the NAS is formatted for broad compatibility (FAT32/Windows), reformat to Mac OS Extended (HFS+) if it will be Mac-only — this preserves resource forks and avoids many Finder I/O errors. Backup first: reformatting erases data.
  • Use a Terminal copy tool which handles forks/attributes more robustly than Finder. Examples:
    ditto -v /path/to/source /Volumes/Target/
rsync -avP /path/to/source/ /Volumes/Target/

    These commands often succeed where Finder fails and help narrow whether Finder or the filesystem is at fault.

Network, permissions and firmware

  • Verify the NAS firmware and update it if an update is available. Check the LaCie admin for whether AFP is actually enabled (try forcing AFP-only for testing), and use a DHCP reservation or a static IP so mounts remain stable (as suggested). Check share/user permissions and look at the NAS logs if available. If problems persist after these checks, archive the folder into a single image (DMG or ZIP) and copy that as a workaround, then contact LaCie support with exact firmware, share settings and a short reproduction log.

Recommended Answers

All 5 Replies

Member Avatar for John A

Did you mean 192.168.0.7? Because 192.168.07 is not a valid IP address.

Member Avatar for Member #443652

Instead of using afp:// try smb:// since you said you have it setup for both windows and OSX sharing.

Or you can also try going to the Go menu in finder and then choose network and it should query the network for devices and if it detects the share you can just click on it from there.

Also as a side note you may want to consider setting a static ip address because it will just keep changing over time and you will have to hunt down what ip it is using each time you want to access it.

Member Avatar for welsbywrites

Sorry for the confusion, the IP address is of course 192.168.0.7.

Now, with a bit of fiddling, I can see the drive as an smb share, but not afp. And I can open it in a window.

However, I tried to load it with one of the directories intended to be store there. All went well at first, the usual progress... message. Then once again, the dreaded "some data cannot be read or written (Error -36) message. And the first few images moved over have disappeared.

I don't know what is going on. I don't even NEED to know how it works or doesn't as long as I can get it working so that I have a single, networked repository for all the pix, copy and data that I need!

TIA

Info awaited from LaCie....

Ken

Member Avatar for Member #443652

Are you using only macs? because the problem may lie in the way the drive is formatted. Since you have it setup for multi OS support it is more than likely formatted as FAT32. Try setting up the drive as OSX only and see if that helps. After the change you should be able to access it using afp://.

Member Avatar for redage

In Directory Access/ Active Directory there is a choice, to choose between afp/smb !!!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.