1 2 Previous Next 24 Replies Latest reply on Sep 3, 2018 7:48 AM by slivovics

    Incompatible device backing specified for device '0'

    shawonpaul Lurker

      I am facing this error meesage while trying to configure a shared disk for two different guest located on two different host.

      I installed windows 2008 enterprise 64 bit on both the node.

      Both node are on different host. I wanted to create a failover cluster.

      I assigned a RDM disk to first node and selected a datastore which is located on SAN.

      Then I tried to assign this disk to second node by selecting "use an existing virtual disk". I selected the same "Disk File Path" .

      But i am just seeing the error saying "Incompatible device backing specified for device '0'".

       

      I am using ESXi 5.0 evaluation.

       

      I tried some fixes like renaming the .vmdk files and deleting cdrom from the add hardware - but none of them worked actually.

        • 1. Re: Incompatible device backing specified for device '0'
          Great_White_Tec Expert
          VMware EmployeesvExpert

          Make sure y ou have the correct controller type (LSI logic SAS) and that you are NOT using SCSI:0., Select SCSI 1:0 for example.

          • 3. Re: Incompatible device backing specified for device '0'
            shawonpaul Lurker

            well i actually used the same as you mentioned here, but no positive result.

            • 4. Re: Incompatible device backing specified for device '0'
              shawonpaul Lurker

              I have this document from the beginning; well documents aren't much in this case.

              I guess some seroius configuration change is required here; this is not a problem by the book

              • 5. Re: Incompatible device backing specified for device '0'
                AxelGonzalez Novice

                shawonpaul

                Im experiencieng the same issue. Could you solve this?

                • 6. Re: Incompatible device backing specified for device '0'
                  continuum Guru
                  vExpertCommunity WarriorsUser Moderators

                  the vmware.log where that message occurs would be helpful

                  • 7. Re: Incompatible device backing specified for device '0'
                    AxelGonzalez Novice

                    This:

                     

                    2012-10-26T12:42:38.684Z| vmx| Log for VMware ESX pid=4135407 version=5.0.0 build=build-469512 option=Release
                    2012-10-26T12:42:38.684Z| vmx| The process is 64-bit.
                    2012-10-26T12:42:38.684Z| vmx| Host codepage=UTF-8 encoding=UTF-8
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_BackdoorHintsMPN                :       0        3        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_HV                              :       2        2        2
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_VNPTShadow                      :       0        0        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_VNPTBackmap                     :       0        0        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_SVMIDT                          :       0        2        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_CallStackProfAnon               :       0        0        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_Numa                            :      93      723       91
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_GPhysTraced                     :     157      335      103
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_GPhysEPT                        :     251     1687      175
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_GPhysNoTrace                    :      14       83       10
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_BTScratchPage                   :       1        1        1
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_StateLoggerBufferPA             :       0        1        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_TraceALot                       :       0        0        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_VIDE                            :       0        3        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_VMXNETWake                      :       0        0        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_BusLogic                        :       0        8        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_PVSCSIShadowRing                :       0        0        0
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon OvhdMon_LSIRings                        :      16       16       16
                    2012-10-26T12:42:38.684Z| vmx| OvhdAnon Total                                   :    4693     7648
                    2012-10-26T12:42:38.684Z| vmx|
                    2012-10-26T12:42:38.684Z| vmx| OvhdMem maximum overheads: paged 12550 nonpaged 3091 anonymous 7124
                    2012-10-26T12:42:38.684Z| vmx|
                    2012-10-26T12:42:38.684Z| vmx| OvhdMem: average total user: 4179 anon: 4040
                    2012-10-26T12:42:38.684Z| vmx| OvhdMem: memsize 3072 MB VMK fixed 74 pages var 0 pages cbrcOverhead 0 pages total 1611 pages
                    2012-10-26T12:42:38.684Z| vmx| VMMEM: Maximum Reservation: 80MB (MainMem=3072MB SVGA=8MB) VMK=6MB
                    2012-10-26T12:42:38.685Z| vmx| VMXVmdb_SetToolsVersionStatus: status value set to 'ok', 'current', install possible
                    2012-10-26T12:42:38.688Z| vmx| Destroying virtual dev for scsi1:0 vscsi=8677
                    2012-10-26T12:42:38.688Z| vmx| VMMon_VSCSIStopVports: Invalid handle
                    2012-10-26T12:42:38.688Z| vmx| VMMon_VSCSIDestroyDev: Not found
                    2012-10-26T12:42:38.688Z| vmx| Destroying virtual dev for scsi0:0 vscsi=8676
                    2012-10-26T12:42:38.688Z| vmx| VMMon_VSCSIStopVports: Invalid handle
                    2012-10-26T12:42:38.688Z| vmx| VMMon_VSCSIDestroyDev: Not found
                    2012-10-26T12:42:38.688Z| vmx| SOCKET 2 (87) disconnecting VNC backend by request of remote manager
                    2012-10-26T12:42:38.689Z| vmx| MKS local poweroff
                    2012-10-26T12:42:38.691Z| vmx| scsi1:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
                    2012-10-26T12:42:38.691Z| vmx| Closing disk scsi1:0
                    2012-10-26T12:42:38.692Z| vmx| DISKLIB-VMFS  : "/vmfs/volumes/49bfc291-f238c3b8-6dda-00215e2c75b6/Guanipa1/Guanipa1_1-rdmp.vmdk" : closed.
                    2012-10-26T12:42:38.692Z| vmx| scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
                    2012-10-26T12:42:38.692Z| vmx| Closing disk scsi0:0
                    2012-10-26T12:42:38.693Z| vmx| DISKLIB-VMFS  : "/vmfs/volumes/4942c063-0aead0e8-e88c-00215e2c75b8/Guanipa2/Guanipa2-flat.vmdk" : closed.
                    2012-10-26T12:42:38.714Z| vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
                    2012-10-26T12:42:38.797Z| vmx| Vix: [4135407 mainDispatch.c:4084]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
                    2012-10-26T12:42:38.798Z| vmx| Vix: [4135407 mainDispatch.c:4103]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
                    2012-10-26T12:42:38.816Z| vmx| Vix: [4135407 mainDispatch.c:4084]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
                    2012-10-26T12:42:38.816Z| vmx| Vix: [4135407 mainDispatch.c:4103]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
                    2012-10-26T12:42:38.816Z| vmx| Transitioned vmx/execState/val to poweredOff
                    2012-10-26T12:42:38.816Z| vmx| VMX idle exit
                    2012-10-26T12:42:38.816Z| vmx| VMIOP: Exit
                    2012-10-26T12:42:38.819Z| vmx| Vix: [4135407 mainDispatch.c:900]: VMAutomation_LateShutdown()
                    2012-10-26T12:42:38.819Z| vmx| Vix: [4135407 mainDispatch.c:850]: VMAutomationCloseListenerSocket. Closing listener socket.
                    2012-10-26T12:42:38.820Z| vmx| Flushing VMX VMDB connections
                    2012-10-26T12:42:38.820Z| vmx| VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
                    2012-10-26T12:42:38.820Z| vmx| VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
                    2012-10-26T12:42:38.824Z| vmx| VMX exit (0).
                    2012-10-26T12:42:38.825Z| vmx| AIOMGR-S : stat o=2 r=6 w=0 i=0 br=98304 bw=0
                    2012-10-26T12:42:38.825Z| vmx| VMX has left the building: 0.

                    • 8. Re: Incompatible device backing specified for device '0'
                      continuum Guru
                      User ModeratorsvExpertCommunity Warriors

                      attach the vmware.log please - this one looks truncated

                      • 9. Re: Incompatible device backing specified for device '0'
                        AxelGonzalez Novice

                        I have configured

                        log.rotateSize = 10000

                        log.keepOld = 5

                        5 files attachments in this .zip

                        Thanks!!!

                        • 10. Re: Incompatible device backing specified for device '0'
                          continuum Guru
                          Community WarriorsvExpertUser Moderators

                          log.rotateSize = 10000
                          is a really bad idea - why did you set that ?

                           

                          it means that your logs are completely useless for troubleshooting

                          • 11. Re: Incompatible device backing specified for device '0'
                            AxelGonzalez Novice

                            continuum,

                            Here is a log more useful...

                            Thanks

                            • 12. Re: Incompatible device backing specified for device '0'
                              continuum Guru
                              User ModeratorsvExpertCommunity Warriors

                              please provide at least one complete, unthrottled log that shows the error

                              • 14. Re: Incompatible device backing specified for device '0'
                                continuum Guru
                                User ModeratorsvExpertCommunity Warriors

                                looks like your host does not like the CD drive
                                try to assign iso files instead

                                1 2 Previous Next