Finder unable to copy files to external RAID array (Error code -36)

App & System Services Core OS
bertieb OP
Created Sep ’16
Replies 22
Boosts 0
Views 4.1k
Participants 6

My iMac recently updated to macOS Sierra 10.12.1 Beta (as I was participating in the beta program)

Unfortunately this appears to have firstly re-organised my iTunes library (all my Movie/TV files were moved into the Home Video folder)

My iTunes library is on an external Volume (LaCie 5Big RAID drive). At first in trying to re-build my iTunes library I discovered I was unable to add any content

Subsequently found that I was unable to add ANY Video content to my LaCie drive - received the dreaded -36 error message

e.g

The Finder can’t complete the operation because some data in “filename.mp4” can’t be read or written.

(Error code -36)

On further investigation it seems that I can’t copy .mp4, .m4v, .mov, .dmg, .mp3, .pkg, .pages, .keynote files...

However copying some other file types to the drive is OK (e.g can copy PDF files, txt…)

Also unable to launch/run video files (as they are copied into iTunes Media Folder - which is on external LaCie drive!)

"Attempting to copy to the disk “LaCie” failed. The disk could not be read from or written to."

(Removed the setting under iTunes Preferences - and can run, but leaves file where it is)


Did some digging around on and tried to clean this up using the dot_clean utility - unfortunately without any luck


Ran Disk Utility - My drive appears to be clean (Apple Disk Utility seems to have lost many of its features)


Ran LaCie Raid Manager - Integrity of the LaCie Volume looks fine - although the notifications are a month behind (see attached screenshot)

I am able to copy ALL files to the external drive using cp from within a terminal window.


I connected the LaCie 5Big drive to my MacBooK Pro (running El Capitan 11.11.6) - and everything appears to be fine - can copy Video files etc - so nothing wrong with the drive!


Have attached a LaCie 1TB ruggedised drive to my iMac and I can copy files to the drive without issue


So problem appears to be with LaCie 5Big RAID (20TB) drive and macOs Sierra 10.12.1 Beta


(updated this morning to the latest beta version and problem still there)


Anyone seen same issue or know how to fix this ?

Replies  22
Boosts  0
Views  4.1k
Participants  6
Firmaxi OP
Oct ’16

I have the very same issue with excatly the same problems and file extensions you have listed. I have

Mid 2013 Macbook Pro 15" Retina / Sierra 10.12.1 / Lacie 10TB 5Big.


I managed to copy significatn ammout of files to Lacie, except few m4m, mov, etc. video files. While trying to solve this issue, I removed all files from Lacie to format and re-initialized the drive. After this process drive couldn't take back even the files that were previously there.


It seems that probelm got worse with Lacie firmware uppdate 2.0.3.1057. Files that coped ok to drive were probaly with earlier / firmware that was supplied with the drive. I do uppdate OSX when new uppdates are available, so I am not 100% sure if some latest Sierra uppdate or Lacie firmware or both are the reason. You might want to contact Lacie support as well, this may not be fully "OSX" related issue as those changes in Firmware has possibly worsen the issue.

0
bertieb OP
Oct ’16

Thanks for the feedback


I had logged a support call with LaCie too - they came back and said that macOS 10.2.1 had not been tested/certified yet!


Checking the logs, On trying to copy a file on the LaCie 5 Big Array I get the following messages in the Console:


default 07:22:21.764404 +1000 DesktopServicesHelper Claim B91841B7-2842-4361-8A53-C1722AD1A24D invoked in client


default 07:22:21.887145 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887187 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887197 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887206 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887214 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887218 +1000 kernel disk3s2: I/O error.



On searching through the system (for mvumi) I find this


82058] backup com.lacie operation: Execute


[82058] \t- arguments: installer, -verboseR, -pkg, /Applications/LaCie RAID Manager/LaCie RAID Manager.app/Contents/MacOS/LaCieMvumi.pkg, -target, /, UNDOEXECUTE, /Applications/LaCie RAID Manager/LaCie RAID Manager.app/Contents/MacOS/rmpkg.sh, -v, -f, /Applications/LaCie RAID Manager/LaCie RAID Manager.app/Contents/MacOS/LaCieMvumi.pkg

[82058] Done

[82058] perform com.lacie operation: Execute

[82058] \t- arguments: installer, -verboseR, -pkg, /Applications/LaCie RAID Manager/LaCie RAID Manager.app/Contents/MacOS/LaCieMvumi.pkg, -target, /, UNDOEXECUTE, /Applications/LaCie RAID Manager/LaCie RAID Manager.app/Contents/MacOS/rmpkg.sh, -v, -f, /Applications/LaCie RAID Manager/LaCie RAID Manager.app/Contents/MacOS/LaCieMvumi.pkg

[82070] installer" started, arguments: "-verboseR -pkg /Applications/LaCie RAID Manager/LaCie RAID Manager.app/Contents/MacOS/LaCieMvumi.pkg -target /

[83504] installer: Package name is LaCie Storage Controller driver\ninstaller: Upgrading at base path /\ninstaller:PHASE:Preparing for installation\xE2\x80\xA6\n

[83539] installer:PHASE:Preparing the disk\xE2\x80\xA6\n

[83554] installer:PHASE:Preparing LaCie Storage Controller driver\xE2\x80\xA6\n

Also read that in macOS Sierra they have changed the permissions on /Volumes - so wondering what mvumi.cpp is trying to do ?

Cheers

1
bertieb OP
Oct ’16

Thanks for the feedback

I had logged a support call with LaCie too - they came back and said that macOS 10.2.1 had not been tested/certified yet!


Checking the logs, On trying to copy a file on the LaCie 5 Big Array I get the following messages in the Console:


default 07:22:21.764404 +1000 DesktopServicesHelper Claim B91841B7-2842-4361-8A53-C1722AD1A24D invoked in client


default 07:22:21.887145 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887187 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887197 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887206 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887214 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887218 +1000 kernel disk3s2: I/O error.


(which on searching through the system is related to the LaCieMvumi.pkg)


Also read that in macOS Sierra they have changed the permissions on /Volumes - so wondering what mvumi.cpp is trying to do ?

Cheers

0
bertieb OP
Oct ’16

Anyone explain why my responses are being moderated ?

0
cheltenham OP
Oct ’16

After updating macOS Sierra 12.1 beta, I encountered same problem on LaCie 5Big Thunderbolt 2 and LaCie 2Big Thunderbolt.

I updated raid manager, but this probloem was not solved.

I could not find any solutions, so I reinstall Sierra 12 again, and recover data from Time Machine.

0
bertieb OP
Oct ’16

For some reasons replies have been moderated - not sure why?


Looks to be a problem with LaCie Drivers and macOS Sierra changing he permissions on /Volumes


When I attempt to copy files get in console:


default 07:22:21.887214 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887218 +1000 kernel disk3s2: I/O error.


/Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp is a LaCie driver - not saure what it is doing...

0
bertieb OP
Oct ’16

Recently upgraded to macOS 10.12.1 Public Beta 3 - same results


As mentioned already (although my replies for some reason are being moderated!)


Checking the logs, when trying to copy a file on the LaCie 5 Big Array I get the following messages in the Console:


default 07:22:21.764404 +1000 DesktopServicesHelper Claim B91841B7-2842-4361-8A53-C1722AD1A24D invoked in client


default 07:22:21.887145 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887187 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887197 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887206 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887214 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887218 +1000 kernel disk3s2: I/O error.


(which on searching through the system is related to the LaCieMvumi.pkg)


Also read that in macOS Sierra they have changed the permissions on /Volumes - so wondering what mvumi.cpp is trying to do ?


Something to do with this temporary mount ?


/Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp

0
Dmitry Tockman OP
Oct ’16

I have the same situation with 10.12.1 Beta (1 & 2) and LaCie 5big Thunderbolt2, and the same infamous -36 error in Finder. In addition to Bert told, music and video files I try to play from LaCie sound/look stuttering and sometimes like they are just empty. When have been copied to the Desktop same files play smoothly.

I described it in my macOS beta report.

0
Firmaxi OP
Oct ’16

We tested 5 Big with El Capitan without any problems, so for sure it starts to look that Lacie is a problem.


Wonder if abyone have tested with plain 12.1 alone?

We got this genius "are cables connected" and "Is power ON" -support from Lacie. They said that it is about Mac OSX. It is not that Apple is declaring that Sierra is 5Big compatible, but Lacie is declaring that that their drives are Sierra compatible.

0
Dmitry Tockman OP
Oct ’16

As far as I remember it was alright on all 10.12 betas until the final. The problems began exactly on 10.12.1 so both changes in Sierra's FS or obsolete kext in LaCie driver might be a reason.

0
Firmaxi OP
Oct ’16

Any ideas how to rollback to 12.1 ?

I noticed that things got actually worse after uppdating Lacie firmware to latest.

0
Dmitry Tockman OP
Oct ’16

Time Machine?

0
bertieb OP
Oct ’16

Yes I have had the problem with 10.12.1 Beta (1, 2 and 3). Believe it worked with non-beta version of Sierra. System upgraded to beta version as I still had beta profile installed


I had replied previously but for some reason my responses are being moderated or rejected ... ?

0
mkummer OP
Oct ’16

I have experienced a very similar issues and reported it via Apple's Feedback assistant and i have an open case pending with LaCie. After the upgrade to 10.12.1 all write access to my LaCie failed but read access continues to work. I have documented the details on my blog: http://www.michaelkummer.com/2016/09/29/macos-10-12-1-beta-incompatible-with-lacie-kernel-extension/ Cheers Michael

0
bertieb OP
Oct ’16

Thanks for the reply - Reassuring to see that I am not the only person with this problem!


When I try and move a file with Finder I see this message in the Console


...

default 07:22:21.887214 +1000 kernel assertion: /Volumes/share/Hayden_tmp/mac/trunk/mvumi/mvumi.cpp,885

default 07:22:21.887218 +1000 kernel disk3s2: I/O error.


Suspect it may be related to this issue others are seeing:


https://forums.developer.apple.com/message/169554


Another link discussing the Permissions problem


https://derflounder.wordpress.com/2016/09/21/macos-sierras-volumes-folder-is-no-longer-world-writable/


I had the same problem with Photos library being corrupted too - fortunately I had a copy and able to open on Macbook running El Capitan

0
Finder unable to copy files to external RAID array (Error code -36)
First post date Last post date
 
 
Q