VMware Cloud Community
studentguy
Contributor
Contributor

ESXi Losing NFS connection to Synology

I'm using VMWare ESXi with a datastore on a Synology NAS (via NFS), and occasionally the ESXi box disconnects from the NAS for a couple of minutes, and the virtual machines are unresponsive. Looking at the VMWare logs points to the connection dropping. Looking at the Synology logs by doing (?diagnose=debug) shows at the same sort of time that the VMWare box loses connection, I get this message:
Mar  6 19:44:15 afpd[3754]: [afp_dsi.c:366-E] afp_alarm: child timed out, entering disconnected state
Mar  7 09:40:22 afpd[13570]: [afp_dsi.c:366-E] afp_alarm: child timed out, entering disconnected state
While I don't have the VMware logs for the 19:44 incident, I do have logs for the 09:40:22 incident:
Configuration file for Unknown 11 cannot be
found
info
07/03/2013 09:42:19
Unknown 11
User
Configuration file for Unknown 10 cannot be
found
info
07/03/2013 09:42:18
Unknown 10
User
Configuration file for Unknown 9 cannot be found
info
07/03/2013 09:42:17
Unknown 9
User
Configuration file for Unknown 8 cannot be found
info
07/03/2013 09:42:16
Unknown 8
User
Configuration file for Unknown 7 cannot be found
info
07/03/2013 09:42:16
Unknown 7
User
Configuration file for Unknown 6 cannot be found
info
07/03/2013 09:42:16
Unknown 6
User
Device or filesystem with identifer
[334d062f-874c4415] has exited the All Paths
Down state.
info
07/03/2013 09:42:15
localhost.localdomain
Device or filesystem with identifer
[3e5d3898-52afa64e] has exited the All Paths
Down state.
info
07/03/2013 09:42:15
localhost.localdomain
Restored connection to server 10.0.1.11 mount
point /volume1/Virtual Machines mounted as
334d062f-874c4415-0000-000000000000 (Ive VM
).
info
07/03/2013 09:42:15
localhost.localdomain
Restored connection to server 10.0.1.11 mount
point /volume1/Software mounted as
3e5d3898-52afa64e-0000-000000000000
(Software).
info
07/03/2013 09:42:15
localhost.localdomain
Uplink vmnic0 has recovered from a transient
failure due to watchdog timeout
warning
07/03/2013 09:42:12
localhost.localdomain
Device or filesystem with identifer
[334d062f-874c4415] has entered the All Paths
Down Timeout state after being in the All Paths
Down state for 140 seconds. I/Os will be fast
failed.
warning
07/03/2013 09:41:52
localhost.localdomain
Device or filesystem with identifer
[3e5d3898-52afa64e] has entered the All Paths
Down Timeout state after being in the All Paths
Down state for 140 seconds. I/Os will be fast
failed.
warning
07/03/2013 09:41:40
localhost.localdomain
Configuration file for Unknown 5 cannot be found
info
07/03/2013 09:41:22
Unknown 5
User
Configuration file for Unknown 4 cannot be found
info
07/03/2013 09:41:22
Unknown 4
User
Configuration file for Unknown 3 cannot be found
info
07/03/2013 09:41:22
Unknown 3
User
Configuration file for Unknown 2 cannot be found
info
07/03/2013 09:41:22
Unknown 2
User
Configuration file for Unknown 1 cannot be found
info
07/03/2013 09:41:22
Unknown 1
User
Configuration file for Unknown cannot be found
info
07/03/2013 09:41:22
Unknown
User
Lost connection to server 10.0.1.11 mount point /
volume1/Virtual Machines mounted as 334d062f-
874c4415-0000-000000000000 (Ive VM).
error
07/03/2013 09:41:20
localhost.localdomain
Lost connection to server 10.0.1.11 mount point /
volume1/Software mounted as
3e5d3898-52afa64e-0000-000000000000
(Software).
error
07/03/2013 09:41:08
localhost.localdomain
Device or filesystem with identifer
[334d062f-874c4415] has entered the All Paths
Down state.
warning
07/03/2013 09:39:32
localhost.localdomain
Device or filesystem with identifer
[3e5d3898-52afa64e] has entered the All Paths
Down state.
warning
07/03/2013 09:39:20
localhost.localdomain
Does anyone have any ideas? I'm at a loose end here?
Thanks
Tags (2)
0 Kudos
2 Replies
Linjo
Leadership
Leadership

This has been a problem with some versions of DSM from Synology, please upgrade to the latest version your NAS supports.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
studentguy
Contributor
Contributor

Hi,

Thanks for the response. I upgraded to the very latest version last night after the last incident, but before the 9:40 am incident. I'm on the newly released 4.2 released the other day 😕 Is there anything I can do or is this a bug with Synology and down to them to fix?

Thanks

0 Kudos