Please help, vm restore after crash.

[SkuBBie]

Hi,

It all started when VMware wrote "the disk is full, please release free space..." before I could log in again. I thought I could add an extra HD and that would help me, but it didn´t. When I deleted the ekstra HD I probably toke the wrong one and now my VM aren't working : (

I found the .vmx, .vmsd, .vmdk, .log ect. files in the folder Virtual Machine and made a copy.

Is there any one who could help me with how I restore my VM and make it work again?

Regards Jens

[FusionUser321]

• Quit Fusion

• Delete all the *.lck files

• Launch Fusion

• Start the VM

Just did this last night and it worked fine. (I had just moved theVM from another drive.)

[WoodyZ]

To help figure out what is what the best way to provide comprehensive diagnostic information is to use the "Collect Support Information" command from the VMware Fusion (menu bar) > Help > Collect Support Information and then attach the .tgz file it created on your Desktop.

In addition to the .tgz file a file listing of the target Virtual Machine Packages is also needed and the directions below will help get it in the format needed.

1. In a Terminal (/Applications/Utilities/Terminal), type the following without the quotes, including the trailing space, however do not press Enter yet and note that the following contains lowercase L's, not ones: "ls -lAF "

2. In Fusion's Virtual Machine Library (VMware Fusion (menu bar) > Window > Virtual Machine Library), ctrl-click the target Virtual Machine and then select "Show in Finder".

3. Drag and drop the target Virtual Machine onto the Terminal and this will populate the fully qualified pathname of the Virtual Machine.

4. Next type the following without quotes, including leading space, then press Enter: " > ~/Desktop/filelist.txt"

Example of the full command line in Terminal:

ls -lAF /Users/${USER}/Documents/Virtual Machines.localized/Windows XP.vmwarevm  > ~/Desktop/filelist.txt

5. Next attach the filelist.txt file and the .tgz file that were created on the Desktop to a reply post.

[WoodyZ]

I edited your "Windows XP Professional.vmx" file to put back the original virtual hard drive using the current snapshot disk as shown in the .vmx so you can swap out these files with Fusion closed.

If you still get errors then provide the other information requested.

[SkuBBie]

Hi WoodyZ

I used your .vmx file and now it's a error (se attachment - Billede 1)

Is it correct that it's using the Windows XP Professionel-0002.vmdk file (2,6MB) and nok the Windows XP Professionel.vmdk which is 7,43GB? I tryed to changethe .vmx file to Windows XP Professinel instead off Windows XP Professionel-000002.vmx, but it is the same erro.

Here is the attach files as your guide explained.

Thank you for helping

[WoodyZ]

• Quit Fusion

• Delete all the *.lck files

• Launch Fusion

• Start the VM

Just did this last night and it worked fine. (I had just moved theVM from another drive.)

That's fine that whatever you did in your particular situation worked for you however it is not applicable here and if your read what the OP wrote and or looked at the attached files you would know what was wrong, (if you really knew what you were doing.)

The OP removed the primary virtual hard drive from the Virtual Machine and I edited the .vmx file to put it back because I didn't what the user to select the wrong .vmdk to add it back via the GUI because if selecting the base disk vs the snapshot disk that was the current disk it would cause additional problems and best to avoid.

Secondly the OP in all likelihood misquoted the error message however what the OP also needs to do is actually free up space on the physical hard drive that the Virtual Machine Package is stored on not the virtual hard drive as the OP was trying to add thinking that would fix the error and in turn deleted the wrong virtual hard drive.

[WoodyZ]

I attached an edited .vmx file to another reply in this thread however you are still going to have to free up some space on your Macintosh HD in order for Fusion to work with the Virtual Machine properly.

According to information in the .tgz you only have 2,02 GB of the 111,47 GB available on the Macintosh HD.

Sometimes looking at the disk graphically helps in order to decide what to move to another drive like an external drive so have a look at: GrandPerspective

[WoodyZ]

I used your .vmx file and now it's a error (se attachment - Billede 1)

Is it correct that it's using the Windows XP Professionel-0002.vmdk file (2,6MB) and nok the Windows XP Professionel.vmdk which is 7,43GB? I tryed to changethe .vmx file to Windows XP Professinel instead off Windows XP Professionel-000002.vmx, but it is the same erro.

Okay you edited this post while I was writing a reply to what you had before editing it however the first thing you're going to have to do is free up some space on the Macintosh HD.

The "Windows XP Professional-000002.vmdk" disk is what was in the Windows XP Professional.vmx.zip file you attached as the current disk howeber because of it's size there is probably nothing in it of any value and you could go back to using the base disk "Windows XP Professional.vmdk" however you're going to have to do some clean up first and you should probably also backup the Virtual Machine Package to an external drive before doing anything else.

Are you able to backup the Virtual Machine Package to an external hard drive?

Note that you must close Fusion before making the backup.

[SkuBBie]

Yes sorry about the editing part

Have much free space are vmware using i order to be running? I have now 8.88 GB free space on my Macintosh HD should that be enough?

I closed the VMware, made the change to Windows XP Professionel.vmx, but it's still the same error.

I'm not having a external HD, my only backup is on the Macintosh HD.

[WoodyZ]

I'm not having a external HD, my only backup is on the Macintosh HD.

Not being able to store files on a separate physical hard drive is not good and even if you have a copy of something on the same hard drive if something happens to that drive you can loose everything!

Also because you cannot make a full backup of the existing Virtual Machine Package you have to potential to loose everything if you make a mistake attempting to fix this issue.

I need to step out for little bit but when I come back I'll tell you how I'd fix the situation.

[SkuBBie]

Okay I will try to find a external HD and make a backup but that will take a day or to.

I would like your reply anyway so that I can try it later on.

Again, thanks for your help until now 🐵

I'm off for to night, will responde tomorrow (danish time)

[WoodyZ]

Okay I'm going to tell you exactly what I would do and if you cannot make the backup and want to proceed you'll most likely be okay however at that point you do understand that you proceed forward at your own risk (even though the risk is rather minimal.)

1. With VMware Fusion closed go into Finder and make a copy of the target Virtual Machine Package.

2. In Finder ctrl-click the target Virtual Machine Package and select Show Package Contents.

3. In the Finder window of the the target Virtual Machine Package create a new folder that you will then move all other files/folders that are within the target Virtual Machine Package into except for the following files:

Windows XP Professional.nvram
Windows XP Professional.vmdk
Windows XP Professional.vmx

By moving everything except the above 3 files into the folder you created within the target Virtual Machine Package it takes then out of the picture in order to have the Virtual Machine just use the base virtual hard drive since the snapshot disk (Windows XP Professional-000002.vmdk) has a problem and because of it's size (basically the default size of a empty 20 GB monolithicSparce disk so there is no real user data in it.)+ The remaining files/folders you moved just are not needed in an attempt to fix this with just the base disk and the .vmx and .nvram files.

4. Open the Windows XP Professional.vmx file in TextEdit and make sure the following lines show as below:

scsi0:0.present = "TRUE"
scsi0:0.fileName = "Windows XP Professional.vmdk"

Save the file if you had to edit it and then close it.

5. Start VMware Fusion and run the Virtual Machine.

If all is well then you can delete the folder that you moved all other files/folders that were within the target Virtual Machine Package into as they no longer have anything to do with the Virtual Machine.

Again while I always stress making backups before doing anything if you do the remaining steps carefully you should have no problems however again without a full backup of the target Virtual Machine Package made while Fusion is closed proceed totally at your own risk.

[SkuBBie]

I tryed your solution but I'm still getting the error:

Haven't got a screenshot but here is the text:

Cannot open the disk ' /users/Skourup/Documents/Virtuaal Mashine.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmdk' or one of the snapshot disks it depends on.

Reason: The specified virtual disk needs repair.

Do you have any other solutions to my problem or new thinks to try?

[WoodyZ]

At this point you will have to try and repair the disk.

In a Terminal (/Applications/Utilities/Terminal) use the following command:

Copy and past the following command into a Terminal and then press the Space Bar to add a space and then drag and drop the "Windows XP Professional.vmdk" file onto the Terminal window and this will populate the fully qualified pathname to complete the command line then click into the Terminal so it has focus and then press Enter.

"/Library/Application Support/VMware Fusion/vmware-vdiskmanager" -R 

[SkuBBie]

Is it my eyes or isn't this a correct command?

/Library/Application\ Support/VMware\ Fusion/vmware-vdiskmanager -R /Users/Skourup/Documents/Virtual\ Machines.localized/Windows\ XP\ Professional.vmwarevm/Windows\ XP\ Professional.vmdk

vmware-vdiskmanager: illegal option -- R ??

[continuum]

your vmdk looks so corrupted that I doubt the -R option would help at all.

You have too many of this lines in the log

DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121695 @15582208 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121696 @15582336 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121697 @15582464 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121698 @15582592 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121699 @15582720 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121700 @15582848 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121701 @15582976 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121702 @15583104 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121703 @15583232 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121704 @15583360 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121705 @15583488 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121706 @15583616 is orphaned.    
DISKLIB-SPARSECHK: [http://./Windows XP Professional.vmdk|http://./Windows XP Professional.vmdk] Grain #121707 @15583744 is orphaned.    

I would try to mount the vmdk on a Windows 32 bit host with vdk.exe - see http://chitchat.at.infoseek.co.jp/vmware/vdk.html.

Then you hopefully can extract some of the data.




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[SkuBBie]

I think the repair is worth a try but can you see what is wrong with my command? Why it aren't working?

[continuum]

the version of vmware-vdiskmanager you have seems to be older than the one Woody uses - it does not look like it understands -R




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[SkuBBie]

Du you know where to find/download new version of vmware-vdiskmanager? Or is it possible to attach a new version file here?

[WoodyZ]

From the vmware.log file I see you're using VMware Fusion 1.1 (62573) and I'm using 3.0.1. VMware Fusion 2 is a free upgrade and supports the "-R" option. You could upgrade if you wanted to in order to get the version of vmware-vdiskmanager that supports that option or you can extract it from the .dmg if you know how of use Pacifist to extract it and use it however it cannot be attached here.