Add an RDM, get an error! (EqualLogic)

Google fodder.

I was able to reproduce as follows:

  1. Take a VM that's already working, shut it down (in my case, 2012 R2).
  2. Add an RDM disk (using a new controller or not, both gave the error)
  3. Try to power up the VM.

You will get an error: 38 (Function not implemented)  Goes on to talk about 'cannot open virtual disk or one of the snapshot disks it depends on' - even though no snapshots.

Thankfully, even though the Google hits were few, I figured it out.  The issue?

This is for moving our physical Veeam backup server into a VM.  For the B2D target I wanted to use an RDM that is on a different SAN than the VMs.  When I created the volume in the EqualLogic group manager I had the option of 512-byte sectors, or 4k sectors.  Figured, hey, 2012R2 can deal with 4k!

Maybe it can, but ESXi 5.5.0 (update 2b?) sure didn't.

I nuked the volume, recreated it with 512-byte sectors and it works no problem.


FWIW, the array is running the latest firmware (at time of writing, something like 7.1.2).

Error stack

** NO DESCRIPTION FOR: Drm.ExecuteVmPowerOnLRO:38 (Function not implemented)

See the error stack for details on the cause of this problem.
Time: 1/21/2015 1:47:01 PM
Target: SERVERNAME
vCenter Server: vcenterServer
Error Stack
An error was received from the ESX host while powering on VM SERVERNAME.
Failed to start the virtual machine.
Module DiskEarly power on failed.
Cannot open the disk '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1.vmdk' or one of the snapshot disks it depends on.
38 (Function not implemented)

Log log log...


2015-01-21T18:30:37.529Z| Worker#0| I120: DISK: OPEN scsi0:0 '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME.vmdk' persistent R[]
2015-01-21T18:30:37.529Z| Worker#1| A115: ConfigDB: Setting scsi0:1.redo = ""
2015-01-21T18:30:37.529Z| Worker#1| I120: DISK: OPEN scsi0:1 '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1.vmdk' independent-persistent R[]
2015-01-21T18:30:37.534Z| Worker#0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME-flat.vmdk" : open successful (10) size = 53687091200, hd = 6817958. Type 3
2015-01-21T18:30:37.534Z| Worker#0| I120: DISKLIB-DSCPTR: Opened [0]: "SERVERNAME-flat.vmdk" (0xa)
2015-01-21T18:30:37.534Z| Worker#0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME.vmdk' (0xa): vmfs, 104857600 sectors / 50 GB.
2015-01-21T18:30:37.534Z| Worker#0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME.vmdk" (flags 0xa, type vmfs).
2015-01-21T18:30:37.534Z| Worker#1| I120: FileIOErrno2Result: Unexpected errno=38, Function not implemented
2015-01-21T18:30:37.534Z| Worker#1| I120: AIOGNRC: Failed to open '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1-rdmp.vmdk' : Function not implemented (260002) (0x2013).
2015-01-21T18:30:37.534Z| Worker#1| I120: OBJLIB-FILEBE : FileBEOpen: can't open '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1-rdmp.vmdk' : Function not implemented (2490372).
2015-01-21T18:30:37.534Z| Worker#1| I120: DISKLIB-VMFS  : "/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1-rdmp.vmdk" : failed to open (Function not implemented): ObjLib_Open failed. Type 10
2015-01-21T18:30:37.534Z| Worker#0| I120: DISK: Disk '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME.vmdk' has UUID '60 00 c2 9d 28 91 73 6a-21 aa 6e fe 71 a8 ac f1'
2015-01-21T18:30:37.534Z| Worker#0| I120: DISK: OPEN '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME.vmdk' Geo (6527/255/63) BIOS Geo (0/0/0)
2015-01-21T18:30:37.535Z| Worker#1| I120: DISKLIB-LINK  : "/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1.vmdk" : failed to open (Function not implemented).
2015-01-21T18:30:37.535Z| Worker#1| I120: DISKLIB-CHAIN : "/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1.vmdk" : failed to open (Function not implemented).
2015-01-21T18:30:37.535Z| Worker#1| I120: DISKLIB-LIB   : Failed to open '/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1.vmdk' with flags 0xa Function not implemented (2490377).
2015-01-21T18:30:37.535Z| Worker#1| I120: DISK: Cannot open disk "/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME_1.vmdk": Function not implemented (2490377).
2015-01-21T18:30:37.540Z| vmx| I120: DISK: Opening disks took 13 ms.
2015-01-21T18:30:37.540Z| vmx| I120: Module DiskEarly power on failed.
2015-01-21T18:30:37.540Z| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0
2015-01-21T18:30:37.540Z| vmx| I120: scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
2015-01-21T18:30:37.540Z| vmx| I120: Closing disk scsi0:0
2015-01-21T18:30:37.541Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/5183d31c-fbe60db1-4ba4-00237d5eba3c/SERVERNAME/SERVERNAME-flat.vmdk" : closed.

Comments

  1. illicitDecember 21, 2015 at 6:36 PM

    Cheers. Just had the same issue. Saved me a lot of time.

    ReplyDelete
  2. UnknownMarch 8, 2016 at 2:38 AM

    The Inventory service was Down!

    ReplyDelete
  3. Simon JacksonJanuary 30, 2017 at 3:38 AM

    Absolutely the same issue provisioning a load of new RDMs to Veeam VMs. Wish I had found this article yesterday!

    ReplyDelete

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D...
Read more