Windows OS
--
Questions
--
Followers
Top Experts
ESXi host array degraded, VM's still responding, unable to connect. Corrupting DC?
Hello,
While diagnosing a raid 5 array (12 disks) that was beeping on a local host (degraded), I removed the disk marked as unconfigured bad (LSI).
Now none of the machines allow me to access them via RDP or Console, I fear that I have caused some serious issues / corruption on the array itself.
We have two VM's running on there, one of which is our Primary DC (and only DC, we are in the middle of an office move and re-allocated HW), the other is a print server (both fuctioning).
Both machines are responding to pings and functioning as normal, however we can't RDP or console to them, are they operating from the ESX hosts memory, would this be corrupting AD?
I am wondering what the best cause of action is, rebooting the host (local storage) and trying to rebuild the array and risk not brining up the DC again, leaving it to run (is there corruption occuring?) and hope the array fixes itself.
It's the only DC we have in the site and can't risk being unable to bring it back up.
In a bit of a pickle. I realise raid 5 was not the ideal choice.
While diagnosing a raid 5 array (12 disks) that was beeping on a local host (degraded), I removed the disk marked as unconfigured bad (LSI).
Now none of the machines allow me to access them via RDP or Console, I fear that I have caused some serious issues / corruption on the array itself.
We have two VM's running on there, one of which is our Primary DC (and only DC, we are in the middle of an office move and re-allocated HW), the other is a print server (both fuctioning).
Both machines are responding to pings and functioning as normal, however we can't RDP or console to them, are they operating from the ESX hosts memory, would this be corrupting AD?
I am wondering what the best cause of action is, rebooting the host (local storage) and trying to rebuild the array and risk not brining up the DC again, leaving it to run (is there corruption occuring?) and hope the array fixes itself.
It's the only DC we have in the site and can't risk being unable to bring it back up.
In a bit of a pickle. I realise raid 5 was not the ideal choice.
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
The volume is reported as being offline by ESX yet the VM's are still running - can't shut them down or interact with them.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Does the raid 5 use all 12 disks, or do you actually have 2 raid 5 arrays? It almost sounds like some vm's are on a different array, or that the dc Vm has a boot partition on one array ad a data partition on another. Either way, you may be in a position where you have to shut down all the vm's and reboot the host to enter the lsi bios so you can fix the array.
Can you post screenshots?
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Thanks Paul, we have resolved by following most of your advice, very much appreciated.
Windows OS
--
Questions
--
Followers
Top Experts
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.