Drive missing when trying to restore guest files

[pops106]

Hello,

I have opened a support call but thought I would post here as well.

I have got an issue with some VMs not showing all the available drives when trying to restore vm guest files, I am not using GPT disks and the VMDK's have different names.

Pictures below should show the issue, has anyone got any ideas.

I have 2 or 3 servers with the same issues.

Logs are here if anyone wants them http://www.highfive.karoo.net/pics/Logs.zip

[ssimakov]

pops106, according to the log we didn't recognize partitions on the second disk for some reason. Could you please double check that MBR partitioning is used?

[pops106]

Thanks for the response, just checked both disks and they both are "Basic, Online, MBR Volumes"

Anything else I can look at?

[ssimakov]

Could you please get the first 1 MB of the VMDK in question using command dd bs=1K count=1024 if=VMDKFILE of=OUTPUTFILE on your ESX and send it attached to your support case? We'll review the partitioning of the disk to understand why it was not recognized.

[pops106]

I have just had a look at the FLR plugin and guess what, there are errors whilst trying to mount the disk but I can actually restore files.

I will upload the file now.

Cheers

[Gostev]

Well, FLR plug-in uses different algorithm/method of determining available partitions, so that explains why the results are different. But since it also displays errors then it looks like there's some problems with partitioning table on this VM indeed.

[pops106]

I can hopefully get that sorted, it must of been something to do with the P2V conversion or something.

Cheers

[jens]

Hi,

do you have a solution for that issue yet ? I have the same problem now....

Jens

[indigene]

can you post the solution here please i have the same problem
thx

[Gostev]

Guys, there is no universal resolution to this problem. Once, it was due to corrupted MBR on virtual disk. The other time, it was an unsupported disk type. The other time, it was due to having more than 1 partition on dynamic disk (which is not supported). So for this type of issue, we need to investigate log files - and sometimes additional stuff.

[PKramer]

ok I have a case in with Support for this exact same problem except mine is a vRDM that is just under 2TB.

I grabbed the logs from the first post and in comparing his logs to mine, I think I see a similarity that maybe should be looked at:

His log:

Code: Select all

[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view: Disk Capacity   : 284500194 sectors (138916 MB)
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view: Number Of Files : 1
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view:   Type     Size    Path
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view:  -------  -------  ----
[12.03.2009 11:54:34] <06> Info  VDK view:   FLAT   284500194  C:\.......\Local Settings\Temp\1\VeeamVirt\Atlas_1-flat.vmdk
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view: Partitions      :
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view:       #   Start Sector    Length in sectors    Type
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view:      --   ------------  ---------------------  ----
[12.03.2009 11:54:34] <06> Info  VDK view: 
[12.03.2009 11:54:34] <06> Info  VDK view:       0              0   284500194 (138916 MB)  <disk>

My log:

Code: Select all

[16.04.2010 10:36:15] <13> Info  VDK view: Failed to decide type of 'C:\......\Local Settings\Temp\VeeamVirt\NTS1_1-rdm.vmdk'.
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view: Open as a simple sector image file.
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view: Image Name      : NTS1_1-rdm
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view: Disk Capacity   : 3925868544 sectors (1916928 MB)
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view: Number Of Files : 1
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view:   Type     Size    Path
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view:  -------  -------  ----
[16.04.2010 10:36:15] <13> Info  VDK view:   FLAT   3925868544  C:\......\Temp\VeeamVirt\NTS1_1-rdm.vmdk
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view: Partitions      :
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view:       #   Start Sector    Length in sectors    Type
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view:      --   ------------  ---------------------  ----
[16.04.2010 10:36:15] <13> Info  VDK view: 
[16.04.2010 10:36:15] <13> Info  VDK view:       0              0   3925868544 (1916928 MB)  <disk>

Notice the similarity, in that both our drives that are not visible do not have the typical 32 or 63 or 126 sectors at the beginning that look like this in the log:

Code: Select all

 
[15.04.2010 10:44:01] <07> Info  VDK open:       0              0   83886080 ( 40960 MB)  <disk>
[15.04.2010 10:44:01] <07> Info  VDK open:  E:   1             63   83762847 ( 40899 MB)  07h:HPFS/NTFS

From what I can tell in my logs, all my disks that work start at the 32nd or 63rd or 123rd sector. The one that does not starts at sector 0.

Does anyone have any disk that start at 0 that show up in the Backup Browser??