9 Replies Latest reply on Jan 25, 2015 9:45 PM by Basavaraj R Navalgund

    Unable to start VM : Invalid argument on *-flat.vmdk

    thoberre Novice

      Hi,

       

      I have an issue on a VMFS5 volume (ESXi5) where the guest vmdk files looks like they are locked in some way.

       

      The guest does not power on (see vmware.log below) and every other command accessing the flat-files fails with an Invalid argument error, including vmfstools and even touch. mv-ing works however, but the same error remains after renaming and changing pointers in the files.

       

      This looks to affect both vmdk disks/files on one particular guest on one volume - but does not affect other guests on same volume nor other vdisks for the same guest on other volumes. (The guest have 4 disks attached).

       

      I don't know how this happened, but it happened at the same time as one of my backup disks failed as a freak coincidence (or some unknown external/environmental issue). I actually lost both my live disks and the backup the same night - it's only a development/test server - but still a significant amount of work lost if not solvable.

       

      I've seen others report on similar errors, but have not been able to understand if this is solvable or how. Really appreciate any pointer in the right direction!

       

      Guest vmware.log:

      2012-06-29T22:30:22.795Z| vmx| DISK: OPEN scsi1:0 '/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest.vmdk' independent-persistent R[]

      2012-06-29T22:30:22.830Z| vmx| FileIOErrno2Result: Unexpected errno=22, Invalid argument

      2012-06-29T22:30:22.830Z| vmx| AIOGNRC: Failed to open '/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest-flat.vmdk' : Invalid argument (1600000002) (0x2013).

      2012-06-29T22:30:22.830Z| vmx| DISKLIB-VMFS  : "/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest-flat.vmdk" : failed to open (Invalid argument): AIOMgr_Open failed. Type 3

      2012-06-29T22:30:22.830Z| vmx| DISKLIB-LINK  : "/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest.vmdk" : failed to open (Invalid argument). 

      2012-06-29T22:30:22.830Z| vmx| DISKLIB-CHAIN : "/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest.vmdk" : failed to open (Invalid argument).

      2012-06-29T22:30:22.830Z| vmx| DISKLIB-LIB   : Failed to open '/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest.vmdk' with flags 0xa Invalid argument (1441801).

      2012-06-29T22:30:22.830Z| vmx| DISK: Cannot open disk "/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest.vmdk": Invalid argument (1441801).

      2012-06-29T22:30:22.830Z| vmx| Msg_Post: Error

      2012-06-29T22:30:22.830Z| vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/4ea9f2f3-7f904f43-3665-001b212e70ba/guest/guest.vmdk' or one of the snapshot disks it depends on.

      2012-06-29T22:30:22.830Z| vmx| [msg.disk.configureDiskError] Reason: Invalid argument.

      2012-06-29T22:30:22.830Z| vmx| ----------------------------------------

      2012-06-29T22:30:22.838Z| vmx| Module DiskEarly power on failed.

      2012-06-29T22:30:22.838Z| vmx| VMX_PowerOn: ModuleTable_PowerOn = 0