Benches macOS

5

Annoying Finder crash

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I am copying a music library from a NAS to my 24" iMac and after nearly an hour it crashed and tells me "The Finder can't complete the operation because some data in "" can't be read or written."

So what is the problem one asks? Is it something on the NAS or something on the iMac, and what was the copy copying when it crashed? I have the dump report but I cannot see where that tells me what file it was having a problem with. It says

"Exception Type: EXC
BADACCESS (SIGSEGV)

Exception Codes: KERN
INVALIDADDRESS at 0x0000000000000048

Crashed Thread: 9"

And tons more information. But nothing that actually TELLS me anything useful. It would have been VERY useful to tell me that last successfully copied file and path, but maybe it simply could not.

What is even more irritating is that another copy of similar size was going on at the same time, this one appeared to be still running but the error box had an OK button which I clicked and - boom - it terminated everything.

Sigh.

Do copies proceed sequentially? So if I search through both directories, the source and target, to find the place where a file exists on the NAS and not on the iMac, will that be a reliable indication of where the copy failed? Is there any way of comparing two file systems? Is there any way of copying and keeping an audit trail?

Any suggestions?

Thanks - Lawrence

5 replies

Sign in or join Beachball Help to reply.

  1. 0

    nate12345

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Would I be right in thinking that the NAS is formatted in FAT32?

    This is a FAT32 error; I don't know anything you can do about it.

    I've had better luck connecting directly to the NAS with USB/FW than over the network.

    Good luck!

    -Nate

  2. 0

    LawrenceHare

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    No, I used the Mac journaled file system when I configured it as I recall, certainly not FAT32. The thing is a Drobo attached to DroboShare. It is used by a bunch of clients, Windows, Mac and Linux. It is a pretty solid piece of hardware and I have never had any problem with it.

    Which is why I was surprised by this error. The music library is accessed by lots of systems, iPods and a SONOS system. None of them have reported any problems.

    I'll mess with it some more, I'm thinking something got out of hand and maybe it is not a file system error. I hope... Better not be!

    Thanks - Lawrence

  3. 0

    nate12345

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    How is it read by Linux and Windows if it's Mac OS Extended (Journaled)?

    I've seen this a lot with my FAT drives, but never on a different format.

    Good luck.

    I suppose you could always try a Disk Utility repair.

  4. 0

    LawrenceHare

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The network interface device, DroboShare, implements SMB for network access. Then at the backend DroboShare uses USB to access the RAID device (Drobo). The RAID device supports various file formats, HFS+ is what I think I set up with the idea I can take it off the network and plug it into my Mac. I use primarily Macs, but we have Windows and Linux machines including a SONOS sound system which is Linux based. I have never experienced a file copy problem and all devices seem to work just fine with the NAS.

    Disk Utility is a good idea, that should be able to crunch through the thing and tell me if it finds anything weird. If it cannot do it through the network then maybe, for the first time, I will try sticking it directly on my Mac.

    Thanks - Lawrence

  5. 0

    LawrenceHare

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I give up on this, don't know what is going on. Thanks for the replies though.

    Lawrence