RDM Mapping Issue

[Jimmy_J97]

We’re having issues migrating the MSOCL1 and MSOCL2 servers, that use RDM mappings. They have been inventoried on the new vCenter however we’re unable to power them on. The log information has been exported as below.

Within the VM settings, the RDM disks are showing as below, and appear unavailable. Also, we are unable to add new RDMs, none are discovered.

Access has been granted on the SAN to both SHESX05 and SHESX06, in this case we’re using SHESX06.

Log when the VM is powered on

Task Details:
	Status: File system specific implementation of OpenFile[file] failed Description: Powering on the new Virtual Machine Start Time: Nov 23, 2017 10:30:04 AM Completed Time: Nov 23, 2017 10:30:06 AM State: error
Error Stack:
	An error was received from the ESX host while powering on VM MSOCL2. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/4c1791b6-20c22689-187f-b8ac6f7f084b/MSOCL1/MSOCL1_3.vmdk' or one of the snapshot disks it depends on. 19 (No such device) File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of OpenFile[file] failed Cannot open the disk '/vmfs/volumes/4c1791b6-20c22689-187f-b8ac6f7f084b/MSOCL1/MSOCL1_2.vmdk' or one of the snapshot disks it depends on. 19 (No such device) File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of OpenFile[file] failed Cannot open the disk '/vmfs/volumes/4c1791b6-20c22689-187f-b8ac6f7f084b/MSOCL1/MSOCL1_1.vmdk' or one of the snapshot disks it depends on. 19 (No such device) File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of OpenFile[file] failed Module 'Disk' power on failed. Cannot open the disk '/vmfs/volumes/4c1791b6-20c22689-187f-b8ac6f7f084b/MSOCL1/MSOCL1_4.vmdk' or one of the snapshot disks it depends on. 19 (No such device) File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of LookupAndOpen[file] failed File system specific implementation of OpenFile[file] failed
Additional Task Details:
	VC Build: 5973321 Error Type: GenericVmConfigFault Task Id: Task Cancelable: true Canceled: false Description Id: Drm.ExecuteVmPowerOnLRO Event Chain Id: 1144732

[RajeevVCP4]

Check if you attached CD rom on this vm, remove it then power on

[Jimmy_J97]

No luck 😞

[DTAltyapiYoneti]

any solution?

[nachogonzalez]

Hey, hope you are doing fine:

I ran into the same issue a few times in the past and I did the following:

1. Take note of the actual LUN ID and SCSI ID for the RDM:
2. Shut down both servers
3. Remove RDM on server 1.
4. Re-add RDM on server 1
5. Change SCSI ID for the RDM to match what was noted on point 1.
6. On server 2 remove RDM.
5. Re-add RDM, but not by adding the RDM but pointing the server 1 RDM's VMDK file.
6. Change SCSI id for the RDM to match what was noted on point 1
7. Power on both servers
8. Perform the health checks you deem necesary

[continuum]

> any solution ?

Yes - the guy who posted this in 2017 had a VM configured with 4 vmdks and none of them was available in the expected path.
Very likely he fixed the paths and was a happy camper afterwards.

Ulli