Quantcast
Channel: Ubuntu Forums - Virtualisation
Viewing all articles
Browse latest Browse all 4211

[SOLVED] physical disk with vmdk problem

$
0
0
Hi,


I have a virtualization server, ubuntu 12.04 LTS, running virtualbox in headless mode. On it where several VM's such as a Windows Domain Controller / Fileserver, utilizing two physical disks with generated vmdk files. (These files were name dev-sdc.vmdk and dev-sdd.vmdk).

A few days ago after a planned shutdown of the physical machine, the server broke down and was unable to boot up again. The problem was a broken power supply. Since I was going to upgrade hardware anyway, I also upgraded the motherboard and basically a complete different chipset resulting in having to completely wipe and reinstalling the base operating system which is now running ubuntu server 14.04 LTS. At the time of shutdown from the previous setup, all running VM's where put into a "save" state. However, because I couldn't edit the VM's configuration, I had to discard it, so I could fix some problems.

The vmdk files that were generated from the previous system setup, don't work anymore because the drives changed names to /dev/sdc1 and /dev/sdd1, so I generated new vmdk files and attached them to the virtual machine.

The problem that I'm having now is that Windows recognizes the drives, but the partitions just say "Healthy (Unknown Partition) 857GB" (This should be NTFS).
To be sure that the partitions were still good, I checked with the command fdisk -ls on the host and the are recognized as followed:

Code:

  Device Boot      Start        End      Blocks  Id  System
/dev/sdd1              63  1953520064  976760001    7  HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.


  Device Boot      Start        End      Blocks  Id  System
/dev/sdc1              63  1953520064  976760001    7  HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.

On the virtual machine, those two disks are displayed as illustrated in this screen shot.
Capture.PNG

To my knowledge, it is suppose the be one big partition for each disk. I know it's the VMDK files where the error is. I still have the old vmdk's is there a way I can fix this or did someone have had the same problem?

I don't really want to loose any data on those disks



Thank you for your input
Attached Images

Viewing all articles
Browse latest Browse all 4211

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>