VMWare: Unable to upgrade Windows Server 2003 32bit to 2008 32bit

detox1978
detox1978 used Ask the Experts™
on
Hi All,

I need to do an in-place upgrade on a Windows 2003 32bit server.

I have the 2008 32bit dvd and it appears to install without issue.  But it hangs when the operating system gets to the green loading bar (looks like a caterpillar).

In safe mode it gets upto;

Loaded:  \Windows\system32\drivers\crcdsk.sys

Reading a couple of posts I thought swapping the BusLogic controller to a LSI Logic SAS would help, but it hasnt.

Some extra info:  I suspect the original server was P2V'd and the ESX version is 5.5


Any suggestions
D
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Jeff PerryWindows Administrator

Commented:
From this technet forum posting the last comment states...
For anyone doing an in place upgrade of a Virtual server on VMWare (not sure if the same applies to Hyper-V) if the boot process hangs and then in safe mode it seem to hang on crcdisk.sys.  Boot from the Windows 2008 DVD and go to Recovery and then a CMD and delete the following file from C:\windows\system32\drivers\Lsicsb.sys and then reboot as normal and the upgrade will continue.  Lsicsb.sys is a legacy driver that isn't needed.

Author

Commented:
Thanks, but i dont have Lsicsb.sys

system32 files
Jeff PerryWindows Administrator

Commented:
Interesting, it was such a close match I thought it would be a solution.

Edit: I did notice that your window path is showing x:\windows\system32\cmd.exe the quoted text says the file is in c:\windows\system32\drivers\

It has been a while since I have messed with 2003 \ 2008 but isn't the x: drive the upgrade source and not the destination?
Ensure you’re charging the right price for your IT

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

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Is there really a reason WHY you are trying an in place upgrade to another legacy OS (and 32 bit ?)

In place upgrades often cause issues and fail.
kevinhsiehNetwork Engineer

Commented:
Is this just a stopgap measure? Even 2008 goes end of support in 16 months, which will leave 2008 almost as insecure as 2003 is now. IMHO it makes much more sense to get whatever you have the old 2003 server doing to at least Windows 2012 R2, if not 2016.

Author

Commented:
I totally understand your point.  The in-place upgrade is not my preferred solution.  But I've been asked to upgrade all 2003 servers to 2008 (or above) to retain a couple of our certifications  (2008 R1 is still under extended support until 2020).

I've done clean build on the servers that are documented (or fairly straight forward).  But there are two left that will take several months of planning.

So the in place upgrade is only a short term stop gap, while the services it hosts are replaced by a new vendor (on a new server).
kevinhsiehNetwork Engineer

Commented:
If the server isn't publicly facing, I would personally push for delay until a more permanent migration can be done.

Author

Commented:
All operating systems need to have an active support contract is an audit requirement, so 2003 is a non starter.  The options i have are;

* rush in two systems without proper research or implementation
* Apply an in-place upgrade to buy a couple of extra months to research the replacement systems
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
1. Spend the time to Implement correctly.

2. Use Active Support contract to fix the BSOD.

Author

Commented:
Any thoughts?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
other than what I posted, you could try and perform a V2V (VMware Converter conversion), sometimes a conversion to correct hardware can fix faults, but if the fault already exists in the registry, it will not be undone.

Author

Commented:
How do I do option 2 if windows doesn't boot?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Microsoft will guide you.

Author

Commented:
Ok.  Thanks.

If no one else has anything to add can a mod delete the question as no one knows the answer.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Did you try a V2V ?

Author

Commented:
V2V resulted in the same issue.  Stopping after crcdisk.sys on boot.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
If the fault is bad enough, faults can be carried across into the VM.

If this is important to get this migrated, you will need to reach out to Microsoft, or Request Assistance, and get more Experts to Assist.

Author

Commented:
The server has no issues.  I just need the OS upgrading, but it fails.  crcdsk.sys engages the hardrive.  Microsoft won't fix a hardware issue.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:

Author

Commented:
The suggested solution is missing what they did

I had to do some registry changes (system32\config\...) and rebooting few times, which upgraded kind of successfully

I've tried switching the controller without any luck.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
So all working now... or not ?

if you google, there are many faults it would appear upgrading 2003 to 2008, with this same issue as you have reported.

Author

Commented:
I can't upgrade as it hangs at crcdsk.sys. I see lots of people with similar issues.  But none of their solutions work.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
So this is 2003 server to 2008 server (32 bit).

Does 2003, have any service packs ?

Author

Commented:
The 2003 has all it's patches
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
I'm intrigued to have a look at this, and upgrade some of our older 2003 servers to 2008, and see what happens.

I have some lab time booked...
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
I've been looking at this today.... and fall into a Gotcha...

Windows Powershell 1.0...

WIndows 2008 In-place upgrade will not Proceed if Windows Powershell 1.0 is installed, but Windows Powershell 1.0 was included with 2003 SP1.

and if you upgrade to SP2, it cannot be uninstalled..

You cannot install Windows PowerShell 1.0 if it is already installed. To determine whether Windows PowerShell 1.0 is installed, locate the Installregistry entry in the following registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Powershell\1\Install
If the value of the Install entry is 1, Windows PowerShell 1.0 is installed. If the Install entry is not present, Windows PowerShell 1.0 is not installed.

If you install Windows PowerShell 1.0 on Windows Server 2003 with Service Pack 1, and then upgrade to Windows Server 2003 with Service Pack 2, you cannot uninstall Windows PowerShell 1.0. Because Windows PowerShell is packaged as a Windows update, uninstalling Windows PowerShell after you apply a service pack is considered uninstalling out of the prescribed order.For more information, click the following article number to view the article in the Microsoft Knowledge Base:


also listed here on EE

https://www.experts-exchange.com/questions/27029014/Upgrading-to-Windows-2K8.html

issue is, if you start ripping out Updates to get round the Powershell, you may end up with unstable 2003/2008 enviornment.

Author

Commented:
I just renamed the powershell folder to get past the check.  Could that cause the crcdsk.sys issue?

I setup a new 2003 server install sp1 and it upgraded no problem to 2008.  So I'm somewhat perplexed.  The age of the server suggests it was p2v'd
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Not sure, I checking....

I also renamed the Powershell folder to get round the Compatibility Check.....

Got three here to do...

1. Physical Server.
2. Physical Server P2Ved to VM.
3. New VM with 2003 installed.

All the above have SP2 installed....

Upgrades is running at present....
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
All my servers upgraded fine with no issues.
Seth SimmonsSr. Systems Administrator

Commented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: Andrew Hancock (VMware vExpert / EE MVE^2) (https:#a42691816)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial