Raw Device Mapping using ESXi on HP ProLiant N54L

I have ESXi 5.1 running on a 250GB drive in the HP N54L.  I just added four new 3TB drives (after running surface scans) and booted back up.  I want to add the four drives to the OpenMediaVault virtual machine using raw device mapping (RDM).

My first thought was to add new drives and select RDM when adding.  It looks like this does not work for local drives, or at least not for the local drives on this machine.  The option was disabled.

I've already read about some command line options to do this, so that was my next step.  This post has some directions for ESXi 4.1, which also worked on ESXi 5.1.

The first step was to enable SSH access.  I had to go to the physical server, access the settings, go to "Troubleshooting Options," and enable SSH access.  Then I was able to ssh in using Putty.

The command to create the RDM VMDK is:
#vmkfstools -z /vmfs/devices/disks/<name of disk> /vmfs/volumes/<name of local volume>/<make a raw disk name>.vmdk

For me, a command was:
# vmkfstools -z /vmfs/devices/disks/t10.ATA_____WDC_WD30EFRX2D68AX9N0_________________________WD
2DWMC1T3154102 /vmfs/volumes/250GB\ datastore/WD_WMC1T3154102.vmdk

This assumes that the raw disk was t10.ATA_____WDC_WD30EFRX2D68AX9N0_________________________WD
2DWMC1T3154102 and the spinning disk was mapped to /vmfs/volumes/250GB\ datastore/

Then, I was able to go to the VM, add a disk, select "Existing Disk," and browse to the new vmdks.  By default, when selecting "Existing Disk," my datastore was listed.  I had to browse into it to see the vmdks.

 
The post that I referenced suggested putting the RDM disks on a new virtual SCSI controller.  I did that in the nest step by selecting SCSI controller 1:0.  I also selected Independent Mode, Persistent.  Independent means that the disk is not included in snapshots.  So if I took a snapshot of the VM, the RDM disks would not be included.  If I revert the VM, the RDM disks will not change.  Persistent means that changes to the files get written to disk.  Non-persistent means that changes are lost after a reboot of the VM.  That would be very bad for a NAS.

I powered on the OpenMediaVault VM after I added the four drives as SCSI 1:0, 1:1, 1:2, and 1:3.  I logged into the web interface and was able to see the new drives under Storage | Physical Disks.

The next step is to add and configure the RAID.  I haven't decided if I'll use RAID 5 for ~9TB or RAID 10 for ~6TB.  Since I don't need the high throughput of RAID 10, I'll probably stick to RAID 5.

Install Plex to OpenMediaVault

I have ESXi 5.1 on an HP ProLiant N54L microserver.  I created a VM and installed OpenMediaVault 0.4.32_amd64.  Now I want to install Plex.

There is a very good guide here.  Here is the abbreviated version.

1. Log into the web administration page using default credentials.  Change password and enable ssh. Changing the password for admin (web access) changes the password for root.
2. ssh into the box as root using the new password.  I use Putty.
3.  Install aptitude and run an update.  If it doesn't work, it is because the web page has a lock on the package updater.  Reboot or find the process and kill it.
• apt-get install aptitude
• aptitude update
4.  Install curl
• aptitude install curl
5. Update /etc/apt/source.list.d/plexmediaserver.list to have 'deb http://shell.ninthgate.se/packages/debian squeeze main'
6. Add the key
• curl http://shell.ninthgate.se/packages/shell-ninthgate-se-keyring.key | sudo apt-key add -
7. Update again.  I saw 2 new packages from the last update.  Install plexmediaserver.
• aptitude update
• aptitude install plexmediaserver
8. Make sure it is running (/etc/init.d/plexmediaserver status), then go to the web page at <IP>:32400/web.