Solved

Blue Screen ON VM After P2V Conversion of Windows 2000 Server

Posted on 2009-07-08
9
4,274 Views
Last Modified: 2012-05-07
Hello,
Upon boot up of VM after conversion - I get a blue screen with the following error:

STOP: 0x0000001E
Address 804A1C07 baes t 80400000 - ntoskrnl.exe

The physical machine I am converting is an old Compaq Proliant 800 Server with three 18.2 gb ultra scsi 3 drives.

The ESX host is a Dell 2950.

I had the same issue with another similiar server, but i fixed it by changing the SCSI host adapter type from Bus Logic to LSI.  

I tried that for this server, but the only thing that happens is the blue screen changes from the error above to "inaccessable boot device".

Thank you for your help!
0
Comment
Question by:bvoris
  • 3
  • 3
  • 2
  • +1
9 Comments
 
LVL 21

Assisted Solution

by:za_mkh
za_mkh earned 360 total points
ID: 24805984
This is a known problem with P2Ving a Windows 2000 box.
Check this link out for how to solve it..
http://communities.vmware.com/thread/206168?tstart=0
 
0
 

Author Comment

by:bvoris
ID: 24806024
Awesome - Thanks.  I will try this and provide results.
0
 
LVL 42

Assisted Solution

by:paulsolov
paulsolov earned 120 total points
ID: 24806976
For Windows 2000 box you'll need to ensure that you have SP4 and SP4 rollup package, otherwise lots of issues.  If you want an easy way to do this download Symantec Backup Exec System Recovery Server trial copy, install on the server and image.  Use vConverter to convert image to the ESX server, it knows about it natively and is usually seemless
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 21

Assisted Solution

by:za_mkh
za_mkh earned 360 total points
ID: 24807943
Pausolov, we had the same issue, with SP4 and the SP4 rollup package. When we experienced it, I seemed to recall that the issue was due to the driver in a post Rollup hotfix causing the issue, hence reverting back to the rollup version .. but my memory is sometimes poor!
0
 
LVL 42

Assisted Solution

by:paulsolov
paulsolov earned 120 total points
ID: 24807964
I've had issues when the sp4 wasn't installed but try to avoid doing Windows 2000 servers directly.  Imaging via acronis or BESR and using vconverter works 99% of the time and avoids customer complaints.
0
 
LVL 12

Assisted Solution

by:S00007359
S00007359 earned 20 total points
ID: 24810562
Also, doing a backup of the old server using the ShadowProtect 3.0 and then doing a Hardware independent restore into a VM, or using a convertor to convert the shadowprotect backup image into a Vm works 100%. Please note that shadowprotect images are now officually supported by VMware.

Thanks
S00007359
0
 

Accepted Solution

by:
bvoris earned 0 total points
ID: 24814753
All,

Thank you for the responses to the question.

What fixed the issue was the info initially provided by za_mkh.

However - the only thing that I did to fix it was downloaded the SP4 rollup, installed in on the Windows 2000 server and reran the VConvertor to do a P2V conversion.  It fired right up - no problems.

I did the same for 3 other W2K servers that were giving me fits after P2Ving them and they all worked.

Thanks a bunch.



http://www.microsoft.com/downloads/details.aspx?FamilyId=B54730CF-8850-4531-B52B-BF28B324C662&displaylang=en&displaylang=en
0
 
LVL 21

Expert Comment

by:za_mkh
ID: 24814787
Good to hear!
0
 

Author Comment

by:bvoris
ID: 24814794
All,

Thank you for the responses to the question.

What fixed the issue was the info initially provided by za_mkh.

However - the only thing that I did to fix it was downloaded the SP4 rollup, installed in on the Windows 2000 server and reran the VConvertor to do a P2V conversion.  It fired right up - no problems.

I did the same for 3 other W2K servers that were giving me fits after P2Ving them and they all worked.

Thanks a bunch.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question