Below is a very handy VCS troubleshooting picture .. it can help you to do basic troubleshooting for any Symantec Veritas Cluster setup..
These are some of the issues I have came across which I would love to share with you all... "Share the Knowledge today so that it will come to you tomorrow"
Monday, June 6, 2011
Saturday, June 4, 2011
Error 1406 – Could not write value InstallPath to key Software\Microsoft
A few days back I tried installing vmware workstation on my Windows 7 64-bit and I got Error -1406 .. Eeeerrrrrr ... Errors all the time... I asked google and got so many answers but I felt unlucky as nothing worked for me.. Belive me I tried 101 things to solve... and I guess the solution was just with me... below is a simple thing what I did to get my workstation started...
Go to the regedit and delete the reg entry
Go to the regedit and delete the reg entry
Thursday, June 2, 2011
Wireless device issue with Fedora 14
I turned my MS to Linux Fedora 14 and I ended up with no Wireless on my laptop, When googled I saw many threads unanswered or unsolved for the wireless drivers for Fedora 14 ...
below solution worked for me, may be it can be a good help for you as well..
1) download the wireless drivers from the below link
below solution worked for me, may be it can be a good help for you as well..
1) download the wireless drivers from the below link
Monday, May 9, 2011
LLT does not work with Linux NIC bonded interfaces during initial startup of symantec cluster
Here goes the Solution…
We can configure Linux NIC bonds as private links under LLT. LLT treats each bonded NIC as single link. So, we must configure these NICs that form the bond in such a way that the NICs are connected to the same switch or hub.
In order to properly configure a linux bond interface to use as an LLT link it MUST be defined as follows in the /etc/llttab:
Saturday, May 7, 2011
Virtual Disk Issues in Vmware ESX
I have found that most of us have struggled a lot when it comes to converting physical System to Virtual (P2V), Due to the IDE disk which VMware is struggling to understand. Generally we see such issues with windows XP, windows 2000 and windows 2003(64-bit).
Most of my colleagues have complains about.....
- Virtual machine contains an IDE virtual disk does not detect after P2V conversion.
- Virtual machine fails to boot with a black screen after P2V conversion with just blinking underscore on the black screen.
- Or with some errors like “disk error occurred, press ctrl+alt+del to restart” after P2V, the virtual machine fails to boot.
Labels:
IDE,
P2V,
virtual disk,
vmware,
xp
Subscribe to:
Posts (Atom)