March 25, 201214 yr Hi there, maybe someone knows the problem, i just cant mount any AFP Timemachine shares anymore. My Mac only tells me that the connection failed and the Failure console shows something like this: AFP_VFS afpfs_MountAFPVolume: GetVolParms failed 0x39 while the unRaid server spits out some messages like this: Mar 25 21:15:48 HTMS afpd[3499]: Duplicate volume name, check AppleVolumes files: previous: "TM-backup", new: "TM-backup" Mar 25 21:15:48 HTMS afpd[3878]: dsi_stream_read: len:0, unexpected EOF Mar 25 21:15:48 HTMS afpd[2398]: dsi_stream_read: len:0, unexpected EOF Mar 25 21:15:48 HTMS afpd[3499]: dsi_stream_read: len:0, unexpected EOF Using the normal AFP share (without Timemachine AddOn works). Restarting the Server or the Mac didnt change anything. I think maybe netatalk needs an Update. Unraid 5.0 beta14 has version 2.2.1 on it and version 2.2.2 is around since January.
October 27, 201312 yr I have this problem, too. My theory is that the timeout setting is wrong. This is based upon what I observe on my Mac: When I watch TimeMachine on the Mac, it begins processing locally. TM checks to see if the server is 'online'. Then the TM icon spins...and the 'list' of stuff to be updated is generated...and then TM goes to 'write' to the server. However, the drives aren't spun up yet, and I get the stream_read error My work around is: 1. whenever I restart the mac: 2. click on 'Tower' in a finder window and navigate to the time machine share 3. wait for the timemachine sparse disk image bundle required for my mac to appear in the file listing...(waiting for the file to appear, seems to be the key element...once it becomes 'known' then the problem stops.) 4. close the finder window. This only seems to be done once per restart per mac. There's a script in another forum posting that automates all of the above at startup/login. However, the discussion suggests that it is no longer reliable with Maverick.
Archived
This topic is now archived and is closed to further replies.