VMware Cloud Community
JCrain
Contributor
Contributor

Inactive Datastore

To start off, I am a student in a networking program that has recently implemented a virtualized infrastructure using a solution from vmware (obviously since im posting this here) to start teaching the basic of a virtualized infrastructure. There is two teachers and they have told me to solve this problem. We have 5 datastores that are connected to two of our ESXi 5.1 host as iSCSI targets that set up on Windows Server 2012 using windows software SCSI service that are running on two 12-bay Poweredge with a perc controller using RAID 5

To start what happened before the problem was back at the beginning of the semester we were having problems with creating and storing VMs on the datastore. I did some troubleshooting and came to find that we had a failed drive. so we ordered a replacement, it came in and tried to rebuild it but with no success. Come to find that another drive was starting to fail before the rebuild and then had failed during the rebuild. so a order was placed in for that drive too. Then the drive came in a few days later and put it in to rebuilt it and got everything started up and no blinking error lights on the drives but we were experiencing the datastores not wanting to connect.

I have been looking online

The problem I am faced with is that two of the datastores that are on one of the poweredge servers, are grayed out with inactive appended to their name. The Event Viewer on the server gives me this error.

Event_Viewer_General.png

the iSCSI software service sees the initiator connected to the target

iSCSI_Virtual_Disks.png

when i look at the storage adapter on the host under the configuration tab, i see that they are connected.

Datastores_connected.png

so in my head everything should work, but there's something I am missing. i don't really have the time to comb through forums or videos as i am now behind on some of my assignments. If anyone has dealt with this problem and has an answer please let me know. and if I have forgotten anything let me know or if more information is needed feel free to ask.

Reply
0 Kudos
1 Reply
King_Robert
Hot Shot
Hot Shot

This could be happened due to network connectivity issue between ESX hosts and the Storage node.

To workaround this issue:

  1. Connect to each ESXi 5.x host to which the LUN is presented by using SSH.
  2. Run this command  to stop the SIOC service:

    /etc/init.d/storageRM stop

  3. In the vSphere Client, select the host and then click the Configuration tab.
  4. Click Rescan All.
  5. After the rescan completes, run this command to restart the SIOC service:

    /etc/init.d/storageRM start
Reply
0 Kudos