Because of hurricane Matthew, our business shutdown all servers for just two times.

Because of hurricane Matthew, our business shutdown all servers for just two times.

Among the servers had been an ESXi host by having a connected HP StorageWorks MSA60.

ingrid nilsen dating

Once we logged in to the vSphere customer, we pointed out that none of our visitor VMs can be found (they truly are all detailed as “inaccessible”). So when we go through the equipment status in vSphere, the array controller and all sorts of connected drives look as “Normal”, nevertheless the drives all reveal up as “unconfigured disk”.

We rebooted the host and attempted going in to the RAID config energy to see just what things appear to be after that, but we received the following message:

“An invalid drive motion ended up being reported during POST. Changes to your array setup following a drive that is invalid can lead to lack of old setup information and articles regarding the initial logical drives”.

Of course, we are extremely confused by this because absolutely absolutely nothing ended up being “moved”; absolutely absolutely absolutely nothing changed. We simply driven within the MSA while the host, and also have been having this problem from the time.

I’ve two primary questions/concerns:

The devices off and back on, what could’ve caused this to happen since we did nothing more than power? We needless to say have the choice to reconstruct the array and commence over, but i am leery concerning the probability of this occurring once again (especially since I have don’t know just what caused it).

Will there be a snowball’s opportunity in hell that i could recover our guest and array VMs, alternatively of experiencing to reconstruct every thing and restore our VM backups?

I’ve two questions/concerns that are main

  1. Since we did nothing but power the products down and right back on, just what could’ve triggered this to occur? We needless to say have the choice to reconstruct the array and commence over, but i am leery concerning the chance for this taking place once again (especially it) since I uk sri lanka dating have no idea what caused.

A variety of things. Do you really schedule reboots on your entire gear? If you don’t you want to just for this reason. The main one host we now have, XS decided the array was not prepared with time and did not install the primary storage space amount on boot. Constantly good to learn these things in advance, right?

  1. Can there be a snowball’s opportunity in hell that I am able to recover our array and guest VMs, alternatively of experiencing to reconstruct every thing and restore our VM backups?

Possibly, but i have never ever seen that one mistake. We are chatting really restricted experience right here. Dependent on which RAID controller it really is attached to the MSA, you could be in a position to see the array information through the drive on Linux utilising the md utilities, but at that true point it really is faster merely to restore from backups.

A variety of things. Would you schedule reboots on all of your equipment? Or even you want to just for this explanation. The main one host we’ve, XS decided the array was not prepared with time and don’t mount the primary storage amount on boot. Constantly good to learn these plain things in advance, right?

I really rebooted this host times that are multiple a month ago whenever I installed updates onto it. The reboots went fine. We additionally entirely driven that server down at round the time that is same I added more RAM to it. Once more, after powering every thing straight right straight back on, the raid and server array information had been all intact.

A variety of things. Do you realy schedule reboots on all your valuable gear? Or even you want to just for this explanation. The main one host we now have, XS decided the array was not prepared over time and don’t install the storage that is main on boot. Always good to learn these things in advance, right?

I really rebooted this host times that are multiple a month ago once I installed updates on it. The reboots went fine. We additionally entirely driven that server down at round the time that is same I added more RAM to it. Once more, after powering every thing right right back on, the raid and server array information had been all intact.

Does your normal reboot routine of one’s host come with a reboot for the MSA? would it be which they had been driven straight straight back on into the order that is incorrect? MSAs are notoriously flaky, likely this is where the problem is.

I would phone HPE help. The MSA is just a flaky unit but HPE support is very good.

I really rebooted this host numerous times about a month ago whenever I installed updates about it. The reboots went fine. We additionally entirely driven that server down at round the time that is same I added more RAM to it. Once more, after powering every thing right straight straight back on, the raid and server array information had been all intact.

Does your normal reboot routine of one’s host add a reboot for the MSA? would it be they had been driven right straight back on within the wrong purchase? MSAs are notoriously flaky, likely that’s where the presssing problem is.

I would phone HPE help. The MSA is a flaky unit but HPE help is quite good.

We unfortuitously don’t possess a reboot that is”normal” for just about any of our servers :-/.

I am not really certain just what the order that is correct :-S. I might assume that the MSA would get driven on very first, then your ESXi host. Should this be proper, we now have currently tried doing that since we first discovered this problem today, while the problem continues to be :(.

We don’t have help agreement on this host or even the connected MSA, and they are most likely solution of warranty (ProLiant DL360 G8 and a StorageWorks MSA60), and so I’m unsure simply how much we would need to invest to get HP to “help” us :-S.

I really rebooted this host numerous times about a month ago whenever I installed updates onto it. The reboots went fine. We additionally entirely driven that server down at round the time that is same I added more RAM to it. Once again, after powering every thing right straight back on, the raid and server array information had been all intact.