5 Replies Latest reply on Jul 18, 2013 3:07 PM by a.p.

    The selected file is not a valid virtual disk file

    eduardosanchez Lurker

      Hi!,

         I'm having a problem with one of my virtual machines on VMWARE Server 2.

       

      Suddenly, after a server crash, the machine didn't boot up correctly. Apparently something went wrong with the hard disk. I tried to remove and add again the hard disk, however, when I tried to add it it says:

       

      "The selected file is not a valid virtual disk file. Please choose a different name"

       

      Attached there are vmx, vmxf and vmdk files.

       

      Any hint about this?

        • 1. Re: The selected file is not a valid virtual disk file
          a.p. Guru
          User ModeratorsCommunity WarriorsvExpert

          Did you run a file system check after the crash to ensure there are no errors with the host's file system itself?

          Does the VM's vmware.log contain any current entries with hints?

          Does the VM's folder contain any .lck files or folders? If yes, delete them.

          If the above doesn't help, post a list of files in the VM's folder (the output of: ls -lisa).

           

          André

          • 2. Re: The selected file is not a valid virtual disk file
            eduardosanchez Lurker

            * There's no errors on host file system itself.

             

            * The vmware.log file has some interesting entries, like this:

             

            Jul 17 16:46:26.204: vmx| DISKLIB-FLAT  : "/var/lib/vmware/Virtual Machines/Request Tracker (Ubuntu Server)/Request Tracker (Ubuntu Server)-f001.vmdk" : failed to open (15): Size of extent in descriptor file larger than real size.

             

            * There are not .lck files or folders.

             

            * Here is a list of the files on the VM's folder:

             

            [root@sj-vmware Request Tracker (Ubuntu Server)]# ls -lisa

            total 14226768

            876545       4 drwxr-xr-x  2 root root       4096 2013-07-18 15:05 .

            417924       4 drwxrwxrwt 22 root root       4096 2013-05-23 10:06 ..

            876548  627188 -rwxrwxr-x  1 root root  641607680 2013-07-17 03:14 Request Tracker (Ubuntu Server)-f001.vmdk

            876550 2090504 -rwxrwxr-x  1 root root 2147221504 2013-07-17 02:23 Request Tracker (Ubuntu Server)-f002.vmdk

            876551 2091448 -rwxrwxr-x  1 root root 2147221504 2013-07-17 02:23 Request Tracker (Ubuntu Server)-f003.vmdk

            876552 2087428 -rwxrwxr-x  1 root root 2147221504 2013-07-17 02:23 Request Tracker (Ubuntu Server)-f004.vmdk

            876553 2091112 -rwxrwxr-x  1 root root 2147221504 2013-07-17 02:23 Request Tracker (Ubuntu Server)-f005.vmdk

            876554 2091872 -rwxrwxr-x  1 root root 2147221504 2013-07-16 17:28 Request Tracker (Ubuntu Server)-f006.vmdk

            876555 2097184 -rwxrwxr-x  1 root root 2147221504 2013-07-17 02:23 Request Tracker (Ubuntu Server)-f007.vmdk

            876556 1049872 -rwxrwxr-x  1 root root 1075576832 2013-07-17 01:35 Request Tracker (Ubuntu Server)-f008.vmdk

            876569      12 -rwxrwxr-x  1 root root       8684 2013-07-17 13:56 Request Tracker (Ubuntu Server).nvram

            876558       4 -rwxrwxr-x  1 root root        870 2013-07-17 14:59 Request Tracker (Ubuntu Server).vmdk

            876549       0 -rwxrwxr-x  1 root root          0 2010-08-18 11:18 Request Tracker (Ubuntu Server).vmsd

            876546       4 -rwxrwxr-x  1 root root       2196 2013-07-17 17:52 Request Tracker (Ubuntu Server).vmx

            876547       4 -rwxrwxr-x  1 root root        286 2013-07-17 17:46 Request Tracker (Ubuntu Server).vmxf

            114862      32 -rw-r--r--  1 root root      31402 2013-07-17 16:42 vmware-0.log

            114801      32 -rw-r--r--  1 root root      31339 2013-07-17 16:35 vmware-1.log

            114860      32 -rw-r--r--  1 root root      31338 2013-07-17 16:28 vmware-2.log

            114806      32 -rw-r--r--  1 root root      31402 2013-07-17 16:46 vmware.log

             

             

             

            Thanks for your help.

            Best regards!

            -eduardo s.m.

            • 3. Re: The selected file is not a valid virtual disk file
              a.p. Guru
              vExpertUser ModeratorsCommunity Warriors

              This unfortunately doesn't look very promising. The size of the first extent is 641,607,680, but should be 2,147,221,504, which means 1.5GB are missing. What makes this even worse, is that this is the first extent which usually contains the partition and file system information. Do you have an up-to-date backup of this VM?

               

              André

              • 4. Re: The selected file is not a valid virtual disk file
                eduardosanchez Lurker

                Unfortunately, I do not have an up-to-date backup :'(

                 

                There's nothing I can do? there aren't tools that can check this vmware hard disk logically and put it together?

                • 5. Re: The selected file is not a valid virtual disk file
                  a.p. Guru
                  User ModeratorsCommunity WarriorsvExpert

                  I'm no data rescue specialist. However, what you can try - after backing up all the VM's current files of course - is to expand the first extend to its correct size (using e.g. the dd utility and appending zeroes to the file). The try to boot the VM from a live CD/ISO to see what can be done. Alternatively you could crate a snapshot (after resizing the extent) to ensure the current .vmdk files won't get touched (and to be able to revert to it if necessary) and then try to power on the VM and see what can be rescued with this approach.

                   

                  André