Forum
Welcome, Guest
Username: Password: Remember me

TOPIC:

ISCSI LUN is not accessible post XenServer 8.2 patching on both the servers. 4 months 4 weeks ago #3039

Allo looks akoe wihin lizzard but drive was gone on hypervisor so we want to reconnect bet when doing we donot get a LUN. So we cannotr attach the drive

Please Log in or Create an account to join the conversation.

ISCSI LUN is not accessible post XenServer 8.2 patching on both the servers. 4 months 4 weeks ago #3040

  • Anuroop
  • Anuroop's Avatar Topic Author
  • Offline
  • Posts: 14
Post patching, the LUN disappeared from the system and disk is showing was showing unplugged. So we consulted citrix and they tired to forget the SR and when trying to recreate the SR, now, we cannot see the LUN.

Citrix is now not supporting this scenario.

Please Log in or Create an account to join the conversation.

ISCSI LUN is not accessible post XenServer 8.2 patching on both the servers. 4 months 4 weeks ago #3041

Within lizard all looks oke but when we trying to attach this drive we are getting no LUN back

Please Log in or Create an account to join the conversation.

ISCSI LUN is not accessible post XenServer 8.2 patching on both the servers. 4 months 4 weeks ago #3042

Which tool you are using the attach the disk, XenCenter?

Without log files it is difficult to understand how the problem was created and how it could be solved.

Please Log in or Create an account to join the conversation.

ISCSI LUN is not accessible post XenServer 8.2 patching on both the servers. 4 months 4 weeks ago #3043

  • Anuroop
  • Anuroop's Avatar Topic Author
  • Offline
  • Posts: 14
I observed in the result of Node2(Slave) iscsi-cfg status.
ISCSI Target service is in stopped state. The service should run as like Node1. Can you please check.

Please Log in or Create an account to join the conversation.

ISCSI LUN is not accessible post XenServer 8.2 patching on both the servers. 4 months 4 weeks ago #3044

No, it should stay stopped! Please look at the sceenshot, you can read there "exepcted stopped".
Only the primary node should have the run status.

Please Log in or Create an account to join the conversation.