How to expand a RAID array on HPE servers running Esxi

I have an existing RAID 6 array created on my HPE Gen 9 server with 6 X 1.8 Tb SAS disks, which gives me a usable capacity of 6.5 Tb. Since this is an Esxi server, I have presented a datastore of the entire existing capacity. Now I need to buy 2 new disks and plug them in and expand the raid array and then expand the datastore on this Esxi server. So after inserting the 2 new disks, you need to go to the Intelligent Provisioning tool on HPE server and expand the array from that interface. Below are the steps that you will have to perform.

Please note that the time that is takes to expand the array depends on the speed of the disks you have and also the size of the array that you wish to expand. So i cant really tell you the approx time this will take, however I can assure you that this is going take a LOT of time!

  • Reboot the server and at the boot up screen hit the F10 button to go inside the Intelligent Provisioning interface.

  • Accept the EULA box and hit the next arrow

  • Select Perform Maintainence

  • Hit the HPE Smart Storage Administrator option

  • Once inside the interface make sure you select the RAID controller card on the the left and click on Configure

  • Then select the logical array on top and click on Manage Data Drives

  • Select the new disks that you have inserted and click next

  • Verify everything is in place and hit finish

  • You will now see under the active tasks that the Logical disks which you have just added are in a transforming state. This process will take a LOT of time.

  • Once the transforming is done, it will go through a parity initialization which again takes a lot of time. ( You can start the server at this time and the parity will continue to run in the background)

After the parity initialization is complete, you can now extend your Logical drive.


After this has been extended, verify the size on the logical volume and then you can start your server. In my case when I started the Esxi server up, I was able to extend my existing datastore without any issues.

HPSUM Node Baseline fails with a Inventory Error on HPE Servers

This is a quick little tip for you guys if you encounter this issue while running the launch_hpsum.bat file from a Windows server and you are trying to update the firmware or the drivers for the hardware components.

When you try and run the node inventory you are presented with the below message. This is quite simple to get around, all you have to do is right click the launch_hpsum.bat file and run as administrator.



How To Delete Or Cancel Hung Print Jobs

Today, one of my user had clogged my entire print queue on a server giving a 4GB print job!! I mean who does that??!. This stopped all my other print jobs from starting and all the users had started complaining.

I tried deleting his job from the print queue manager on the server and I got an Access Denied message, so not sure what was going on. So I finally performed the below steps to blow that 4GB print job from the queue!

  • Stop the Print Spooler service

  • Go to the folder —> C:\Windows\System32\Spool\Printers

  • In that folder look for all the .SPL files, which are the spool files and locate the one with the massive size that you want to delete and blow it away.

  • Start the Print Spooler service back on

  • After that if you see the print queue on the server, you should not see that job again and chances are that all your other print jobs should start to print.


Unable to install the .NET Framework security update KB4457918 on Windows Server 2008 R2

This month my SCCM team had released a .NET framework update for 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 7 and Server 2008 systems. I was trying to install that on one of my Windows 2008 R2 server system and it kept failing.

After looking at the WindowsUdpate.log file under C:\Windows, I spotted quite a few error codes which ranged from:

  • WARNING: Command line install completed. Return code = 0x0000066a, Result = Failed, Reboot required = false

  • WARNING: Exit code = 0x8024200B

  • WARNING: Exit code = 0x00000000; Call error code = 0x80240022

  • Installation Failure: Windows failed to install the following update with error 0x80070643

The way I fixed my particular issue was I repaired my Microsoft .NET Framework 4.5.2 listed under the Program and Features menu.

  • Start —> Run —> Appwiz.cpl

  • Locate Microsoft .Net Framework 4 Client Profile and right click it

  • Select Uninstall/Change

  • Select the repair option and click on NEXT

  • After the installation has been repaired, it will ask for a reboot

  • Reboot the server

  • Install the latest update again and hopefully it should install just fine this time.

If the above procedure does not work, then you will have to look at alternatives.


The mount point disk volume is not a clustered resource.To continue, add the resource to the cluster, or remove the mount point to cluster the shared disk

I had a Windows 2012 cluster on which my SQL team was trying to create a new role and install SQL 2016 on it. When running through the SQL installation they kept getting an error message and the base disk which acts as a mount point for the rest of the disks wasn't being detected and an error would show up.

The way we install SQL is,  we have a base disk which acts as a mount point, which is generally 1 Gb in size. Then we have different disks namely Data,Backup,Logs and TempDB which are mounted inside this base disk as mount points and have varying sizes depending upon the requirement. The actual error was:

"The mount point disk volume '\\?\Volume{79d2349d-08dc-472a-ba6a-a73117f88bd2}\' mounted at 'J:\$RECYCLE.BIN\S-1-5-21-1831736574-1690769945-617630493-456775\$R5498E5\' is not a clustered resource.To continue, add the resource to the cluster, or remove the mount point to cluster the shared disk."

To fix this I followed the below steps:

  • Remove the disks from the resource group
  • Remove the disks from the cluster
  • Bring the disks online in computer management
  • Format the Base disk that the mount points attach to
  • Recreate the mount points inside the Base disk
  • Re-add the disks to the cluster
  • Delete the Role and re-create it
  • Re-add the disks to the resource group
  • Re-create the dependencies from the mount point disks to the Base disk
  • Start SQL installation