Albatros66
Contributor
Contributor

Problem with a ghost LUN in ISCSI which is driving me crazy

Hello everyone !

I really need your help with a problem that I haven't been able to solve for several days...

If anyone has an idea and finds a solution, I'm willing to pay for a beer anywhere in the world!

The context: I have a small infrastructure with 2 esxi V7u3, a Synology 1215 NAS, a Cisco 3850 in the middle. The connection is made via ISCSI fiber.

After a restart, impossible to find my datastore even though the devices are clearly seen in the ESXi.

I can clearly see my LUNs on the NAS side and on the ESX side with an esxcli iscsi adapter target lun list

If I create a new LUN on the NAS, I see this devices listed ESX and I can create my datastore, so the path seems OK.

I also cloned my LUN to storage to try to reconnect but it doesn't work.

I feel like I have a lock or hang on my LUN.

My 2 LUNS are:
naa.60014053b90ac9ddd622d463edae0dd1 (heartbeat)
naa.6001405aa947686d3ca2d481ed8c85d0 (my vms)

My VMKernel.log is not easy to read, but here is an excerpt in attachment (i can share other log if needed) 

 

Thank you veryyyyyyy  much in advance if you can help me

 

Reply
0 Kudos