No Target found for handle 36

[Visseroth]

I just started seeing this error, I was wondering if anyone had any idea what it means?

Code:

No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36
No Target found for handle 36

 

[dlavigne]

Which FreeNAS build version (from System -> Information)?

What type of initiator?

What are the target settings?

Anything else network related in /var/log/messages?

 

[Visseroth]

That's the thing, I don't use iSCSI at this time so I don't have targets
Build FreeNAS-11.1-U4

Platform Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz

Memory 65388MB

As for the logs, nothing unusual other than that error

Code:

May  3 00:00:00 storage newsyslog[65676]: logfile turned over due to size>200K
May  3 00:00:00 storage syslog-ng[24073]: Configuration reload request received, reloading configuration;
May  3 00:00:00 storage No Target found for handle 36
May  3 01:00:00 storage No Target found for handle 36
May  3 02:00:00 storage No Target found for handle 36
May  3 03:00:00 storage No Target found for handle 36
May  3 04:00:00 storage No Target found for handle 36
May  3 05:00:00 storage No Target found for handle 36
May  3 06:00:00 storage No Target found for handle 36
May  3 07:00:00 storage No Target found for handle 36
May  3 08:00:00 storage No Target found for handle 36
May  3 09:00:00 storage No Target found for handle 36

 

[Visseroth]

You know what.
I'm wondering if the zpscan.sh script (for lighting up the fault light of a ejected drive) is causing these errors since it happens every hour or so, but the question is why?