getting blue screen after adding disk on win 2003 server

[miatech]

guys, I keep getting blue screen after adding an ntfs disk to the vm client. I followed this guide

http://itknowledgeexchange.techtarget.com/virtualization-pro/vmware-esx-storage-how-to-get-local-sto...

any help appreciated

thanks

blog: http://pctechtips.org

[mmathurakani]

In the link that you followed the instructions from, the 4th step seems to be having some issues:

1. vmkfstools -i OpenFiler.vmdk -d raw:/vmfs/devices/disks/vmhba0:1:0:0 OpenFiler_1.vmdk

Try replacing the raw with rdm

[miatech]

do you mean? rdm:/vmfs/devices/disks/vmhba0:1:0:0 OpenFiler_1.vmdk

and what's rdm?

thanks

blog: http://pctechtips.org

[mmathurakani]

yes thats right.

rdm stands for raw device mapping

[mmathurakani]

do let me know if that worked.

[miatech]

no, when I booted, it reported the wrong size. My HD was 1T, and it reported only 15G. And not mentioning that I'm in the process of recovering all the data because it partitioned the hard drive.

[mmathurakani]

In general YES a VM can mount a NTFS LUN

And now the big BUT:

1. Take care that only one system has the volume mounted, otherwise the Volume will be destroyed!

2. You have to add the NTFS LUN to the storagegroup of the ESX Hosts, so that any ESX Server can "see" this NTFS LUN.

3. Open VI Client, point to an ESX Host, open Configuration, go to Storage Adapters and rescan twice!

Repeat this step on any ESX Host in your Cluster that contains the VM you want to work with this NTFS LUN.

The next Step will present the NTFS LUN exclusively to the VM so do this only if the physical system is down!!!

4. In VI Client point to the VM and go to Edit Settings.

Add new Harddisk and choose Raw Device Mapping, then finish the assistent as usual, but leave the RDM in "physical mode".

Mounting Volumes is hot-plugging so the VM doesn't need to be restarted.

5. Inside the VM Oepen the Diskmanager from with Windows and rescan it, the Volume will be presented like on the physical System