Newly added disk shows up as almost full in DPM. Incorrect usage reported in DPM


, , ,


I added a new disk to DPM, and as usual formatted it, labeled it and tried to add the disk as storage pool. Whoa! 0kb remaining. Where did the space go?



1) Microsoft DPM 2012 R2, expects its storage to be kept away from prying eyes. I.e. No explorer interface.

2) Go to disk management, delete the volume.

3) Run “Add” disk and you will start seeing the newly added disk in your DPM console.

WhatsApp tile grayed out on Windows Phone. WhatsApp not working on Windows Phone developer Preview.

This morning I faced a strange issue of watching my WhatsApp live tile grayed out. I tried restarting the phone, and hard reset (volume rocker key (-) + unlock key) to no avail.  Little scouting on support forums provided the answer:


When Windows Phone 8.1 tries to backup data to cloud, it disables the app communication temporarily, so that backup is consistent. This stage should be over in 2 minutes maximum. However, if the backup process is stuck due to connectivity or other issues, it takes time, or never sends signal of resuming communication for the app, WhatsApp in this case. This renders the WA inactive, with tile grayed out.


Go to Settings->Backup->app+settings-back up now.

Once the backup starts, wait for few minutes to complete, if it does not, cancel it explicitly. “Cancel” action will intimate WA to resume communication, and your tile will be live again.

Can’t start Virtualbox VM – Error VERR_VD_IMAGE_READ_ONLY

Encountered while trying to start VM created from System Center Data Protection Manager 2012 R2, using a preview VHD downloaded from microsoft evaulation center.

Error message it provides refers to not being able to write to the file, it being read only.

Troubleshooting: I tried changing file permissions locally, no effect!

Uninstalled Virtual Box, which was installed with local account having admin privileges. Re-installed it using “Run as Administrator” and tried to recreate the VM with same VHD. It worked beautifullly.

SCVMM Error: Error adding host to SCVMM


, ,

When creating test setup, we almost always use our domain administrator credentials. The reason why we do it is because domain\administrator has far reaching powers, and setup or Test bed we are trying to create is usually for some other functional testing. Non administrator credentials are avoided unless test coverage needs to be for non-root non-superuser account.


Here I was trying to add Hyper-V host to test SCVMM setup, which was failing. Some forum posts searching revealed that,

1) SCVMM should not be setup using domain administrator privileges. The service account needs to be part of administrators, but not the “Domain\Administrator” 

2) Hyper-V setup should be created after the Windows server (Host) is already a domain member server.



Hope this helps 🙂

OpenStack Keystone service crash.


, , ,

Issue: Openstack keystone service crashes with

“WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from”

If you try to start the keystone service after the keystone-manage db_sync, during openstack setup, the keystone service starts up and then disappers. A tailf on /var/log/keystone/keystone.log shows the above mentioned error.
Happens because keystone-all tries to use the auth_token in the keystone.conf and a mere parsing error due to extra white space causes the service to crash. your auth_token and the hex value you created as token should not have any white spaces on the line.
e.g. ‘<whitespace>admin_token = 6fb86a63ac5930b4873b’ does not work but ‘admin_token=6fb86a63ac5930b4873b’ does.
When you remove the ‘#’ before the line, don’t forget to delete the whitespace there.

W: GPG error: precise-updates/grizzly Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 5EDB1B62EC4926EA


, , , ,

Why: Unable to install some cloud related packages from a Ubuntu repository even as we have specifically added the repository

#echo “deb precise-updates/grizzly main” >> /etc/apt/sources.list.d/cloud-archive.list

Simply adding the repo does not work, we must also have a valid public key available, for these packages to get installed. OS verifies the originality of the packages by using the public key.

SOlution: Install the key manually from the CLI as

#apt-get adv –recv-keys –keyserver 5EDB1B62EC4926EA

#apt-get update


Open SUSE LIVE CD not Bootable on Hyper-V: prog data error 8



Very peculiar indeed! So Open SUSE Live CD/ or any Open SUSE for that matter, having kernel version 3.1.X may not boot correctly. It is observed that Boot process works correctly till reading from the CD/ISO but fails to load the kernel when “Installation” option is selected. All it shows is two column table “data prog with error 8”.

Same ISO works great for VMWare ESX/ESXi platform but does not work on MS Hyper-V 2012.

Error shown on the screen when “Live” option is selected is:Image

Why it happens: Well I could not really find any useful information on the web related to this error. And NO Solution on any support forums.

Resolution: “data prog error 8” issue seemed to stem out of kernel not getting loaded correctly in the memory, and something wrong with the chain loading. It probably is caused by option “Live System” passed to the kernel, which does not get displayed in graphical boot menu. The key is to intercept the boot process before it reaches the graphics stage.

1) Attach Live CD/ISO to disk drive on Hyper-V VM’s settings

2) Power on the VM and hit “Esc” button repeatedly to pause the booting sequence splash screen before it reaches the graphics menu.

3) proceed with first boot option, but without using “Live System” 



Note: I am using a customized Live CD created using Open SUSE studio, which by the way is fantastic way to customize your Linux desktop ( or all of them in your organization). Issue however affects most live CD applications on Hyper-V. So it is kind of generic. Few links to forum discussions:

OpenSUSE forum:


“could not find ParserDetails.ini”


, ,


This file is referrred to by many installers/perl apps that use XML functionality. Your app or an install script may refer to this file to verify what modules are present.

Occurs when: 

ParserDetails.ini file is missing from /usr/perl/…/SAX. XML::SAX perl module is incorrectly installed or Not created at all by SAX module installation script.



Run the following command as root to create the said file.

1) “perl -MXML::SAX -e “XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()”

2) Re-run your application/installation script