ScaleIO: Cannot install Windows 2012 on VxRack Node hardware

Article Number: 493737 Article Version: 3 Article Type: Break Fix

ScaleIO 1.32.1,ScaleIO 1.32.2,ScaleIO 1.32.3,ScaleIO 1.32.4,ScaleIO 1.32.5,ScaleIO 1.32.6,ScaleIO 2.0,ScaleIO 2.0.0,ScaleIO,ScaleIO,ScaleIO,ScaleIO 2.0.1,ScaleIO

Issue Description

Unable to install Windows 2012 R2 on VxRack Node hardware


Customer is following the SolVe Desktop procedures to install Windows 2012 R2 on VxRack Node hardware and is failing at the “Windows Setup” screen.


Upon choosing which partition to install Windows to in the “Windows Setup” screen and hitting the “Next” button, an error will pop up:

“Windows cannot be installed to this disk. This computer’s hardware may not

support booting to this disk . Ensure that the disk’s controller is enabled in the

computer’s BIOS menu.”

User-added image


Cannot install Windows OS to the VxRack Node hardware, upon which ScaleIO will be installed.

Windows will not recognize the UEFI disk as bootable.


If the SolVe Desktop procedures have been followed precisely, the workaround is to make the boot disk use legacy mode.

In the BIOS of the VxRack node, change the following settings:

  1. Advanced -> CSM Configuration -> Storage -> Legacy
  2. Boot -> Boot Mode -> Legacy
  3. Boot -> Boot Option #1 -> Hard Disk:(Bus 03 Dev 00)PCI Raid Adapter

    This can be manipulated under “Boot -> Hard Disk Drive BBS Priorities

If step #3 shows the satadom, make sure that the virtual drive has already been created. If it has, reboot the host one more time to show the hard drive correctly in step #3.

This will allow Windows to see the disk as bootable and then successfully install Windows 2012 on the hard drive.

Impacted versions


v 2.0.x

Fixed in version



Converting Linux VMDK to GHO file, Error 652

I need a solution

Hi. I’m following the instructions found here to create a ghost file from a Linux virtual machine. Unfortunately I’m encountering some issues. In the command prompt, I get the message “ABORT: 62, Attempted to access an inconsistent Linux partition. Operation aborted at user request”

It’s Ubuntu 18.04, file system is ext4

Any help appreciated. Thanks.



Need Help in replacing Boot drive


We have just got our support contract expired and we will renewing the contract in some days, but we got 1 boot drive replacement alert and our third party hardware support is replacing the boot drive

We need to replace the boot drive on NL400 node, I have got the document regarding it. Can some one brief me out the list of commands that need to be on cluster

I’m just aware the FRU package needs to be installed and drive firmware update needs to be done, where the firmware packages needs to be placed, it just says drag and drop on the cluster


Guard Boot stopped showing up on dual boot encrypted windows with unencrypted linux

I need a solution


It uses to work great for both windows and linux, and suddently the boot guard dissapeared and not showing up on power on / restart

Now the Guard Boot not showing up, it goes straith to grub bootloader, from there i can successfully boot unencrypted linux.

But can’t boot encrypted windows. 

I tried restoring the guard boot, by downloading recovery image.

If i boot from recovery image, the drive is recognized, i enter my passphrase and successfully boot to windows.

From there i tried running:

pgpwde –recover –disk 0

But i get:
Error: This drive is already managed.



NetScaler SDX Single Bundle Upgrade Failure When Upgrading from to or

For the NetScaler SDX single bundle upgrade to succeed, disk space used as reported by XenServer/Dom0 filesystem should be equal to or lower than 72%.

Before upgrading the SDX appliance, check the available space on XenServer and Dom0 partition. Run the df / command to check the amount of disk space used (Use%). If the disk space does not meet the requirement, don’t proceed with the upgrade until you’ve cleared the disk space.

Example 1: Failure scenario where disk use is greater than 72%

In the example below, disk space used by XenServer filesystem is reported as 75%. Amount of space used by logs in /var/log directory is reported over 400 Mb. This will cause the single bundle upgrade to fail.

[root@netscaler-sdx ~]# df /Filesystem 1K-blocks Used Available Use% Mounted on/dev/sda2 4128448 2927040 991696 75% /[root@netscaler-sdx ~]#[root@netscaler-sdx ~]#[root@netscaler-sdx ~]# cd /var/log/[root@netscaler-sdx log]# du . -sh483M .

For SDX appliances in which RAID is deployed, disk reported disk partition is /dev/md_d0p2 instead of /dev/sda2.

Example 2: Working scenario where disk use is less than or equal to 72%

 [root@netscaler-sdx]# df /Filesystem 1K-blocks Used Available Use% Mounted on/dev/md_d0p2 4128448 2821304 1097432 72% / cd /var/log [root@netscaler-sdx log]# df /Filesystem 1K-blocks Used Available Use% Mounted on/dev/md_d0p2 4128448 2821304 1097432 72% / [root@netscaler-sdx ~]# cd /var/log/[root@netscaler-sdx log]# du . -sh215M


Troubleshooting NetScaler Hard Disk Issues

Hard Drive errors can come in many forms and can be resolved via other ways than an RMA. Errors include not allowing access to the NetScaler via GUI to not booting completely.

SSH Access Works but No GUI Access

Go to shell and run command df –h the directory you’ll investigate is /var. If /var is 90% capacity, then you’ll need to check the filesystem and determine what is filling the drive. Typically, the files are newnslogs that aren’t compressed located in /var/nslog (to resolve this issue refer to CTX205014 – NetScaler newnslog Files Not Compressed Which Results in /var Directory Getting Full), support Bundles located in /var/tmp/support, and lastly install files from previous upgrades found in /var/nsinstall.

User-added image

The easiest way to find these files is to run command du -sh /var/* | sort -nr | grep G this will print out the largest directories at the top with the format in gigabytes.

User-added image

If you’re not familiar with removal of files using commands, then use WinSCP to move or delete the files.

NetScaler is unresponsive to GUI/SSH but has Console Access

We’ll need to access via the Console and reboot. If there’s a hard-drive issue, you’ll typically see error messages during boot.

User-added image

Re-seat the hard-drive and test again. Refer to Citrix Documentation To install a hard disk drive for detailed procedure to re-seat the hard drive.

Verify the File System Integrity of a NetScaler

Refer to CTX122845 – How to Verify the File System Integrity of a NetScaler.

VAR partition shows less than 5GB

If the VAR partition has less than 5GB of available space then the firmware upgrades may fail. You will need to to release some space before proceeding with the upgrade. Typically have more than 6 GB of available space upgrades.

User-added image
When using the command “installns” you will see an error that insufficient free space available :

User-added image

The upgrade error in GUI when upgrading with insufficient free space in VAR partition is kind a misleading as does not indicate a HDD capacity issue:

User-added image


  • If Flash is used for the boot up process and if NetScaler does not successfully boot, then you would see flash HD errors. In this case open a case to investigate further if an RMA is required for the SSD.
  • If the NetScaler completed boot up process but other HDD errors are detected this means the error should be under the HDD.
  • If there is still doubt about the hard-drive, then create a case with Citrix and submit a support bundle to CIS.


Scripted install from automation fails in UEFI

I need a solution

We just got our first Dell OptiPlex 7060, which only supports UEFI for internal devices.

I am able to use BootWiz to create an ISO image, burn this to a flash drive, boot the PC to this as UEFI, and start the install of Windows–it runs start to finish no problems.

I’d like to get installing via automation working; this works flawlessly for legacy computers.

  • Install WinPE: OK
  • Boot to Automation: OK
  • Erase Disk: OK
  • Partition Disk: OK
  • Install Windows 10 x64: fails with the following error:

ErrorMessage: Exception has occured in File tcube_clientsoi.cpp at Line No 893. Type of exception is ClientSOIException. Error Description is Create Process failed. Value of Windows error code = 5 and message is Access is denied.

Any thoughts on this?




AppLayering 4.x – OS layer creation fails with error “An error occurred. The required file ‘OSType.txt’ was not found on your OS disk. Please obtain the application layering OS machine tools, run ‘Setup_x64.exe’ on your OS image”

AppLayering only supports MBR and Hyper-V Generation 1 machines. It does not supports GPT and Generation 2 machines.

Capture ELM logs and in camlogfile we could see, if GPT is being used.

2017-11-17 11:43:46,085 INFO Threadpool worker Shell: EXEC: Device Boot Start End Blocks Id System

2017-11-17 11:43:46,085 INFO Threadpool worker Shell: EXEC: /dev/nbd1279p1 1 4294967295 2147483647+ ee GPT

Note: App Layering will only look at the first partition or two, so if we are running setup64.exe and it’s saving on a 3rd or 4th partition, it’ll never look at that partition by design, so it will never find ostype.txt there.


Dual-boot: BootGuard not showing up

I need a solution


I have a windows computer with windows 8 intalled in it that was encrypted. I did a patition and intalled windows 10 without decrypting the other partition. Now, the pre-boot Boot Guard is not showing up and therefore I can not access the windows 8 partition eventhough I can see it in the windows boot menu.

The partition is showing up as “RAW” since I haven’t decrypt it.

How can I get BootGuard to pop-up so I can put my passphrase and decrypt?

or alternatively how can I decrypt it without BootGuard?



XenServer on SDX does not get upgraded to 12.1.0-105

In case of Single bundle upgrade failure, the Dom0 partition disk space Use% gets stuck at 100%.

This is sticky condition and can only be corrected by rebooting the SDX appliance.

Once the system reboot is complete, the disk Use% should drop back to normal.

A check can be performed by the df / command as described in previous section.

Loss of space can be attributed to the amount of logs accumulated in the /var/log directory on the file system.

Bringing down the Use% to 72% will allow the SBU to succeed, the following steps have to be performed –

1> Reboot the system to get it out of 100% sticky mode

2> Run the following command on XS/Dom0 console to cap the log rotate to 200 Mb instead of 500 Mb

sed -i.bak ‘s/500/200/’ /opt/xensource/bin/delete_old_logs_by_space

3> Wait for minute or so for log rotate to kick in an do the necessary clean up and reduce the accumulated logs to around 200 Mb.

4> Verify that the XS/Dom0 partition available disk space Use% is less than 72% for upgrade to succeed.

5> Run the SBU again.


  • No Related Posts