![hp smart array controller rapid rebuild hp smart array controller rapid rebuild](https://i0.wp.com/www.bitcon.be/wp-content/uploads/2020/09/MSAgen6-1.png)
I'm not even sure what the correct order is :-S. We unfortunately don't have a "normal reboot schedule" for ANY of our servers :-/. The MSA is a flaky unit but HPE support is quite good. The MSA is a flaky unit but HPE support is quite said in "Invalid Drive Movement" (HP Smart Array said in "Invalid Drive Movement" (HP Smart Array P411): Again, after powering everything back on, the server and raid array information was all intact.ĭoes your normal reboot schedule of your server include a reboot of the MSA? Could it be that they were powered back on in the incorrect order? MSAs are notoriously flaky, likely that is where the issue is. We also completely powered that server down at around the same time because I added more RAM to it. I actually rebooted this server multiple times about a month ago when I installed updates on it. Depending on which RAID controller it is connected to the MSA, you might be able to read the array information from the drive on Linux using the md utilities, but at that point it's quicker just to restore from said in "Invalid Drive Movement" (HP Smart Array said in "Invalid Drive Movement" (HP Smart Array P411): We're talking very limited experience here. Possibly, but I've never seen that particular error.
![hp smart array controller rapid rebuild hp smart array controller rapid rebuild](https://www.dectrader.com/pdf/quickspecs/13201_na/13201_ov.jpg)
Do you schedule reboots on all your equipment? If not you really should for just this reason. Since we did nothing more than power the devices off and back on, what could've caused this to happen? I of course have the option to rebuild the array and start over, but I'm leery about the possibility of this happening again (especially since I have no idea what caused it).Īny number of things.Is there a snowball's chance in hell that I can recover our array and guest VMs, instead of having to rebuild everything and restore our VM said in "Invalid Drive Movement" (HP Smart Array P411): Since we did nothing more than power the devices off and back on, what could've caused this to happen? I of course have the option to rebuild the array and start over, but I'm leery about the possibility of this happening again (especially since I have no idea what caused it). We simply powered up the MSA and the server, and have been having this issue ever since. Needless to say, we're very confused by this because nothing was "moved" nothing changed. Modifications to the array configuration following an invalid drive movement will result in loss of old configuration information and contents of the original logical drives". "An invalid drive movement was reported during POST. We rebooted the server and tried going into the RAID config utility to see what things look like from there, but we received the following message: And when I look at the hardware status in vSphere, the array controller and all attached drives appear as "Normal", but the drives all show up as "unconfigured disk".
![hp smart array controller rapid rebuild hp smart array controller rapid rebuild](https://support.keemotion.com/hc/article_attachments/360019354879/array_controller-1024x848.png)
When we logged into the vSphere client, we noticed that none of our guest VMs are available (they're all listed as "inaccessible"). One of the servers was an ESXi host with an attached HP StorageWorks MSA60. Due to hurricane Matthew, our company shutdown all servers for two days.