#MUCOMMANDER OPEN WITH LINUX MAC OS#
#MUCOMMANDER OPEN WITH LINUX SOFTWARE#
#MUCOMMANDER OPEN WITH LINUX MAC#

After removing this attribute the drive custom icon disappears and reverts to the standard yellow icon. After aligning permissions on the drive between the ones I could access and the one I could not, I narrowed this down to the only difference being the extended attribute, confirmed by running ls on the /Volumes path. For example most LaCie drives come with a nice custom icon instead of the default external drive icon and I was unable to access this drive over the network, however all other drives were perfectly accessible. Noticed an interesting problem after a few days whereby when File Sharing is enabled and you try and access a hard drive on the server that has an extended attribute on it, specifically which seems to be placed when a drive has a custom icon on it, either finder on the client machine will hang and crash, and/or samba on the server will hang and crash entirely.

#MUCOMMANDER OPEN WITH LINUX MAC#

Ventura finder crashes when opening share that has extended attribute Recently updated my MPB and Mac mini used as a home server to Ventura. Please allow us to turn on or off autosave.

So now I have to duplicate to local drive then copy back to server. 'ask to keep changes when closing documents' is not a fix. (I seriously detest auto save in specific instances like when quickly raiding a file for content). Open the duplicate copy of that file in this location from the NAS on the M1 mini – boom errors.Ĭan't even turn off auto save to fix the error. Opened a pages file yesterday on older iMac machine running os from 3 or 4 versions back on another synchronised NAS, no problem. Saving it onto a local drive (M1 mini Big Sur) the file works fine. The numbers file was opened from a template file and saved onto the Nas. Im working at three in the morning alone. The file has been changed by another application. The document “insert document name.pages” could not be autosaved. Apple Pages and Numbers both throwing these persistent errors. This suggests the issue could be with macOS, though I can't rule out issues with the NAS's OS.ĭocument could not be autosaved (Synology NAS / SMB Mounted Volume) Driving me bats. I have no problems connecting to the NAS (and staying connected) through a web brower on the Mac, or through Synology's iOS apps DS Audio and DS File running in the latest iOS 13 on a 2017 iPad Pro. If I re-connect to those folders via the Finder ('Connect to Server'), the triangle remains.Īfter disabling AFP on the NAS, I removed the folders from the login items and added them back, just in case the connection method matters. In my Login Items, I've added two folders from the NAS drive, which appear as separate volumes.Īt some point, the Mac loses track of them, and a yellow triangle appears next to them in the Login Items list.

It just happened again as I've been writing this. I switched from AFP to SMB for connecting (disabling AFP on the NAS and clearing recent servers from the 'Connect to Server' window in the mac Finder).Īt first that seemed to resolve the problem, but it continues. The last several days, the Mac has frequently disconnected from the NAS, automatically ejecting it from the Finder for no apparent reason. Problems connecting iMac to Synology NAS I have a Synology DS218+ and an iMac, both connected to a Netgear passive Ethernet switch. Has anyone seen anything like this before? I don't recall seeing this problem before upgrading the MacBook Air to Monterey. Rsync copies the file correctly to the USB SSD Drive, so I think it's the Finder drag and drop that's causing the problem.

#MUCOMMANDER OPEN WITH LINUX SOFTWARE#

I don't think the old software version on the server is a factor as the same corruption happens copying the file to a local USB SSD disk. The server is an older Mac Mini running Catalina 10.15.7.

#MUCOMMANDER OPEN WITH LINUX MAC OS#

The source computer is an Intel MacBook Air running the most recent Mac OS Monterey 12.3.1. Initially I thought it might be a problem with my wireless network, but what is really weird is that when I copy the same file from the MacBook Air to a locally attached USB SSD drive then it is corrupted in the exact same way - the MD5 for the corrupted file on the SSD is the same value as the corrupted file on my server. If I generate an MD5 hash then I can check the copied file against the original, which in this case shows that the source and target files are clearly different. When I compared the local files with their copies on the server, whole sections of data had been replaced with #00 characters. I only noticed this after seeing video glitches when I went to play the files back on my TV. I have a really odd problem where files are being corrupted when I use Finder to copy them from my MacBook Air to my Mac Mini server.

Mucommander open with linux