Error 'select virtual disk format.

Similar Questions

• Current virtual disk format

  How can I check the current disk for a virtual machine format?  I have a model I want to build it, but I want to make sure you that I respect another virtual machine disk format.  I want to check the other VM to see which of these options below has been selected.

  Same format as the source

  Zero lazy stocked thickness

  Zero eager stocked thickness

  Provision of thin

  Thank you

  Click with the right button on the virtual machine and then click on change settings. Click on the vmdk and look to the right where it says disk Provisioning. The Type field will tell you the kind of vmdk is.

• What are the steps to create, format and install a new virtual disk in Windows

  I swear I've scoured the Internet for days trying to find the details of this process, and I'm embarrassed to have failed in my quest to understand what I must be a very simple thing.  The best I can do is this:

  Step 1: Create a new vmdk using vmware-vdiskmanager

  Step 2:?

  Step 3: Get your vmdk newly formatted using vmware-mount, or using "Map Virtual Disk" of the Workstation option

  Now, you will see that somewhere between step 1 and 3, it is an essential step of the new vmdk format so that it can be recognized and mounted.  Simply, I can't find any example online how to do this.  I just know someone will say "just attach to a virtual machine and format her", to which my answer is "how?  It won't let me get an unformatted disk.  When I try to go directly to step 3 after step 1, I get the following error, "error reading volume information.  Please select another file to disk.

  Help!

  VM--> change the settings.

  Hardware tab.

  Add the button.

  Select "hard drive".  Follow the instructions in the wizard.  At the selection of create new floppy or use existing, select "Use an existing virtual disk" and find the vmdk file, you have created.

• The virtual disk is either corrupt or not a format supported.

  We have a 2008 R2 SP1 VM Datacenter we cannot snapshot.

  A manual snapshot of in the Client vSphere indicates the following in the tasks and events:

  The virtual disk is either corrupt or not a format supported.

  Our NetBackup software is automatic snapshots for VM backups and generates these three errors in the tasks and events:

  Cannot run a snapshot operation
  

  Operation timed out
  

  A general error occurred: VMX protocol error.

  The virtual machine has two virtual disks:

  [vmds-standard: (1) default] outhostname/ourhostname - 000001.vmdk

  [vmds-standard: (1) default] outhostname/outhostname_1 - 000001.vmdk

  Virtual disk files seem to be the usual file names. Instead, they resemble snapshot files or something similar.

  I don't know what is happening. Can anyone help?

  The file names are correct, since there is an active snapshot on the virtual computer. I found a few entries in the log file that we/you can see:

  08:01:25.543 Mar 23: vmx | DICT scsi0:2.deviceType = scsi-disk hard
  08:01:25.543 Mar 23: vmx | DICT scsi0:3.deviceType = scsi-disk hard

  There are some entries of old/orphaned for already deleted virtual disks! However, it should ask the question.

  21:13:06.212 25 March: vmx | In SUMMARY: SnapshotBranch failed: changes, followed by target file already exists (5).

  That's what I think is related to the question. For me, it looks like a problem once with block change tracking, which may have left orphans. What I would do, is first of all to delete all the .ctk files in the folder of the virtual machine on the data store (they will be recreated, only the next incremental/differential backup will take more time). If this is not enough, you can try to disable - at least temporarily - CBT for the virtual machine or remove the virtual machine to inventory, delete the .ctk files and then add it to the inventory...

  André

• Dual Boot with windows XP Pro with 2 HARD drive, error on secondary windows install: "Windows did not start because of a configuration of the disk of the computer problem. Could not read the selected boot disk. Check boot path and disk hardware... »

  Hi, I recently bought a new Hitachi 1 TB internal hard drive. I wanted to do a clean install on the new drive (d), be able to dual boot my computer and leave my old 300 GB disk (C :) as the primary windows installation. After physically installing the new HARD drive, I noticed that "new hardware found" and the the brand name flashed in the bottom right corner. I thought I'd see the new hard drive in my computer, but I did not. I initialized the new HARD drive with the computer management window (right click on my computer - manage) and I also formatted in NTFS (I had to change my printer hard drive letter to assign the new HARD drive with the letter D, but I've made other changes after this step). Now, I could see and use in my main windows on the C: installation. I then installed a windows new copy XP pro with the installation CD I got for my C: but on the D: (Note: I have a Dell computer (and the Dell reinstallation CD) and my current version of windows has SP3 while the installation CD is only SP2) (I also reformatted my HARD drive during the installation of windows to NTFS)

  Now when I try to start on installing the new on my D: I get "Windows did not start because of a configuration of the disk of the computer problem. Could not read the selected boot disk. Check startup disk and hardware access path. "and another line saying to refer to manuals HARD drive and windows.

  My Boot.ini file at this time was:

  [boot loader]
  Timeout = 5
  default = multi (0) disk (0) rdisk (0) partition (2) \WINDOWS
  [operating systems]
  "multi (0) disk (0) rdisk (0) partition (2) \WINDOWS="Microsoft Windows XP Professional "/ noexecute = optin/fastdetect
  "signature (ac516a5c) disk (0) rdisk (0) partition (1) \WINDOWS="Microsoft Windows XP Professional own "/ noexecute = optin/fastdetect

  I looked towards the top of this help page, but for now I'm unlucky:

  http://support.Microsoft.com/kb/314477

  (The next steps I took by throwing from the Windows CD and go into the repair console)

  I tried to use the bootcfg /rebuild but the line to boot.ini for my secondary HARD drive still does not work.

  He gave me something like:

  [boot loader]
  Timeout = 5
  default = multi (0) disk (0) rdisk (0) partition (2) \WINDOWS
  [operating systems]
  "multi (0) disk (0) rdisk (0) partition (2) \WINDOWS="Microsoft Windows XP Professional "/ noexecute = optin/fastdetect
  "signature (ac516a5c) disk (0) rdisk (1) partition (1) \WINDOWS="Microsoft Windows XP Professional own "/ noexecute = optin/fastdetect

  I also tried to change the signature() to multi (0), but it did not work. (or try almost all possible permutations of disk() and rdisk() partition() 0 to 2).

  I also tried to use expand F(dvd-drive):\i386\ntkrnlmp(I_have_a_duo-core).ex_ D:\windows\system32\ntoskrnl.exe and a few other combinations, but I when I login as D:\windows simply, it fails to extend with a message like "could not develop" or C:\windows I get "restricted access".

  I have not yet tried CHKDSK/r, but since I did a clean install on a newly formatted drive... I don't think it would work.

  I've also marked the partition on the D: as active (in computer management), but it did not help me.

  I've done a first installation of windows repair, strangely, I couldn't fix this one... Still does not work...

  My default windows installation yet works very well & I see that windows has been installed on the D: but I'm ideas from how to operate the dual-boot, can someone throw me a BONE on what to do?

  Maybe try to do something with the Boot Manager (whatever it is?) Create a new partition and use it as a boot manager? I don't really want to do this, because if I made a mistake I will be unable to use my computer and dual boot should work without going through all this trouble... But I found this page: http://technet.microsoft.com/fr-fr/library/ee829686%28WS.10%29.aspx

  Could a clean install two HDD help? I hope I won't have to do...

  Someone has an idea?

  PS: I'm not such an advanced user so I need a solution step by step, thanks!

  Edit: I also noted that I can't see my new HARD drive in my BIOS... weird... SATA-0 is my old drive HARD 1 and 2 are my dvd 3-5 readers are 'off' and it doesn't seem to be anything that it is plugged in. I also have 4 bays for internal HARD disks. Now, 2 are busy.

  Edit2: I looked inside my case and enabled the good Sata in the Bios after a reboot it detected the drive correctly. Dual boot doesn't always work well... The fact that it was disable in the BIOS while I was installing the new HARD drive could change anything? Hmm...

  In case I wasn't clear enough: I had a windows XP Pro installed on my C:, bought a new hard drive and installed the same copy of windows on it (d). I think that should allow me to double boot between the two installs different. Even if for some reason I can't boot from one on my D:. Andrew, I do not understand why you so far physically disconnect the other drive, the point of the whole operation is to build a boot.ini file so that the BIOS knows that it y facilities 2 windows and you allow to choose (and not have conflicting problems between the 2 systems), someone correct me if I'm wrong? "Expand" the part of my first post made reference to one of the solutions provided by Microsoft in the first link that I have included in my previous post (but I can't seem to work).

  In addition, it is the procedure that I followed: http://www.ehow.com/how_5950826_boot-two-different-hard-drives.html

  (except I've had the first installation already done).

  Andrew "also, once a new hd is plugged on the pc & running, most of the BIOS will place (them) as 1st priority hd, set the BIOS to do this", you mean that by installing separately from windows on each unit when the other is not plugged in, I could choose what disk to start from defining their priority in the BIOS once they are all plugged back? It's too tedious (as I intend to move frequently between the 2 installs) and requires a computer to other users of the lack of computer knowledge. Unfortunately, it is not a viable option.

  EDIT: I DID IT! Hmmm... Well, I double checked in the recovery console, the path of the new HARD drive with the arc command Scan. Tried to start again with the MULTI (0) in my boot.ini and it worked... I also had my windows install CD in. Maybe that is why I could not start, windows needs the CD to complete the installation? Weird, I don't know what I did to the difficulty it... but hey, it works! Thanks for your ideas guys!

• My computer won't allow me to access my files on my portable hard disk without error appear "you must format the E: drive before using it. How can I fix this please!

  My computer won't allow me to access my files on my portable hard disk without error appear "you must format the E: drive before using it. How can I fix this please!

  Try to scan your driver with anti-virus, also try to throw the disc looking for this driver and as you try to run the following tools:

  http://support.Microsoft.com/mats/system_maintenance_for_windows/

  http://support.Microsoft.com/mats/windows_file_and_folder_diag/

• 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.

• When running Disk Management, get the error - failed to connect to the virtual disk Service.

  When I run the Snap on the local server disk management, I get an error message in the status bar: unable to connect to the virtual disk Service.

  Thanks, I have tried these things and nothing has solved the problem.  Here's what I did:

  (a) check the VDS service was manual and failures later per second are 'take no action '.
  ANSWER: Yes to manual and following, second has not changed to "restart the service" of "non-action".
   
  (b) sfc/scannow as administrator
  ANSWER: the System File Checker has found no problem (program reported no problem and findstr/c: "[SR]" on CBS.log doesn't have the list of issues)

  (c) restore to a previous system restore point
  ANSWER: I have tried restore points several more early, each of them failed

• Impossible to P2V Windows 2003 x 64 server - an error occurred while opening a virtual disk

  Hello.

  I have a physical Windows Server 2003 x 64 R2 Standard and try to convert it to vSphere with vCenter Converter Standalone 5.5.0 VM 5.5.

  When I start the task, VM is created on vSphere, but after a few seconds machine is removed and task collapsed with messages: "year error occurred opening a virtual disk." "Make sure the server Converter and source computer have a network access to hosts esx/esxi source and destination.

  There are no problems with access to the network, I check.

  I tried many things (disable SSL on the server Converter, converter running directly on the source machine, see providers vss on source...) but without success.

  Any idea is welcome.

  Thank you.

  Ante

  Please check if Windows Server is able to resolve the name of the ESXi host. If DNS does not work, add the ESXi host (s) of Windows server hosts file destination.

  André

• popular error; An error occurred when opening a virtual disk. Make sure that the converter server and source running machines have network access to the ESX/ESXi hosts source and destination.

  Once again; same problem, others have encountered but nothing seems to work.

  An error occurred when opening a virtual disk. Make sure that the converter server and source running machines have network access to the ESX/ESXi hosts source and destination.

  We have 1 physical servers, we need to see. Here is the environment. All 3 separated location, 3 all firewall separated

  1 physical servers

  -Internal IP address; 172.16.160.21
  -FARM Firewall

  vCenter Server

  -Internal IP address; 172.16.1.85

  -Local Office (ALX)

  Location of destination (ESXi host):

  -Internal IP address; 172.16.153.20

  -Firewall ROOMMATE

  
  Already completed:

  VMware KB: disable SSL on VMware Converter Standalone 5.x encryption   SSL disabled in converter-worker

  Firewall are open / Tunnel is open throughout the environment.

  I have attached the logs.

  Thank you very much

  POCEH; Thanks for the reply. But I wouldn't be pulling my gray hair if I knew what the problem was. I understand that there not for the peer but why...?

• Converter does not have "an error occurred when opening a virtual disk. Verify that the Converter server and source running machines have network access to the ESX/ESXi hosts source and destination. »

  Hi all

  I'm having some trouble converting server physical windows using autonomous vConverter 5.5.

  error message:

  "An error occurred when opening a virtual disk. Verify that the Converter server and source running machines have network access to the ESX/ESXi hosts source and destination. "

  I have attached the bundle newspapers. Please notify.

  See you soon...

  Your error is:

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 info "Default"] GetManagedDiskName: Get disklib file name as vpxa-nfcssl: / / [a0110-vmgt70-001] WIN-MOVRCVCSITG/WIN-MOVRCVCSITG.vmdk@a0110tesxhyp01.datacenter.telenorservices.com: 902! 2 b 52 87 75 03 03 ff 49-67 2f 3 a 61 76 and 00 cd e1

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 WARNING 'Default'] [, 0] NfcNewAuthdConnectionEx [NFC ERROR]: unable to connect to peer. Error: Failed to search for host for a0110tesxhyp01.datacenter.telenorservices.com server address: the requested name is valid, but no data of the requested type was found

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 info "Default"] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code: 2338)

  Check the manual on the required ports.

  HTH

• 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é

• I tried to convert a virtual disk in Extensible with vmware-vdiskmanager, but an error...

  Hello

  I tried to convert a virtual disk in Extensible with vmware-vdiskmanager, but an error...

  

  ' Could not convert the drive: the system cannot find the specified file < 0 x 1900000004 >. '

  No idea what lack us.

  I read a few threads on this subject and they say to delete all snapshots. Don't have any as soon as I used the vmrun program to list all snapshots for this virtual machine and it returned 0.

  can someone help me with this?

  Thanks in advance,

  Rui

  It seems that there is typo in the file extensions of the virtual disk, i.e. '.vdmk' instead of 'hard '!

  André

• How to resolve the error "the specified file is not a virtual disk?

  Hello - I have a ubuntu/linux host running vmware 1.08 with a SBS2003 VM that recently ran out of physical space in HD. After adding a new drive hard I know to get a specified file is not a virtual disk on one disk error I try to add - the other 3 work. After looking around here, I checked the file descriptor and it seems in good condition.

  My paper does not help because I can not start the virtual machine with the hard drive, I need.

  What are some solutions that I can try?

  Thanks for any help!

  B.

  Unfortunately, you lost the data of zero bytes hard snapshot files. I hope that you don't have a backup of your data, since the snapshot was created in January!

  To be able to feed the virtual machine - even with the disk data corruption - replace zero files hard bytes per who has 327680 bytes, which is essentially an empty file with only the metadata.

  André

  PS: as mentioned earlier, please save the files until you turn on the virtual computer to be able to return to the current status in case you should!

• VMDKMounter gets error "could not open the virtual disk.

  I have two Win7 x 64 virtual machines running fine with VMware Fusion 4.1.2.  I installed VMDKMounter from VMware 3.1.3 and OSXFuse 2.3.9.  I can ride one of the files hard with VMDKMounter very well, but others told "Cannot open the virtual disk" when I try to mount it.

  8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: could not parse the instant string ' / Users/finchr/Documents/VirtualMachines.localized/hoth.univ.dir.wwu.edu.vmwarevm/hoth.univ.dir.wwu.edu.vmx '. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: will not be able to take an informed decision, based on partial information. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: mount the drive read-only instead. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: failed to open the disc: disc encoding error (261993021117)

  The virtual machine that VMDKMounter fails to mount was created by VMware vCenter Converter 5.0 of a physical machine.  The virtual machine that works was created in VMware Fusion 4.

  Of course, the hard I really want to ride with VMDKMounter is he who fails.  No idea how to make so that he can get?

  Well, I see nothing in the disc DescriptorFile which prevents the hard mounted.

  So right now, you can mount other hard files, but not this one, then I have two suggestions...

  It would be to use vmware-vdiskmanager to create a new hard that will not go up and the other would create a new empty hard, then add it to a virtual machine, as well as one that will not go up and then start with appropriate optical disk or an ISO Image containing the appropriate tools/utilities in order to image the drive to the new empty.  I usually use Symantec Norton Ghost for operations like this.  Then maybe a new mounts with VMDKMounter.