服务器 Gind.cn
  1. 服务器 Gind.cn
  3. VMware Workstation上的Windows 2000 Server不启动
Intereting Posts
可达主机的“networking名称无法find” ls | grep正则expression式，忽略.tab文件， 如何在AWS-IAM中添加特定的CloudFormation，EC2，RDS和S3访问限制 创build一个公共SQL Server 闲置VMware来宾资源消耗 允许自定义代码的SharePoint（MOSS）托pipe 安全的L2连接 configuration无损的Amazon S3存储桶策略 Windows Server中的邮件实用程序（与Linuz邮件相同的function） OpenSource PKI解决scheme：用户反馈和build议 我怎样才能debugging一个悬挂的SSH连接？ ProxyPass指令中是否可以使用基于身份validation的远程用户名进行插值？ 运行后台作业在集群环境中 Nginx的，如何设置fastcgi_index为几个值？ 为什么不这个.htaccess文件工作？

VMware Workstation上的Windows 2000 Server不启动

我正在尝试使用VMware Workstation打开Windows 2000服务器。 看来我没有环境的所有相关文件。 我猜服务器是用3个部分分区的。 我没有第三部分的vmdk。 有一些REDO文件。 无论如何，我可以创build第三部分的vmdk吗？

所以现在它给错误。 现在我没有物理环境。 所以请帮助和指导是否有可能恢复或做这项工作。

图片

日志文件有以下内容： 

2016-06-24T14:04:07.812+05:30| vmx| I120: hread 792 5924VMXAIOMGR: Using: simple=Generic unbuf=Compl 2016-06-24T14:04:07.822+05:30| vmx| I120: WORKER: Creating new group with numThreads=1 (20) 2016-06-24T14:04:07.822+05:30| vmx| I120: SNAPSHOT: SnapshotConfigInfoReadEx: Snapshot failed due to version error: 7 2016-06-24T14:04:07.822+05:30| vmx| I120: SNAPSHOT: SnapshotConfigInfoReadEx failed for file 'OS 2000 Server.vmx.sav': Snapshots are not allowed on this virtual machine (9) 2016-06-24T14:04:07.822+05:30| vmx| I120: SNAPSHOT: Snapshot_ListRollingTiers failed: Snapshots are not allowed on this virtual machine (9) 2016-06-24T14:04:07.822+05:30| vmx| I120: SnapshotVMX_RollingPowerOn: failed to initialize rolling snapshots Snapshots are not allowed on this virtual machine (9) 2016-06-24T14:04:07.842+05:30| vmx| I120: DISK: OPEN scsi0:0 'C:\pr\BAAN\LN6.1FP3\Windows 2000 Server (2).vmdk' undoable R[.\Windows 2000 Server (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

重做文件设置为差异磁盘types的东西（例如，你有一个“locking”的源VMDK磁盘和一个或多个虚拟机，使用它作为一个来源，并写入他们的改变到重做文件，而不是vmdk。

您在那里看到的错误表明，虚拟机的BIOS设置为仅从networking引导，并且没有find从networking上引导的源。

所以…

  • 检查VM设置中的虚拟驱动器是否正确安装。
  • 检查虚拟客户端上的BIOS是否可以看到硬盘，并将其设置为从其启动。

如果你实际上已经丢失了任何虚拟机的VMDK文件，那么你就会崩溃。