otispresley 21 Posted June 24, 2015 Yeah, it sounds like getting those files off the SSD, even just as a backup, is the best course of action until you can replace that disk. Also, I can't copy out these VMDK files, I'm getting errors. And I can't remove the SSD because I get an error that it is in use. The main issue is that I can't create the RDM because it is grayed out though. I feel I need to get the SSD out of the system and/or get those VMDK files for the RDMs gone before I can do anything. Quote Share this post Link to post Share on other sites
RobbieH 35 Posted June 26, 2015 Yeah, even that didn't work. I can't figure out why RDM creation is grayed out. About to manually create new VMDK files so that I can add an existing VMDK. EDIT: Recreating the VMDKs manually fixed the issue. Quote Share this post Link to post Share on other sites
otispresley 21 Posted June 27, 2015 Glad to hear it! Yeah, even that didn't work. I can't figure out why RDM creation is grayed out. About to manually create new VMDK files so that I can add an existing VMDK. EDIT: Recreating the VMDKs manually fixed the issue. Quote Share this post Link to post Share on other sites
RobbieH 35 Posted June 29, 2015 Yeah, I would kind of like to start all over, but all the hours I have put into this... It wouldn't be too hard really, I boot ESXi off a USB thumb drive, then I just have to add the inventory to the new host... Quote Share this post Link to post Share on other sites
RobbieH 35 Posted April 4, 2016 It is always something fun. So, I maxed out my boot SSD, and moved my machines to a new SSD. I still don't have the ability to directly create an RDM to my physical drives, but now I can't even create manual VMDKs like I have in the past. I just get the following error: Failed to create virtual disk: Function not implemented (2490377) I have no idea what I have done here, but I really want to get these servers back up and running. Nevermind, I finally remembered what I was doing wrong on creating the RDM's manually. Forgot to put the target volume name in. Quote Share this post Link to post Share on other sites
aws1971 2 Posted December 11, 2018 Sorry to resurrect a old thread, I'm also planning to move to a esxi setup, And I read you need to disable RdmFilter.HbaIsShared but I read somewhere else you need to have that enabled to bypass the 2TB limit. My drives are all 4TB. Is this still true ? Quote Share this post Link to post Share on other sites
