Category Archives: ESXi

Extend a raidset with STORCLI CLI

You can use this command to see the status of the Raid Controller and Raidset.

storcli /c0 show
Generating detailed summary of the adapter, it may take a while to complete.

Controller = 0
Status = Success
Description = None

Product Name = Intel(R) RAID Controller RS3DC080
Serial Number = SK94678290
SAS Address =  500605b00f7ef7e0
PCI Address = 00:b5:00:00
System Time = 03/18/2022 15:44:57
Mfg. Date = 11/24/19
Controller Time = 03/18/2022 15:44:29
FW Package Build = 24.21.0-0126
BIOS Version = 6.36.00.3_4.19.08.00_0x06180203
FW Version = 4.680.00-8519
Driver Name = lsi-mr3
Driver Version = 7.702.13.00
Current Personality = RAID-Mode
Vendor Id = 0x1000
Device Id = 0x5D
SubVendor Id = 0x8086
SubDevice Id = 0x9360
Host Interface = PCI-E
Device Interface = SATA-3G
Bus Number = 181
Device Number = 0
Function Number = 0
Drive Groups = 1

TOPOLOGY :
========

-----------------------------------------------------------------------------
DG Arr Row EID:Slot DID Type  State BT       Size PDC  PI SED DS3  FSpace TR
-----------------------------------------------------------------------------
 0 -   -   -        -   RAID5 Optl  N    5.451 TB dflt N  N   dflt N      N
 0 0   -   -        -   RAID5 Optl  N    5.451 TB dflt N  N   dflt N      N
 0 0   0   252:4    8   DRIVE Onln  N  930.390 GB dflt N  N   dflt -      N
 0 0   1   252:5    9   DRIVE Onln  N  930.390 GB dflt N  N   dflt -      N
 0 0   2   252:6    10  DRIVE Onln  N  930.390 GB dflt N  N   dflt -      N
 0 0   3   252:7    11  DRIVE Onln  N  930.390 GB dflt N  N   dflt -      N
 0 0   4   252:0    15  DRIVE Onln  N  930.390 GB dflt N  N   dflt -      N
 0 0   5   252:1    12  DRIVE Onln  N  930.390 GB dflt N  N   dflt -      N
 0 0   6   252:2    13  DRIVE Onln  N  930.390 GB dflt N  N   dflt -      N
-----------------------------------------------------------------------------

DG=Disk Group Index|Arr=Array Index|Row=Row Index|EID=Enclosure Device ID
DID=Device ID|Type=Drive Type|Onln=Online|Rbld=Rebuild|Dgrd=Degraded
Pdgd=Partially degraded|Offln=Offline|BT=Background Task Active
PDC=PD Cache|PI=Protection Info|SED=Self Encrypting Drive|Frgn=Foreign
DS3=Dimmer Switch 3|dflt=Default|Msng=Missing|FSpace=Free Space Present
TR=Transport Ready

Virtual Drives = 1

VD LIST :
=======

-------------------------------------------------------------
DG/VD TYPE  State Access Consist Cache Cac sCC     Size Name
-------------------------------------------------------------
0/0   RAID5 Optl  RW     Yes     RWBD  -   ON  5.451 TB
-------------------------------------------------------------

EID=Enclosure Device ID| VD=Virtual Drive| DG=Drive Group|Rec=Recovery
Cac=CacheCade|OfLn=OffLine|Pdgd=Partially Degraded|Dgrd=Degraded
Optl=Optimal|RO=Read Only|RW=Read Write|HD=Hidden|TRANS=TransportReady|B=Blocked|
Consist=Consistent|R=Read Ahead Always|NR=No Read Ahead|WB=WriteBack|
AWB=Always WriteBack|WT=WriteThrough|C=Cached IO|D=Direct IO|sCC=Scheduled
Check Consistency

Physical Drives = 8

PD LIST :
=======

-------------------------------------------------------------------------------------
EID:Slt DID State DG       Size Intf Med SED PI SeSz Model                   Sp Type
-------------------------------------------------------------------------------------
252:0    15 Onln   0 930.390 GB SATA SSD N   N  512B Samsung SSD 870 QVO 1TB U  -
252:1    12 Onln   0 930.390 GB SATA SSD N   N  512B Samsung SSD 870 QVO 1TB U  -
252:2    13 Onln   0 930.390 GB SATA SSD N   N  512B Samsung SSD 870 QVO 1TB U  -
252:3    14 UGood  - 930.390 GB SATA SSD N   N  512B Samsung SSD 870 QVO 1TB U  -
252:4     8 Onln   0 930.390 GB SATA SSD N   N  512B Samsung SSD 860 EVO 1TB U  -
252:5     9 Onln   0 930.390 GB SATA SSD N   N  512B Samsung SSD 860 EVO 1TB U  -
252:6    10 Onln   0 930.390 GB SATA SSD N   N  512B Samsung SSD 860 EVO 1TB U  -
252:7    11 Onln   0 930.390 GB SATA SSD N   N  512B Samsung SSD 860 EVO 1TB U  -
-------------------------------------------------------------------------------------

EID=Enclosure Device ID|Slt=Slot No.|DID=Device ID|DG=DriveGroup
DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare
UBad=Unconfigured Bad|Onln=Online|Offln=Offline|Intf=Interface
Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info
SeSz=Sector Size|Sp=Spun|U=Up|D=Down|T=Transition|F=Foreign
UGUnsp=Unsupported|UGShld=UnConfigured shielded|HSPShld=Hotspare shielded
CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded


Cachevault_Info :
===============

---------------------------------------------------------
Model  State   Temp Mode MfgDate    Next Learn
---------------------------------------------------------
CVPM02 Optimal 23C  -    2020/04/09 2022/03/31  00:41:59
---------------------------------------------------------

Here you can see under PD List, that drive 252:3 14 stand as UGood. Thats the new disk i have put into the server, and have been detected by the raidset.

To include this disk into the array that you see under VD List, you need to do this

 storcli /c0/v0 start migrate type=raid5 option=add drives=252:3

This will add the disk to the raidset. This can takes hours and even days, if you have a big raidset.
You can check the status with this command:

storcli /c0/v0 show migrate
Controller = 0
Status = Success
Description = None


VD Operation Status :
===================

------------------------------------------------------------
VD Operation      Progress% Status      Estimated Time Left
------------------------------------------------------------
 0 Reconstruction         2 In progress 9 Hours 52 Minutes
------------------------------------------------------------

DG=Arrays | Slot=Drive Bay No|VD=Virtual Drive/Logical Drive|EID=Enclosure Device ID

Here you can see that it will take 9 hours and 52 minutes to complete the Reconstruction

When it done with the reconstuction, the command from before will output this:

VD Operation Status :
===================

-----------------------------------------------------------
VD Operation Progress% Status          Estimated Time Left 
-----------------------------------------------------------
 0 Migrate   -         Not in progress -                   
-----------------------------------------------------------

And then you can check the array with the command from the top of this guide

storcli /c0 show

After this you need to change the partition table, and then expand the volume.

Move vSwitch vlans information from old host to a new one

To use this examples, there requirements are: VMware PowerCLI and a VMWare vCenter.

This example will copy all vlan’s (Virtualportgroup) from one host to another.
It will take all vlan’s from vSwitch0 on the old host, and copy it to the new host on vSwitch1.

connect-viserver
$oldhost = get-vmhost -name OldServerIP
$newhost = get-vmhost -name NewServerIP
 
$oldhost | get-virtualswitch -name vSwitch0 | get-virtualportgroup | foreach { $newportgroup = $newhost | get-virtualswitch -name vSwitch1 | new-virtualportgroup -name $_.Name -VLanID $_.VLanID }

 

Install Dell OpenManage on ESXi 5.1 host

If you have follow my guide to install the Dell Openmanage on a ESXi 4.1 host, and try the same thing on a ESXi 5.1 you will get a warning from the host saying:
This operation is NOT supported on 5.1.0 platform.

You need to install it directly on the ESXi host in 5.1 version.
So you just need to upload the Dell OM-SrvAdmin-Dell-Web-7.2.0-6945.VIB-ESX51i.zip file to the host, i will do this with WinSCP, i will put in the /tmp directory.

Then SSH to the host and run this commands:

esxcli software vib install –d /tmp/OM-SrvAdmin-Dell-Web-7.2.0-6945.VIB-ESX51i.zip

Output:

~ # esxcli software vib install -d /tmp/OM-SrvAdmin-Dell-Web-7.2.0-6945.VIB-ESX51i.zip
Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed: Dell_bootbank_OpenManage_7.2-0000
   VIBs Removed:
   VIBs Skipped:

After you have install the VIB packages successfully, the ESXi 5.1 host needs to be restarted. When the host is ready again, you should be able to see that UserVars.CIMvmw_OpenManageProviderEnabled is set to 1. In this location

Select the host and go to the Configuration tab. Click on Advanced Settings and find the UserVars.CIMvmw_OpenManageProviderEnabled, and check that this is set to 1. In ESXi 4.1, this is UserVars.CIMoemProviderEnabled

Stop error 0xc0000225 on P2V’d Windows 2008 R2

I have P2V a windows 2008 R2, from Xenserver to vmware.

But after the first good boot, it come with: Status: 0xc0000225, Info: The boot selection failed because a required device is inaccessible.

The machine will startup just fine one time, first i thougt it was the uninstall of XenServer tools?.
So i try to remove the Xenserver tools, before the P2V, but again i godt 0xC000225 error again.

I then google it, and found this post: http://web2.minasi.com/forum/topic.asp?TOPIC_ID=31980, and the fix was pretty simple:

  • Mount the Windows 2008 R2DVD in VMware and boot the virtual machine, with CDRom boot at the first boot device.
  • Hit any key to boot from the CDRrom.
  • At the first screen of the installation (Language Selection), you can hit Shift-F10 to get a command prompt.
  • Type Regedit at the command prompt.
  • Loaded hive HKEY_LOCAL_MACHINE (which mounts as a sub-hive)
    1. Highlight HKEY_LOCAL_MACHINE
    2. File > Load Hive
    3. Select < c: > \Windows\System32\config\system (name it something like “qwerty”)
  • Expand HKEY_LOCAL_MACHINE\qwerty\ControlSet001\Services\intelide
  • Change the data for value “Start” from “3” to “0”.
  • File > Unload Hive.
  • Exit regedit.
  • Reboot the VM.

 

Revert to snapshot causes virtual machine to be suspended

Error:

host cpu is incompatible with the virtual machine’s requirements at cpuid level 0x1

Details

If you take a snapshot of the virtual machine and then VMotion or cold-migrate the virtual machine to another host that uses a different CPU model and/or family, you may experience the following symptoms:

  • The virtual machine becomes stuck in a suspended state after performing a Revert to Snapshot operation
  • If you try to remove the virtual machine from its suspended state, you see the error:
    Error: error encounter trying to restore cpu state from file.

Solution

This issue may occur if the CPU information as recorded in the virtual machine configuration file (.vmx) after the Revert to Snapshot operation does not match the current CPU information. If this occurs, the server does not un-suspend the virtual machine.
To resolve this issue, you must remove the checkpoint.* lines from the .vmxfile. Removing these lines allows you to power on the virtual machine.
To remove the checkpoint.* lines:
  1. Ensure that the virtual machine is not running another process.
  2. Unregister the virtual machine.
  3. Open the .vmx file in a text editor.
  4. Remove the checkpoint.* lines from the file.
  5. Save and close the file.
  6. Re-register the virtual machine.

    The virtual machine is in a powered off state. You can now power it on.