VMWare ESXi suicide
Can Windows kill itself? I think no. But VMWare ESXi is easy. And so the conditions of the experiment.
It is given: The server on the Intel SR2500ALLXR platform with local storage. 6 × 300Gb SAS disks are combined into a RAID5 array. Install in the usual way ESX (say from a DVD).
After installation, we connect to the console through the VI Client and see a warning that you need to install a storage to get started with ESXi. Logically, click “Click here to create a datastore ...”
')
The most interesting begins, at first everything goes as usual:
Select Disk / LUN
Choosing a local RAID array
And here he is a stone foretold. On the first path you go head down you lose, on the second you will blow it
As it turns out, VMWare ESXi sees that the disk has already been somehow marked up in principle, but it has no idea that it did the markup itself and, in fact, was launched from these partitions. If you select the first option, you will successfully create a storage and be able to place virtual machines that will work fine BUT until the first reboot of the host, as the clock strikes 12, your virtual environment will turn into a pumpkin and you will not see anything on the screen except Non bootable partition.
What happened? VMWare ESXi completely cleared the only local storage where it was installed. The hypervisor itself is fully loaded into RAM and the hard disk is essentially not needed for operation. And your virtual machines lie to themselves as if nothing had happened safe and sound.
If you are in such a situation, the main thing is not to hurry and not try to restore ESXi from the installation disk - you will spoil everything.
You need to connect any external drive of sufficient size and install the ESXi hypervisor on it, then simply connect the local storage. After that, you will need to drop all the necessary virtual machines in a safe place and reinstall VMWare ESXi on the server's RAID array, then back up and start the virtual machines.
To prevent this from happening, you naturally need to select the Use free space option, but in my opinion, it seems silly to look at the suicide performed by VMWare - after all, you just had to once again issue a warning that ESXi was already installed and running on this disk. And user errors can no longer be.
ps It was a matter of installing ESXi on another platform, and there such a situation did not arise in principle. Even during the installation process, ESXi has already created a repository, so perhaps this is a feature of this particular platform.
Original dimka.yz74.ru/2009/03/13/wmware_suicide
It is given: The server on the Intel SR2500ALLXR platform with local storage. 6 × 300Gb SAS disks are combined into a RAID5 array. Install in the usual way ESX (say from a DVD).
After installation, we connect to the console through the VI Client and see a warning that you need to install a storage to get started with ESXi. Logically, click “Click here to create a datastore ...”
')
The most interesting begins, at first everything goes as usual:
Select Disk / LUN
Choosing a local RAID array
And here he is a stone foretold. On the first path you go head down you lose, on the second you will blow it
As it turns out, VMWare ESXi sees that the disk has already been somehow marked up in principle, but it has no idea that it did the markup itself and, in fact, was launched from these partitions. If you select the first option, you will successfully create a storage and be able to place virtual machines that will work fine BUT until the first reboot of the host, as the clock strikes 12, your virtual environment will turn into a pumpkin and you will not see anything on the screen except Non bootable partition.
What happened? VMWare ESXi completely cleared the only local storage where it was installed. The hypervisor itself is fully loaded into RAM and the hard disk is essentially not needed for operation. And your virtual machines lie to themselves as if nothing had happened safe and sound.
If you are in such a situation, the main thing is not to hurry and not try to restore ESXi from the installation disk - you will spoil everything.
You need to connect any external drive of sufficient size and install the ESXi hypervisor on it, then simply connect the local storage. After that, you will need to drop all the necessary virtual machines in a safe place and reinstall VMWare ESXi on the server's RAID array, then back up and start the virtual machines.
To prevent this from happening, you naturally need to select the Use free space option, but in my opinion, it seems silly to look at the suicide performed by VMWare - after all, you just had to once again issue a warning that ESXi was already installed and running on this disk. And user errors can no longer be.
ps It was a matter of installing ESXi on another platform, and there such a situation did not arise in principle. Even during the installation process, ESXi has already created a repository, so perhaps this is a feature of this particular platform.
Original dimka.yz74.ru/2009/03/13/wmware_suicide
Source: https://habr.com/ru/post/54322/
All Articles