He had to fix virtual disk

When I try to delete a snapshot I get the message: "there is ERROR WHILE TRYING to DELETE the SNAPSHOT impossible to clean deleted files: the specified virtual disk needs to be repaired" I had this problem for a long time and nobody seemed to be able to help me.  The biggest problem is that now I get the error message: "THIS VIRTUAL MACHINE HAS MORE THAN 100 SHOTS IN a SINGLE BRANCH OF ITS SNAPSHOT TREE if you take several shots of the VM in this branch, the guest operating system may not start again.  You must delete some shots or make a full clone of the virtual machine"when I use the 'dismantling' to try to remove snapshots there is only 1 shoot snap it (not more than 100) and it won't let me not even delete this one - I get the message on repair the specified disk!  If I'm better to do a clon full I can find how to do but I think the best thing would be to locate more than 100 pictures and delete them. Help!

For those following this thread that the resolution is down to use TeamViewer to establish a connection and after reviewing the State of the existing virtual machine and its file structure, we used a copy of the original disc base within the whole of the existing Virtual Machine to create a new virtual and moved the Copy Machine in the package of the virtual machine in order to keep everything bundled default normal Fusion Virtual Machine.  It had basically everything accept the current user data that will be saved out of the old Virtual Machine before it is deleted.  What makes it particularly easy to do's, is the original Virtual Machine was created in Fusion 1.x and had the VHD monolithic default and with the character size and the date and time this basic disk, all that is needed are Windows updates since the middle of October and current user data and it is so good to go and up to date.  So that made it very easy to decide to create an existing virtual machine from the base of the virtual machine disk and not even try to treat 100 orphans AutoProtect snapshots and just delete the now old Virtual Machine after it is in checked that all the user data has been retrieved.

Also the appearance of things the situation that caused the problem has been the AutoProtect feature was still creating AutoProtect snapshots and do not delete as it should to in order to keep only the number defined when configuring this feature.  This not the first time I see a mess like that I firmly believe that it is caused by a bug in this feature.

In any case Todd was nice to talk to you and help you with this problem.  Once you are sure to have your user out of the VM now old data, you can simply delete it like I showed you and also mentioned by oreeh.

Tags: VMware

Similar Questions

  • Trying to fix a CID parent access to a file descriptor of delta but VM still does not start. Other error "cannot open the disk...". The specified file is not a virtual disk.

    Starting the virtual machine has been tried several times earlier when I received the error message to tell the parent disk had been changed since the child was created. I looked at the resolution and had a go at fixing.

    I downloaded the vmdk files to find the problematic descriptor file it corrected and then download the a back fixed to the data store. I then removed the VM of the inventory and then re he added before attempting to start it. He says now the specified file is not a virtual disk. Unfortunately, I didn't know that he was still working on a snapshot file and had been for some time. It was a former VM test that I had played a little bit with all learning on VMware, but unfortunately he had a few files on it which is no longer, I have backup ups for and I could really do with recovery of them! The base file and delta file are always on display in the data store and I can re - use the base file in a new virtual machine but I need the data from the snapshot if possible file. Not sure if it can be manually engaged at the base (I have a copy of). I'm new to this depth of troubleshooting and according to research I realize it is a great chance, the data is not recoverable. Having said that if there is no hope at all then I would try or at least have someone who knows what they're doing a go help before you tell me everything is lost! I'm not really bothered to get the virtual machine running again, but must be able to copy some files in the C drive.

    Any help much appreciated.

    Thank you

    Craig

    I can't tell you if the data in the virtual drive itself can be retrieved by the attached hard file. However, it seems that you have used an editor who added a BOM (Byte-Order-Mark) at the beginning of the file, which made her an invalid for ESXi.

    André

  • The specified file is not a virtual disk - easy to fix?

    Ok.  So I know there are a lot of posts dealing with this problem, but most are with the merger.  I HOPE mine should be an easy fix...

    So my just bluescreened machine while running my Ubuntu VM.  The first thing that happened when the computer reboots, I opened VM Player and my my Ubuntu.vmdk file was missing, so I looked all around her.  Found it or a copy of it in the trash.  Reconstituted and then he said "the specified file is not a virtual disk"...  So I upgraded to VM Workstation and still get the same thing...  All the files look good...  How to find on which file is corrupt?  I tried with vmware-vdiskmanager-R option and he said: everything is good.  Help, please!

    Ubuntu.VMDK

    C:\Ubuntu-1010 > Ubuntu.vmdk more
    # Disk DescriptorFile
    version = 1
    CID = e37c3858
    parentCID = ffffffff
    isNativeSnapshot = 'no '.
    createType = "twoGbMaxExtentSparse.

    # Description of the measure
    RW SPARSE 4192256 "Ubuntu - s001.vmdk.
    RW SPARSE 4192256 "Ubuntu - s002.vmdk.
    RW SPARSE 4192256 "Ubuntu - s003.vmdk.
    RW SPARSE 4192256 "Ubuntu - s004.vmdk.
    RW SPARSE 4192256 "Ubuntu - s005.vmdk.
    RW SPARSE 4192256 "Ubuntu - s006.vmdk.
    RW SPARSE 4192256 "Ubuntu - s007.vmdk.
    RW SPARSE 4192256 "Ubuntu - s008.vmdk.
    RW SPARSE 4192256 "Ubuntu - s009.vmdk.
    RW SPARSE 4192256 "Ubuntu - s010.vmdk.
    RW SPARSE 20480 "Ubuntu - s011.vmdk.

    # The database disk
    #DDB

    DDB. Encoding = "windows-1252".
    ddb.adapterType = "free".
    DDB. Geometry.sectors = "63".
    DDB. Geometry.Heads = "255".
    DDB. Geometry.Cylinders = "2610".
    ddb.virtualHWVersion = "4".
    ddb.longContentID = "301956ccc44d62dcba724cc5e37c3858".
    ddb.toolsVersion = "8325.

    Directory;

    12/09/2011 14:50 < DIR >.
    12/09/2011 14:50 < DIR >...
    08/09/2011 10:59 1 073 741 824 564d29b3-9f68-5736-32f3-387596b53bbd.vmem

    08/09/2011 10:59 < DIR > 564d29b3-9f68-5736-32f3-387596b53bbd.vmem
    .lck
    13/03/2011 20:33 < DIR > caches
    01/09/2011 10:18 8 684 nvram
    13/03/2011 17:51 Readme.txt 887
    08/09/2011 10:58 13,172,736 Ubuntu - s001.vmdk
    08/09/2011 10:58 1,282,277,376 Ubuntu - s002.vmdk
    08/09/2011 10:58 1,145,896,960 Ubuntu - s003.vmdk
    08/09/2011 10:58 97,583,104 Ubuntu - s004.vmdk
    08/09/2011 10:58 297,467,904 Ubuntu - s005.vmdk
    08/09/2011 10:58 471,334,912 Ubuntu - s006.vmdk
    08/09/2011 10:58 1,678,901,248 Ubuntu - s007.vmdk
    08/09/2011 10:58 1,414,987,776 Ubuntu - s008.vmdk
    08/09/2011 10:59 796,327,936 Ubuntu - s009.vmdk
    08/09/2011 10:59 40,370,176 Ubuntu - s010.vmdk
    08/09/2011 10:59 65 536 Ubuntu - s011.vmdk
    10/09/2011 12:40 AM Ubuntu.log 39,356,019
    08/09/2011 10:59 Ubuntu.vmdk 830
    01/09/2011 09:18 Ubuntu.vmem 1 073 741 824
    13/03/2011 17:53 Ubuntu.vmsd 0
    01/09/2011 10:19 Ubuntu.vmss 30,979,100
    12/09/2011 13:07 4 328 Ubuntu.vmx
    13/03/2011 19:31 Ubuntu.vmxf 261
    2010-01-22 19:46 993 840 vmware - vdiskmanager.exe
    22 file (s) on 9,457,213,261 bytes
    4 dir 81,049,886,720 bytes free

    Sorry, but I'm a little confused. What do you mean by 'vmx-converted vmdk "?

    In any case, I took a look at the vmx file and found:

    scsi0:0. FileName = "Ubuntu - s001.vmdk.

    who should actually be

    scsi0:0. FileName = "Ubuntu.vmdk".

    because "Ubuntu.vmdk" is the file descriptor.

    André

  • Failed to initialize the library for the assembling and disassembling workstation virtual disks 9

    I am using VMware Workstation 9.0.4 build-1945795 and have a problem with "map of the virtual disks. I tried map a virtual drive on windows server 2008 r2, windows server 2008, windows 7, windows xp, windows 2000, windows 98, and BACK 6.22. I have went to the file - card virtual disks and get 'Could not initialize the library for the Assembly and disassembly of the virtual disks', every time I have try to map any operating system for the virtual machine. Some have snapshot while others do not is a mixture of 64-bit and 32-bit virtual machines. My system is Windows 7 Enterprise 64-bit. What I'm missing here because if a feature is available in the menu you seem to expect it to work actually on something.

    OK the fix for me was that I had to uninstall VMware workstation and now it seems to work very well on all the OS preceding reinstall it.

  • Dell virtual disk are larger. You want to increase the size of the data store.

    Hello

    I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

    I tried to follow the article here that explains how to do this via the CLI.

    Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

    Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

    I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

    ---

    I use that as a guide:

    http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461


    1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

    This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)


    2. open a console to the ESXi host.

    Pretty simple.


    3. get the DeviceID for the data store to change.

    ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

    System file VMFS-5, 60 extending on 1 partition.

    File system label (if applicable): datastore1

    Mode: public

    Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

    UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

    Partitions split (on 'lvm'):

    NAA.6c81f660ef0d23001ad809071096d28a:4


    A couple of things to note:

    a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

    b. the number of Partition on the disk is: 4 ' [...]: 4 "»

    c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

    4. Enter the amount of disk space available on the data store.

    ~ # df h

    Size of filesystem used available use % mounted on

    VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1


    5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

    ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

    364456 255 63 5854986240

    1 63 80324 222 0

    2 80325 8466884 6 0

    3 8466885 13709764 252 0

    4 13711360 3865468766 251 0

    ~ #


    According to the table in article KB

    4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

    | |        |          |   |

    | |        |          |   \---attribut

    | |        |          \---type

    | |        \---se finishing sector

    | \---a starting from sector

    partition \---Numero


    Also note how the number of section start the old end sector number is + 1.


    6 identify the partitions that need to be resized and the size of the space to use.

    We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.


    7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

    ESXi 5.x has a command to do this:

    ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

    1 5854986239

    This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

    13711360 - 5854986239 (i.e. the end of the disc)


    8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

    Using the above information, our command is:

    resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239


    9 step 8, the partedUtil command can report the warning:

    He did not. Displacement.


    10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.


    11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

    Fact.


    12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

    vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.


    It did not work. I got an error:

    / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

    23001ad809071096d28a:4 ".

    Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information


    Also the partition was very different to what I asked:

    ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

    364456 255 63 5854986240

    1 63 80324 222 0

    2 80325 8466884 6 0

    3 8466885 13709764 252 0

    4 13711360 1560018942 251 0


    I fixed it by running these commands:

    ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

    ~ # vmkfstools v

    ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

    364456 255 63 5854986240

    1 63 80324 222 0

    2 80325 8466884 6 0

    3 8466885 13709764 252 0

    4 13711360 3865468766 251 0

    Update:

    Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

    Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

  • Virtual disk parent has changed since the child was created.

    I recently had one of my virtual machines go down and I couldn't connect to access anything whatsoever, so I rode as an extra hard drive to another virtual machine in order to access the data I needed.

    Once I had finished I he took off the other VM and proceeds to the power on the virtual machine, but I got an error of:

    "The virtual disk parent has been changed since the child was created." The content of the virtual disk ID parent does not match the ID of parent matching the child content. »

    Reason: The virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent matching the child content.
    Cannot open disk ' / vmfs/volumes/4e24c6fe-3c2ad61e-a57c-e4115bbbce6c/SNCTrillium/SNCTrillium-000003.vmdk' or one of the snapshot disks it depends on.

    I read upward through the knowledge base of VMWare on the modified files, but I've never had to do that before and I'm not sure about how to go on this subject as I've never used the vsphere CLI either.

    I am currently using ESXi 5.0.0 with vsphere client 5.0.0. I've attached a screenshot of the error.

    According to the snapshot between SNCTrillium - 000001.vmdk and the basic disk SNCTrillium.vmdk is broken, which means that the basic disk has been changed. I have attached an instant replacement for the SNCTrillium - 000001.vmdk with a fixed string that should allow you to open the virtual machine. However, since I do not know what and how much data has changed on the basic disk, I can't tell you how much data corruption, you will see. So you better take an another snapshot to be temporary once loading hard file attached, in order to ensure the current hard data files cannot be changed.

    André

  • Please help: the virtual disk parent has changed...

    After a few days of research about this error, I decided that I had to ask for some evidence of your experts to help me recover from this error.

    Thank you!

    It is a small desktop application:

    -Dell T410 esxi Server 5

    -a virtual machine, Windows Server 2003 with 2 discs, no fixed size

    I was help this office by managing services and updates on this Server 2003.  I ran updates on Friday and restarted.  When he came I open vSphere and found the virtual machine does not.  I tried to start it and got the error.  So, it seems I may have the CID issue that needs to be corrected.

    I don't have a direct access to this server so I'm remoting with RDS on 2003 VM server and vSphere on the esxi.  Did I make the right diagnosis and is it possible for me to make the necessary corrections to distance or I need direct access to the server?  Everything I've read has files of people editing CID numbers and it seems that they directly access the esxi server.

    Shows the data store:

    hard 'server '.

    hard 'server_1.

    'server' - 000001.vmdk

    "server_1" - 000001.vmdk

    'server' - snapshot1.vmsn

    I stuck a few newspapers below...

    DISC: Scsi0:0 [OPEN ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' persistent R]
    2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': open with success (10) size = 5620404224, hd = 213826. Type 8
    2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-DSCPTR: open [0]: "Server-000001 - delta.vmdk ' (0xa)
    2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' (0xa): vmfsSparse, 35526656 sectors / 16.9 GB.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': open with success (14) size = 18189647872, hd = 181059. Type 3
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-DSCPTR: open [0]: 'server - flat hard' (0xe)
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk' (0xe): vmfs, 35526656 sectors / 16.9 GB.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB LINK: DiskLinkIsAttachPossible: incompatibility of the content ID (parentCID f72e60c7! = f05537b3) /vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-STRING: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk ': cannot open (the virtual disk parent has changed since the child was created.) The content of the virtual disk ID parent does not match the ID of parent for children's content).
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': closed.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': closed.
    2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LIB: can't open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' with the virtual disk 0xa flags parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
    2012-08 - 05T 20: 00:06.035Z | VMX | DRIVE: Cannot open disk ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk ': the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
    2012-08 - 05T 20: 00:06.035Z | VMX | Msg_Post: error
    2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.noBackEnd] unable to open drive ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' or one of the snapshot disks it depends on.
    2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.configureDiskError] reason: the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent matching the child content.
    2012-08 - 05T 20: 00:06.035Z | VMX |

    Thanks again for any direction you can provide!

    / r

    John

    The parentCID of the snapshot must match the CID from its parent, as shown in the log file

    "... The content ID mismatch (parentCID f72e60c7! = f05537b3)... »

    Server.VMDK

    CID = f05537b3
    parentCID = ffffffff

    Server - 000001.vmdk

    CID = a2b9ba8b
    parentCID = f72e60c7---> f05537b3

    Make sure you change the file on the host using the vi editor or - if you want to change the file in Windows - use an editor who is aware of the line breaks Unix (do not use Notepad!)

    Once this is done, I highly recommend that you take another cliché before you on the virtual computer. This prevents existing virtual disk files to be modified, so that you can return to this State where you need. After that everything works as expected, consider deleting all snapshots.

    André

  • Additional virtual disk space not usable in Windows

    I resized a virtual disk of virtual machines by changing properties and then used a live CD partitioning tool to resize the partition.  Inside windows disk manager, it shows that the additional disk space as if the size of the Windows partition has been increased with success.  However, when I look at the properties of the hard drive in Windows, the extra size does NOT appear and it is not usable or accessible to the file system.  Any ideas what went wrong and how to fix it?

    Thank you

    I had exactly this before strange point of view and could not explain it. Seemed rather strange that the operating system will appear to display the disk space as allocted but the extra space was not available (even when checking the query WMI etc.)

    Ultimately, however, EXTPart has remedied the problem for me. (and quickly)

    If you do not use EXTPart, you can use the converter to recreate the disk.

  • Reason: The specified virtual disk must be repaired. Running on MAC

    I NEED HELP.

    I'm new to mac and am a nood. I am running the latest version of vmware fusion, os and windows 7.

    So my computer crashed and I had to force stop. VMware was running in time with windows 7, now when I try to run windows 7 I get this:

    Cannot open disk ' / users/user/Documents/Virtual name Machines.localized / 7.vmwarevm/Windows 7.vmdk Windows' or one of the snapshot disks it depends on.

    Reason: The specified virtual disk must be repaired.

    I went online and tried the two ways that forms said to fix, went to the Terminal and tried to fix the vmdk but kept getting the disk must be mounted?, so I tried to use an older version of vmwares support program and that has not worked.

    So I eaither need to know how to fix the vmdk or it go to mount so I don't understand this error, or if there is a way to trasfer my programs which crashed windows to other windows I installed it, (Aso 7)

    the path that you used seems to be badly formatted - use quotation marks around the file names with spaces and do not mix slashes to backslashes

    don't know - this forum software does not display paths well so you can have it is just - just new doublecheck

    _________________________

    VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

    You find me also in the PhD Virtual Backup support team

  • Loss of confusion concerning the data on the virtual disk in VMWare

    The evening

    Excuse the amateurism, but I'm looking for help with a problem I have with a virtual machine.

    I created a Virtual Machine with a virtual disk of fixed size for use as a LAMP (in this case, Ubuntu 9.10) development environment. I have used this in the course of nearly a year and have taken quarterly snapshots, or before, I did something stupid to the BONE. So far we five snapshots and a clone that I got a month ago.

    Recently, I created an another VM to install the configuraiton of LIGHT even on Ubuntu 10.04 (I wanted a new installation).  I didn't know it was a bad idea in time, so I created a second disk on the VM 10.04 and mounted the main drive of the virtual machine 9.04. Obviously, 10.04 altered the disc somehow, as I had received the "+ the Ramdisk parent has changed since the child was.

    created. + "error every time I tried to start it.

    After several unsuccessful attempts to try to find a recent clone, I created a new virtual machine and up from 9.04 virtual disk. However, from the start of this virtual machine, I went back to, what I believe to be, the first State of the virtual machine before snapshots. However, it is also possible that I lost the correct VM while trying to find a recent clone (of course, I hope it's a snapshot problem and not a problem of stupidity).

    My question is, is - it possible that the disc that I mounted does not take into account my snapshots?

    See http://sanbarrow.com/vmdk-errors.html#e4 for an explanation of the error and some tips how to fix it.

    If in doubt ask before doing anything more that could "destroy" the disc.

  • Feature suggestion: virtual disk via USB hot

    I suggested this feature in VMWARE 2 years, I had not seen this be taken seriously. But I insist it is very useful and would it make Workstation & other products much more powerful convinent server for users.

    Essentially now existing virtual disks cannot be ADDED to a virtual machine as an IDE or SCSI drive, this must be done after the virtual machine is stopped. Thus, it is not hot.

    The equvilant material action REAL hot plug is to plug your physical hard drive via a SATA to USB adapter and connect to PC and PC will detect a new USB dive. For a VITURAL Machine, I takes VMWARE to write a function to CONNECT a virtual disk available (all files hard) in a VM running via the USB interface.

    VMplayer and workstations can now connectable to warm physical USB readers of thumb, but not no virtual disks, it's a shame. It would be a feature very very handy and popular because there are so many things, that you can do with it.

    Without this feature, users will have to turn off the virtual machine and fix the existing virtual disks and then after use, turn off again to remove them.

    Attachable to hot only saves a lot of time.

    I mean WHY NOT? VMWARE should really consider this, I hope.

    u.y.

    What guest operating system do you use?

    What version of virtual hardware is configured?

  • Install a second virtual disk

    I currently have a virtual disk (windows vista) installed on my mac, I recently tried to install a second virtual disk (windows xp). However inorder to save hard drive space, I created the external hard drive on a hard disk. Problem is when I pass by windows set up it does not recognize my drive external hard to Setup cannot continue. When I try to connect to my external hard drive, I get an error. I have attached a picture of the error. What can be done to fix this?

    First when you install Windows on a virtual machine to its Virtual Hard Drive Windows only has not to see the physical drive that the Virtual Machine is created or stored on, and more important again when it is an external USB drive it is the storage location of the Virtual Machine itself you should not try to connect to the virtual machine and therefore the message your bet.

    The result is if you run a Virtual Machine that is stored on a USB external drive, the host has control of it and must keep control of it since the merger is accessed under OS X and trying to connect it to the Virtual Machine directly you try to allow Windows to take control of it and you just can't do it because it is already used by OS X and current merger run the Virtual Machine in it.  If it was just a USB external drive that had opened and locked by an application running under OS X or OS X, as the merger then you would have no problem connecting to it and take direct control of OS X.

    So if you need to run a VM on an external drive, then just do it but do not try to take control of the physical device by pulling below the host and in turn merge since it already in direct use by both.

    JSYK I create and run Virtual Machines all the time on external drives and never have a problem installing any OS in the comments that as part of the process and so that the operating system is installed on the virtual machine, there never to see or to exercise a direct control of it nor I ever try to connect directly to the Virtual Machine.

  • Acer Aspire V5 - 572G windows update, net and virtual disk problems.

    So I installed w7 x 64 ultimate on my laptop and notiiced windows update does not work. It shows that he can not connet to the server. After trying to fix it I discovered that I need to install net framework, which I tried, but he also failed because when I download the framework and before I press on install it shows me how much to download and it is 0. After I press on install it loads a little and it is said that he was not successful. Also tried to download some programs, such as driverpack, drivers search for and he found this lack gcdbusdevice and dcbusdevice im. When I tried downlaoding them, they seem not to exist. And when I try to install daemon tools or some simillar programs, it will fail to install, or fails to create a virtual disk, and after that the laptop can not stop lights. I have to use the restore point, and then he turns then on.

    So yes, some advice or help would be nice, thank you.

    Please see this link:
    Installation of a different operating system

    There are no drivers Windows 7 for the V5 - 572G on our page drivers.

    We don't support Windows 7 on this model.

  • MD3000 cannot change virtual disk ownership / preffered path - ERROR 29

    Current configuration

    PowerVault MD3000 (deleted by the moderator) - attached to two servers PowerEdge R610 using Dell SAS 5/e card in each r610. The R610s act as a host ESX VMWare ESXi 5.5.0

    We have created multiple LUNS on the storage array and noticed that traffice all happening through a RAID controller or another module (and it seems to me not change without prompting when you look at the storage Bay). I turned off a two different virtual machines to try to change the path and had an error with a certain delay - I stuck this error below. I also tried to redistribute virtual disks tab the MDSM software nothing works support.

    By reading, it seems that the LUN should be attributed to a particular raid controller before all I / 0, but I still feel like're missing us something as to why we cannot distribute the traffic properly.

    According to some records for a MD3200 -.

    "If the host has a path of data unique to the MD, the virtual disk storage array.
    must be owned by the controller to which the host is connected.
    That's what we're trying to accomplish. I don't know if the hosts are to be physically detached from the SAN, or if there is a bit of software to fail us.
    Thank you in advance! If I failed to provide all the details, please let me know and I'll try to gather the information.
    Here's the error output:

    OPERATING ENVIRONMENT DATA

    Name of the client system: FLMGMT01
    Client OS: Windows Server 2008 R2

    Application version: 03.35.G6.88
    Storage management of version table: 03.35.G6.88
    Name of storage array: VAB-NAS-01
    Firmware version: 07.35.39.64
    Management class: devmgr.v1035api01.Manager

    **************************************************

    DATA ERROR

    Command sent to the RAID controller module to the location: 0
    Host name: 192.168.19.233
    IP address: 192.168.19.233

    Return code: error 29 - this operation cannot complete because there was a failure of authentication of security on a parameter in the command sent to the RAID controller module.

    Try the operation again. If this message persists, contact your Technical Support representative.
    Operation when the error occurred: PROC_assignVolumeOwnership
    Timestamp: August 25, 2014 16:18:59

    DATA BATTERY

    devmgr.v1035api01.Sam.JAL.ManagementOperationFailedException:
    at devmgr.v1035api01.sam.jal.SYMbolClient.dispatchOperation (unknown Source)
    at devmgr.v1035api01.sam.jal.StorageArrayFacade.issueCommand (unknown Source)
    at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommandCommon (unknown Source)
    at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommand (unknown Source)
    at devmgr.v1035api01.sam.jal.StorageArrayFacade.assignVolumeOwnership (unknown Source)
    at devmgr.v1035api01.sam.configuration.controller.ChangeControllerOwnershipDialogPanel.performCommitAction (unknown Source)
    to devmgr.v1035api01.shared.wizard.DialogPanel$ NotifyBackgroundTaskAdapter.performOp (unknown Source)
    at devmgr.v1035api01.shared.AbstractTaskAdapter.run (unknown Source)

    THREAD DATA

    Thread [reference Manager 10, System]
    Thread [finalizer, 8, System]
    Thread [dispatcher Signal, 9, System]
    Thread [attach auditor, 5, System]
    Thread [Java2D grinder, 10, System]
    Thread [TimerQueue, 5, System]
    Thread [Swing-Shell, 6, System]
    Thread [AWT-closure, 5, main]
    Thread [AWT-Windows, 6, main]
    Thread [EventQueueMonitor-ComponentEvtDispatch, 5, main]
    Thread [Thread-3, 5, main]
    Thread [AWT-EventQueue-0, 6, main]
    Thread [DestroyJavaVM, 5, main]
    Thread [SwingWorker-pool-2-wire-1, 5, main]
    Thread [ChangeDetector, 6, main]
    Thread [PreferenceStoreChangeDetector, 6, main]
    Thread [LogMsgThread, 6, main]
    Thread [Np_Link_Monitor0, 6, main]
    Thread [DMVGarbageCollectorThread, 6, main]
    Thread [RecoveryProfile-27, 6, main]
    Thread [NEA-28, 6, main]
    Thread [RecoveryProfile-30, 6, main]
    Thread [NEA-31, 6, main]
    Thread [Timer 0, 6, main]
    Thread [RecoveryProfile-35, 6, main]
    Thread [NEA-36, 6, main]
    Thread [RecoveryProfile-38, 6, main]
    Thread [NEA-39, 6, main]
    Thread [Timer 1, 6, main]
    Thread [Timer 2, 6, main]
    Thread [Timer-3 6, main]


    Thread [RecoveryProfile-48, 6, main]
    Thread [NEA-49, 6, main]
    Thread [Timer-4 6, main]
    Thread [RecoveryProfile-53, 6, main]
    Thread [NEA-54, 6, main]
    Thread [Timer-5 6, main]
    Thread [SwingWorker-pool-2-wire-2, 5, main]
    Thread [RecoveryProfile-69, 6, main]
    Thread [NEA-70, 6, main]
    Thread [Timer-14, 6, main]
    Thread [Timer-91, 6, main]
    Thread [host 2.3, principal of the Image]

    Hello MrRedPants,

    Since you are using a configuration not redundant you will have problems trying to modify the paths between the controllers since the two hosts have only a single connection to the MD3000.  What you could do if possible is to get 2 more SAS cables & connect ports second on the MD to RAID opposite that the host is currently connected to.

    Now, if this isn't an option so that you can make is to have 2 disk groups and assign the virtual disks / LUNS that are connected to each host in their own disk group.  If you go to each host their own groups of disks, then you will need to stop the e/s as you move the Ramdisk to the new group of disks so that you want to discard any data loss.

    Please let us know if you have any other questions.

  • initializing virtual disks

    I have a powervault MD1000 (Bay raid storage) connected to a backup server. It is set up with 3 virtual drives that each use 2 terabytes of storage in RAID 5 from our range of 8 physical disks.

    I had to replace two of the physical drives, and I need to initialize my virtual disks. In the Perc 6/E management screen VD, I can select the virtual disks (that show in red) and press F2 to display the operations, but the initialization button is dimmed and I can't select it. In the PD management screen, the new drives show as ready.

    How do I initialize my virtual drives? Should I delete them and create new virtual disks? It's my first time doing this, so please bear with me. Any help would be appreciated.

    I just updated the firmware of the 6th Perc to version 6.3.3 - 0002, which has a rep to support Dell recommended that I do, if this is useful.

    After you remove virtual drives, I was able to create a new virtual disk and initialize it. It seems that I just have to build the virtual disks from scratch.

    Thank you for your time.

Maybe you are looking for