2 Replies Latest reply on Feb 28, 2013 1:50 AM by a.p.

    help with fixing Grain Table

    dlfjr Lurker

      Hi, I am working with a problem vmdk file. The good news is, no snapshots or other complications. The bad news is, I've taken this as far as I know to take it.

       

      I copied the vm to another machine and behavior is exactly the same in both places. Can't start it. Can't add the vmdk to a new machine either. I have seen a few posts where folks know how to snip out the bad bits... but that was not a Windows box. Can it be done here as well?

       

      I reckon this is the relevant bit of the log, but I am happy to post any additional information that may be useful. I will also attach a zip of the log. Thank you in advance for any suggestions.

       

      Feb 27 15:50:29.475: vmx| DISK: OPEN scsi0:0 'D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk' persistent R[]
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Grain #542052 @69393792 is pointed to by multiple GTEs
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DG): GT[1376][7] = 69393792 / 69328256
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][7] = 69328256
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (XG): GT[1376][12] = 69325123 / 69328896
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][12] = 69328896
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (XG): GT[1376][28] = 69330635 / 69330944
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][28] = 69330944
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (XG): GT[1376][30] = 69326915 / 69331200
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][30] = 69331200
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Grain #549100 @70295936 is pointed to by multiple GTEs
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DG): GT[1376][127] = 70295936 / 70492544
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Resolving      GT[1376][127] = 70492544
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] Grain #1449 @196608 is pointed to by multiple GTEs
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1376][255] = 196608 / 0
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1376][383] = 196608 / 0
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1376][511] = 196608 / 0
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][127] = 196608 / 0
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][255] = 196608 / 0
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][383] = 196608 / 0
      Feb 27 15:50:29.882: vmx| DISKLIB-SPARSECHK: [D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk] GT Error (DZ): GT[1377][511] = 196608 / 0
      Feb 27 15:50:29.882: vmx| DISKLIB-SPUTIL: ===== Extent dump (D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk) =====

        • 1. Re: help with fixing Grain Table
          dlfjr Lurker

          A bit more info...

           

          I downloaded the old vdk tools and ran vdk view...

           

          Virtual Disk Driver for Windows version 3.1
          http://chitchat.at.infoseek.co.jp/vmware/

           

          'D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk' Invalid description entry.
          > ddb.geometry.biosHeads = "255"
          A) abort / I) ignore ? i
          'D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk' Invalid description entry.
          > ddb.geometry.biosSectors = "63"
          A) abort / I) ignore ? i
          'D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk' Invalid description entry.
          > ddb.geometry.biosCylinders = "5622"
          A) abort / I) ignore ? i
          'D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk' Invalid description entry.
          > ddb.encoding = "windows-1252"
          A) abort / I) ignore ? i
          Image Name      : psfsdgutil01
          Disk Capacity   : 90319478 sectors (44101 MB)
          Geometry        : (C) 5622 * (H) 255 * (S) 63
          Number Of Files : 1

           

            Type     Size    Path
          -------  -------  ----
            VMDK   90319478  D:\Data\VMServers\PSFSDGUTIL01\psfsdgutil01.vmdk

           

          Partitions      :
                #   Start Sector    Length in sectors    Type
               --   ------------  ---------------------  ----
                0              0   90319478 ( 44101 MB)  <disk>
                1             63   37752687 ( 18433 MB)  07h:HPFS/NTFS
                2       37752750   52436160 ( 25603 MB)  07h:HPFS/NTFS
                3       90188910      80325 (    39 MB)  deh:Dell Utility

           

          Ulli AKA Continuum has indicated elsewhere that these invalid description entries are an artifact of using the tool with Server 2 vmdks.

          I hit Ignore past those and I can indeed mount the file. That's kind of cool, but I'm not really after file recovery at this point. Just thought I'd add as much info as possible.

           

          meanwhile vmware-vdiskmanager commands blow up with unrecoverable error

           "not_implemented d:/build/ob/bora-156745/bora/lib/disklib/sparsechecker.c:1622"
          • 2. Re: help with fixing Grain Table
            a.p. Guru
            User ModeratorsCommunity WarriorsvExpert

            What you could try to do - after backing up the files - is to use the vmware-vdiskmanager tool attached to http://kb.vmware.com/kb/1023856 and try to repair the .vmdk file with this version.

             

            André