Blue Screen ON VM After P2V Conversion of Windows 2000 Server

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!
bvorisAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

za_mkhIT ManagerCommented:
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
bvorisAuthor Commented:
Awesome - Thanks.  I will try this and provide results.
0
Paul SolovyovskySenior IT AdvisorCommented:
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
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

za_mkhIT ManagerCommented:
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
Paul SolovyovskySenior IT AdvisorCommented:
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
S00007359Cloud Engineering OfficerCommented:
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
bvorisAuthor Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
za_mkhIT ManagerCommented:
Good to hear!
0
bvorisAuthor Commented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.