O Windows 2000 Server no VMware Workstation não está inicializando

Question

Estou tentando abrir um servidor Windows 2000 usando o VMware Workstation. parece que não estou tendo todos os arquivos relevantes do ambiente. Eu acho que o servidor foi particionado com 3 partes. Eu não estou tendo o vmdk para a 3ª parte. existem alguns arquivos REDO. Existe alguma maneira eu posso criar o vmdk para a 3ª parte?

Então agora isso dá erro. Agora não tenho o ambiente físico. Então, por favor, ajude e guie é possível recuperar ou fazer este trabalho.

oarquivodelogtinhaoseguinte:

2016-06-24T14:04:07.812+05:30|vmx|I120:hread7925924VMXAIOMGR:Using:simple=Genericunbuf=Compl2016-06-24T14:04:07.822+05:30|vmx|I120:WORKER:CreatingnewgroupwithnumThreads=1(20)2016-06-24T14:04:07.822+05:30|vmx|I120:SNAPSHOT:SnapshotConfigInfoReadEx:Snapshotfailedduetoversionerror:72016-06-24T14:04:07.822+05:30|vmx|I120:SNAPSHOT:SnapshotConfigInfoReadExfailedforfile'OS2000Server.vmx.sav':Snapshotsarenotallowedonthisvirtualmachine(9)2016-06-24T14:04:07.822+05:30|vmx|I120:SNAPSHOT:Snapshot_ListRollingTiersfailed:Snapshotsarenotallowedonthisvirtualmachine(9)2016-06-24T14:04:07.822+05:30|vmx|I120:SnapshotVMX_RollingPowerOn:failedtoinitializerollingsnapshotsSnapshotsarenotallowedonthisvirtualmachine(9)2016-06-24T14:04:07.842+05:30|vmx|I120:DISK:OPENscsi0:0'C:\pr\BAAN\LN6.1FP3\Windows2000Server(2).vmdk'undoableR[.\Windows2000Server(2).vmdk.REDO_a03836]2016-06-24T14:04:07.902+05:30|vmx|I120:DISKLIB-DSCPTR:Opened[0]:"Windows 2000 Server (2).vmdk-s001.REDO_a03836" (0xa)
2016-06-24T14:04:07.942+05:30| vmx| I120: DISKLIB-DSCPTR: Opened [1]: "Windows 2000 Server (2).vmdk-s002.REDO_a03836" (0xa)
2016-06-24T14:04:08.002+05:30| vmx| I120: DISKLIB-DSCPTR: Opened [2]: "Windows 2000 Server (2).vmdk-s003.REDO_a03836" (0xa)
2016-06-24T14:04:08.002+05:30| vmx| I120: AIOWIN32C: Failed to open '.\Windows 2000 Server (2).vmdk-s004.REDO_a03836' : Could not find the file (3).
2016-06-24T14:04:08.002+05:30| vmx| I120: DISKLIB-SPARSE: Opening unbuffered failed; trying Simple.
2016-06-24T14:04:08.002+05:30| vmx| I120: AIOGNRC: Failed to open '.\Windows 2000 Server (2).vmdk-s004.REDO_a03836' : Could not find the file (600000003) (0x3).
2016-06-24T14:04:08.002+05:30| vmx| I120: DISKLIB-SPARSE: ".\Windows 2000 Server (2).vmdk-s004.REDO_a03836" : failed to open (25): AIOMgr_Open failed
2016-06-24T14:04:08.132+05:30| vmx| I120: DISKLIB-LINK  : ".\Windows 2000 Server (2).vmdk.REDO_a03836" : failed to open (The system cannot find the file specified).  
2016-06-24T14:04:08.132+05:30| vmx| I120: DISKLIB-CHAIN : ".\Windows 2000 Server (2).vmdk.REDO_a03836" : failed to open (The system cannot find the file specified).
2016-06-24T14:04:08.132+05:30| vmx| I120: DISKLIB-LIB   : Failed to open '.\Windows 2000 Server (2).vmdk.REDO_a03836' with flags 0xa The system cannot find the file specified (25).
2016-06-24T14:04:08.132+05:30| vmx| I120: DISK: Failed to open disk '.\Windows 2000 Server (2).vmdk.REDO_a03836' : The system cannot find the file specified (25) 5456.
2016-06-24T14:04:08.132+05:30| vmx| I120: Msg_Post: Error
2016-06-24T14:04:08.132+05:30| vmx| I120: [msg.disk.fileNotFound] VMware Player cannot find the virtual disk ".\Windows 2000 Server (2).vmdk.REDO_a03836". Verify the path is valid and try again.
2016-06-24T14:04:08.132+05:30| vmx| I120: [msg.disk.noBackEnd2] Cannot open either the disk 'C:\pr\BAAN\LN6.1FP3\Windows 2000 Server (2).vmdk' or the redo log '.\Windows 2000 Server (2).vmdk.REDO_a03836'.
2016-06-24T14:04:08.132+05:30| vmx| I120: [msg.disk.configureDiskError] Reason: The system cannot find the file specified.
2016-06-24T14:04:08.132+05:30| vmx| I120: ----------------------------------------
2016-06-24T14:04:28.093+05:30| vmx| I120: Module DiskEarly power on failed.
2016-06-24T14:04:28.093+05:30| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0
2016-06-24T14:04:28.093+05:30| vmx| I120: SNAPSHOT: SnapshotConfigInfoReadEx: Snapshot failed due to version error: 7
2016-06-24T14:04:28.093+05:30| vmx| I120: SNAPSHOT: SnapshotConfigInfoReadEx failed for file 'C:\pr\BAAN\LN6.1FP3\OS 2000 Server.vmx.sav': Snapshots are not allowed on this virtual machine (9)
2016-06-24T14:04:28.093+05:30| vmx| I120: SNAPSHOT: Snapshot_TimeStampTiers failed: Snapshots are not allowed on this virtual machine (9)
2016-06-24T14:04:28.093+05:30| vmx| I120: SnapshotVMX_RollingPowerOff: Failed to timestamp rolling tiers at power off: Snapshots are not allowed on this virtual machine (9)
2016-06-24T14:04:28.093+05:30| vmx| I120: AIOWIN32C: asyncOps=0 syncOps=48 bufSize=0Kb fixedOps=0 sgOps=24 sgOn=1
2016-06-24T14:04:28.103+05:30| aioCompletion| I120: AIO thread processed 0 completions
2016-06-24T14:04:28.103+05:30| vmx| I120: AIOWIN32: asyncOps=0 syncOps=0 bufSize=0Kb delayed=0 fixed=0 sgOp=0 sgOn=1
2016-06-24T14:04:28.183+05:30| vmx| I120: WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
2016-06-24T14:04:28.183+05:30| WinNotifyThread| I120: WinNotify thread exiting
2016-06-24T14:04:28.193+05:30| vmx| I120: Vix: [6036 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2016-06-24T14:04:28.193+05:30| vmx| I120: Vix: [6036 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2016-06-24T14:04:28.193+05:30| vmx| I120: Transitioned vmx/execState/val to poweredOff
2016-06-24T14:04:28.203+05:30| vmx| I120: Vix: [6036 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0
2016-06-24T14:04:28.203+05:30| vmx| I120: Vix: [6036 mainDispatch.c:4106]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error
2016-06-24T14:04:28.203+05:30| vmx| I120: VMX idle exit
2016-06-24T14:04:28.203+05:30| vmx| I120: VMIOP: Exit
2016-06-24T14:04:28.203+05:30| vmx| I120: Vix: [6036 mainDispatch.c:869]: VMAutomation_LateShutdown()
2016-06-24T14:04:28.203+05:30| vmx| I120: Vix: [6036 mainDispatch.c:819]: VMAutomationCloseListenerSocket. Closing listener socket.
2016-06-24T14:04:28.203+05:30| vmx| I120: Flushing VMX VMDB connections
2016-06-24T14:04:28.203+05:30| vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2016-06-24T14:04:28.203+05:30| vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
2016-06-24T14:04:28.213+05:30| vmx| I120: VMX exit (0).
2016-06-24T14:04:28.213+05:30| vmx| I120: AIOMGR-S : stat o=1 r=3 w=0 i=0 br=49152 bw=0
2016-06-24T14:04:28.213+05:30| vmx| I120: FileTrack_Exit: done

    

Answer 1

Os arquivos Refazer são configurados para o tipo de disco diferencial (por exemplo, você tem um disco VMDK de origem "bloqueado" e uma ou mais máquinas virtuais que usam isso como uma fonte e gravam suas "alterações" no arquivo Refazer e não no vmdk .

O erro que você está vendo sugere que a BIOS da máquina virtual está configurada para inicializar somente a partir da rede e não está encontrando uma origem para inicializar na rede.

Então ...

• Verifique se as unidades virtuais estão corretamente conectadas nas configurações da VM.
• Verifique se o BIOS do convidado virtual pode ver o disco rígido e se está configurado para inicializar a partir dele.

Se você realmente perdeu os arquivos VMDK para qualquer máquina virtual, então você é escolhido.