Error Accessing ISCSI Disk mounted on XenServer VM - Windows 2016

[Joao Labisa]

I am having a BIG problem on my FreeNas setup.

I have a freenas box sharing a ZVOL with ISCSI directly to a VM with windows 2016 server on a XenServer.
Its been working fine for many weeks and just today the volume started to give error on accessing folders (file corruption).
After a reboot of the VM now i have no access to the volume!

I rebooted the FreeNas box also with no luck.
I see no errors on the Freenas.
I have other iscsi shares on the same pool and the are working fine!

OS Version:
FreeNAS-11.2-U4
(Build Date: May 7, 2019 0:46)
Processor:
Intel(R) Celeron(R) CPU G1610T @ 2.30GHz (2 cores)
Memory:
12 GiB

This is a production VM so any help would be much appreciated!PLEASE.

 

[dlavigne]

Were you able to resolve this? If not, anything in /var/log/messages around the time of the failure to help pinpoint what happened?

 

[Joao Labisa]

no and nothing on the logs that I can see... the rsync error is an old schedule task.


Jun 18 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 18 00:00:00 red syslog-ng[2295]: Configuration reload finished;
Jun 18 23:00:00 red rsync: rsync: failed to connect to xxxxxx: Connection refused (61)
Jun 18 23:00:00 red rsync: rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Jun 19 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 19 00:00:00 red syslog-ng[2295]: Configuration reload finished;
Jun 19 13:14:03 red WARNING: 192.168.xxxxxx (iqn.1991-05.com.microsoft:xeon.sedept.local): no ping reply (NOP-Out) after 5 seconds; dropping connection
Jun 19 17:50:41 red WARNING: 192.168.xxxxx (iqn.1991-05.com.microsoft:ao-fs1.sedept.local): no ping reply (NOP-Out) after 5 seconds; dropping connection
Jun 19 23:00:00 red rsync: rsync: failed to connect to xxxxxx: Connection refused (61)
Jun 19 23:00:00 red rsync: rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Jun 20 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 20 00:00:00 red syslog-ng[2295]: Configuration reload finished;
Jun 20 23:00:00 red rsync: rsync: failed to connect to xxxxx: Connection refused (61)
Jun 20 23:00:00 red rsync: rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Jun 21 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 21 00:00:00 red syslog-ng[2295]: Configuration reload finished;
Jun 21 23:00:00 red rsync: rsync: failed to connect to xxxxxxxxx: Connection refused (61)
Jun 21 23:00:00 red rsync: rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Jun 22 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 22 00:00:00 red syslog-ng[2295]: Configuration reload finished;
Jun 22 03:45:00 red ZFS: vdev state changed, pool_guid=1330256214465605880 vdev_guid=3017654521962861990
Jun 22 23:00:00 red rsync: rsync: failed to connect to xxxxxxxx: Connection refused (61)
Jun 22 23:00:00 red rsync: rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Jun 23 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 23 00:00:00 red syslog-ng[2295]: Configuration reload finished;
Jun 23 23:00:00 red rsync: rsync: failed to connect to xxxxxxx. : Connection refused (61)
Jun 23 23:00:00 red rsync: rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Jun 24 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 24 00:00:00 red syslog-ng[2295]: Configuration reload finished;
Jun 24 23:00:00 red rsync: rsync: failed to connect to xxxxxx : Connection refused (61)
Jun 24 23:00:00 red rsync: rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Jun 25 00:00:00 red syslog-ng[2295]: Configuration reload request received, reloading configuration;
Jun 25 00:00:00 red syslog-ng[2295]: Configuration reload finished;

 

[dlavigne]

Please create a report at bugs.ixsystems.com and post the issue number here.

 

[Joao Labisa]

The Issue number is NAS-102307.
Thank you