The scenario:
I want my movies and music available to my Mac Mini for the following appications:
Air Video Server
Playback
Plex (Server Mode)
So I have the Mini and LS-V2.0TL connected to each other via a 100/1000 Netgear Switch to ensure maximum reliability. However, the LS-V2.0TL simply will not maintain a reliable SMB or AFP mount and OS X will not reliably recover from a disconnect without manually going back to the share via finder to browse the share.
Here are some logs...
SMB
------
2/26/11 11:13:36 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:13:37 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:13:40 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:13:40 PM kernel smb_iod_reconnect: Reconnected share SHARE with server ls-vlc8d
2/26/11 11:14:26 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:27 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:30 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:30 PM kernel smb_iod_reconnect: Reconnected share SHARE with server ls-vlc8d
2/26/11 11:14:39 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:41 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:43 PM KernelEventAgent[44] tid 00000000 received event(s) VQ_NOTRESP (1)
2/26/11 11:14:43 PM KernelEventAgent[44] tid 00000000 type 'smbfs', mounted on '/Volumes/share', from '//tripp@ls-vlc8d/share', not responding
2/26/11 11:14:43 PM KernelEventAgent[44] tid 00000000 found 1 filesystem(s) with problem(s)
2/26/11 11:14:43 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:47 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:53 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:58 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:14:58 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:14:59 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:00 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:01 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:02 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:03 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:03 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:15:04 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:05 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:06 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:07 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:08 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
2/26/11 11:15:12 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:13 PM KernelEventAgent[44] tid 00000000 received event(s) VQ_NOTRESP (1)
2/26/11 11:15:13 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[791] *** process 791 exceeded 500 log message per second limit - remaining messages this second discarded ***
2/26/11 11:15:13 PM kernel smb_iod_reconnect: Retrying connection to ls-vlc8d error = 61
AFP
-----
2/27/11 1:05:35 AM KernelEventAgent[47] tid 00000000 received event(s) VQ_NOTRESP (1)
2/27/11 1:05:35 AM KernelEventAgent[47] tid 00000000 type 'afpfs', mounted on '/Volumes/share', from 'afp_35BfB735BfB735BfB735BfB7-2.2d000004', not responding
2/27/11 1:05:35 AM KernelEventAgent[47] tid 00000000 found 1 filesystem(s) with problem(s)
2/27/11 1:05:35 AM kernel ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 1 on so 0x8a697f8
2/27/11 1:05:35 AM kernel AFP_VFS afpfs_DoReconnect started /Volumes/share prevTrigger 1 currTrigger 2
2/27/11 1:05:35 AM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/share
2/27/11 1:05:35 AM kernel AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/share
2/27/11 1:05:35 AM kernel AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/share
2/27/11 1:05:35 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:05:35 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:05:35 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
2/27/11 1:05:36 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:05:36 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:05:36 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
2/27/11 1:05:38 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:05:38 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:05:38 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
2/27/11 1:05:42 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:05:43 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:05:43 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
2/27/11 1:05:51 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:05:51 AM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 7 /Volumes/share
2/27/11 1:05:51 AM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/share
2/27/11 1:05:52 AM KernelEventAgent[47] tid 00000000 received event(s) VQ_NOTRESP (1)
2/27/11 1:05:52 AM kernel AFP_VFS afpfs_DoReconnect: Primary Reconnect failed 5 on /Volumes/share
2/27/11 1:05:52 AM kernel AFP_VFS afpfs_DoReconnect: trying Secondary Reconnect on /Volumes/share
2/27/11 1:05:53 AM kernel AFP_VFS afpfs_DoReconnect: get the reconnect token
2/27/11 1:08:53 AM kernel ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 2 on so 0x8a697f8
2/27/11 1:08:53 AM KernelEventAgent[47] tid 00000000 received event(s) VQ_NOTRESP (1)
2/27/11 1:08:53 AM KernelEventAgent[47] tid 00000000 type 'afpfs', mounted on '/Volumes/share', from 'afp_35BfB735BfB735BfB735BfB7-2.2d000004', not responding
2/27/11 1:08:53 AM KernelEventAgent[47] tid 00000000 found 1 filesystem(s) with problem(s)
2/27/11 1:08:54 AM kernel AFP_VFS afpfs_DoReconnect started /Volumes/share prevTrigger 2 currTrigger 3
2/27/11 1:08:54 AM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/share
2/27/11 1:08:54 AM kernel AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/share
2/27/11 1:08:54 AM kernel AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/share
2/27/11 1:08:54 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:08:54 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:08:54 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
2/27/11 1:08:55 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:08:55 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:08:55 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
2/27/11 1:08:57 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:08:57 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:08:57 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
2/27/11 1:09:01 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:09:01 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:09:01 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
2/27/11 1:09:09 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:09:09 AM kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 7 /Volumes/share
2/27/11 1:09:10 AM kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/share
2/27/11 1:09:10 AM KernelEventAgent[47] tid 00000000 received event(s) VQ_NOTRESP (1)
2/27/11 1:09:11 AM kernel AFP_VFS afpfs_DoReconnect: Primary Reconnect failed 5 on /Volumes/share
2/27/11 1:09:11 AM kernel AFP_VFS afpfs_DoReconnect: trying Secondary Reconnect on /Volumes/share
2/27/11 1:09:11 AM kernel AFP_VFS afpfs_DoReconnect: get the reconnect token
2/27/11 1:20:11 AM kernel ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 3 on so 0x8a697f8
2/27/11 1:20:11 AM KernelEventAgent[47] tid 00000000 received event(s) VQ_NOTRESP (1)
2/27/11 1:20:11 AM KernelEventAgent[47] tid 00000000 type 'afpfs', mounted on '/Volumes/share', from 'afp_35BfB735BfB735BfB735BfB7-2.2d000004', not responding
2/27/11 1:20:11 AM KernelEventAgent[47] tid 00000000 found 1 filesystem(s) with problem(s)
2/27/11 1:20:12 AM kernel AFP_VFS afpfs_DoReconnect started /Volumes/share prevTrigger 3 currTrigger 4
2/27/11 1:20:12 AM kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/share
2/27/11 1:20:12 AM kernel AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/share
2/27/11 1:20:12 AM kernel AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/share
2/27/11 1:20:12 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:20:12 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:20:12 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
2/27/11 1:20:13 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:20:13 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:20:13 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
2/27/11 1:20:15 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:20:15 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:20:15 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
2/27/11 1:20:19 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:20:19 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:20:19 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
2/27/11 1:20:27 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:20:27 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:20:27 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
2/27/11 1:20:37 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:20:37 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:20:37 AM kernel AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
2/27/11 1:20:46 AM KernelEventAgent[47] tid 00000000 received event(s) VQ_DEAD (32)
2/27/11 1:20:46 AM KernelEventAgent[47] tid 00000000 type 'afpfs', mounted on '/Volumes/share', from 'afp_35BfB735BfB735BfB735BfB7-2.2d000004', dead
2/27/11 1:20:47 AM kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/share
2/27/11 1:20:47 AM kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/share failed 61.
2/27/11 1:20:47 AM kernel AFP_VFS afpfs_DoReconnect: posting to KEA to unmount /Volumes/share
2/27/11 1:20:47 AM kernel ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 4 on so 0x8a697f8
2/27/11 1:20:47 AM kernel AFP_VFS afpfs_DoReconnect started /Volumes/share prevTrigger 4 currTrigger 5
2/27/11 1:20:47 AM kernel AFP_VFS afpfs_DoReconnect: already in unmount /Volumes/share
2/27/11 1:20:47 AM kernel AFP_VFS afpfs_unmount: /Volumes/share, flags 524288, pid 47
2/27/11 1:20:48 AM loginwindow[46] AFP error -1 mapped to EIO
This isn't a problem with the switch as multiple switches have been tried. It isn't a problem with the afformenetioned software because it all chugs along just fine if the media is on the local hard drive.
Any help in nailing down why the LS-V2.0TL is dropping the connection in the first, and moreover why OS X seems unable to recover from the drop would be most appreciated.
Otherwise the device is essnetially useless to me.
What firmware is the unit running on?
Thanks for the reply Jotin.
It is running 1.37 which was what was installed when I bought and is the latest (I think).
HOWEVER
Last night I realized that because the computer is primarily my wife's system the OS might not have be updated in some time. Sure enought the OS was 10.6.5 and not 10.6.6. I upgraded the system and got through about 2 hours of video without a hitch. So this may have solved the problem.
I am headed out of town this week, but I will update this thread some time after 3/7/2011 when I can test it again more thoroughly.