Hello,
We have these errors showing up in synology messages:
[83364.302667] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000ed
[83364.310318] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000ee
[83364.318384] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000ef
[83364.326011] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000f0
[83364.333667] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000f1
[83364.341276] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000f2
[83364.348920] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000f3
[83364.356558] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000f4
[83364.364245] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000f5
[83364.371850] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000f6
They seem to appear when VMware Data Recovery starts working and for has once crached all the esx hosts that were connected to the synology iscsi.
I gather from some posts that one solution is to downgrade to iet. Is that still valid? And if so then when might the issue with lio be fixed. Or maybe it's something different..
Esxi 4.1
DSM 3.2-1955

