3 Replies Latest reply on Jan 23, 2020 8:45 AM by Pollard

    Correct way to create RMDs and what type of SCSI controller is needed

    Pollard Novice

      What's the correct way to create RDM's? I had originally created mapping files using vmkfsstools and then added them as existing physical hard drives on the only SCSI controller. However I've had continuous freezing and host lockups along with the VM with them mapped not starting. Doing some reading it appears they need a dedicated scsi controller if so what type should it be SAS, Parallel, or Paravirtual and BUS sharing? I attempted to move them to a new dedicated scsi controller but the VM wont boot completely its sitting at the windows loading screen. If possible I would also like multiple VM's to have access directly to the drives.

       

       

      2.PNG

      3.PNG

        • 1. Re: Correct way to create RMDs and what type of SCSI controller is needed
          Pollard Novice

          Forgot to mention these were existing NTFS drives full of data from another computer.

          • 3. Re: Correct way to create RMDs and what type of SCSI controller is needed
            Pollard Novice

            No documentation saying it needs to be on a different dedicated scsi controller and which type is best. This thread SCSI Bus Sharing and RDMs... does it apply? gives a pretty decent explanation of bus sharing.

            None implies no SCSI bus sharing, I.e. the RDM can not be used as part of a cluster

            Virtual implies that the RDM will be shared by VMs on the same ESX host.

            Physical implies that the RDM will be shared by VMs on different hosts

             

             

            I update esxi 6.7.0 the the newest build review lastnight and I was able to get the VM back online with the dedicated SCSI controller.

             

            Current config

            2.PNG

            1.PNG

             

            Still getting these in my VMkernel warnings log

             

             

            2020-01-23T10:45:17.945Z cpu10:2097545)WARNING: NMP: nmpDeviceTaskMgmt:2400: Attempt to issue lun reset on device naa.5000cca255ee4065. This will clear any SCSI-2 reservations on the device.

             

             

            2020-01-23T10:45:17.945Z cpu10:2097545)WARNING: SCU OSSL scuTaskMgmt: type:0x2  cmdId.serialNumber:0x0

             

             

            2020-01-23T10:45:19.616Z cpu23:2097946)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.5000cca255ee4065" state in doubt; requested fast path state update...

             

             

            2020-01-23T10:46:36.708Z cpu26:2102054)WARNING: E1000: 4317: End of the next rx packet

             

             

            2020-01-23T10:47:56.275Z cpu17:2097946)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.50014ee2b93d8bff" state in doubt; requested fast path state update...

             

             

            2020-01-23T10:52:56.275Z cpu18:2097946)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.50014ee2b93d8bff" state in doubt; requested fast path state update...

            ..