• TRONTRON is one of the largest blockchain-based operating systems in the world. TRON is an ambitious project dedicated to building the infrastructure for a truly decentralized Internet.

  •  Dell EMC Elect 2018 

    Unfortunately the Dell EMC Elect program has been canceled with the merger between dell and emc after 1 year.

    Read more

  • Demo Image Everything you need and nothing you don’t. EMC MOBILE is the essential tool for those of us who live EMC. Now your documentation library is available and in-sync online or off direct from the EMC Cloud


  • Mikes AppMikes.eu App listed in Top Free Business App Windows Store. This simple but very clear app shows all the new posts from this site. Available for Windows 8 and 10. Try it out!

  • Demo ImageWhy Advertise on Mikes.eu

    Mikes.eu traffic varies depending on the post. We have a VERY focused audience in the Virtualization, AI, Blockchain, Storage and Cloud Marketing space. We have been ranked in the top 5 of Favorite Independent Blogger and one of the most visited website.


Re-add RAW LUNs to a new VMware Virtual Machine

Written by on . Posted in How to

Re-add some RAW LUNs to a new virtual machine can be tricky. You want not to end up without data. For experienced people this is very easy. But I can imagine that there are a lot of people who still have difficulty to perform such actions. There are some basic steps you need to follow before you proceed. The description below is one way to carry it out. There are of course more ways that leads us to our goal.

What I am going to do is following: For example there's a server named FS01. This server has to be deleted because it's running Microsoft Server 2003. I am going to create a new virtual machine named FS01, but this time running Microsoft Server 2008 R2. Because valuable data is on the disks we re-add these disks from old to new. The server must be presented exactly as it was. Only differents: OS

Check how many RAW LUNs you have connected to your virtual machine by open the virtual machine properties

Check inside your OS which Partitions are chosen. You do not want to end up with an application failure. You can also check through disk management. You will probably get a better overview. There's another option via DISKPART as well.

Do not forget about any shares you probably set. If not, skip this one. If you did check via Computer Management > Shared Folders

There are serveral (Storage) tools/plugins who help you to find which LUN is which. Pay attention! The wrong choice could have major implications. In my case I use the EMC Storage Plugin. It will give you a good overview. In my example below you see my RAW LUNs are C0:T0:L0 / C0:T0:L4 / C0:T0:L10.

This means:

C0:T0:L0 = Disk 3 / Driveletter F (Home)
C0:T0:L4 = Disk 4 / Driveletter G (Data)
C0:T0:L10 = Disk 5 / Driveletter H (Beheer)

Note! C = Controller : T = Target : L = LUN ID (HLU, Host LUN number, which is the LUN ID presented to the server.)

If you do not have a storage plugin you need to go to your ESX host > Configuration > Storage Adapter > Choose the right LUNs

Create a new virtual machine. Remember to create this new FS01 server NOT on the same VMFS datastore as the old Server. You wil end up with a name such as FS01_1. You do not want that!

Remove the RAW LUN disks from the 'old' FS01 server. You can choose for, Remove from virtual machine or Remove and delete... You only delete the .vmdk pointer file and not the RAW LUN. 

Add new disks to the 'new' FS01 via vm settings followed by the option Add Raw Device Mappings

Add the disks in logical sequence. Choose Physical of Virtual.

Check everything within the Windows OS. Now you are done!

Download Free Designs http://bigtheme.net/ Free Websites Templates