VMWare: Unable to upgrade Windows Server 2003 32bit to 2008 32bit
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\
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
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\
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
Jeff Perry
From this technet forum posting the last comment states...
ASKER
Thanks, but i dont have Lsicsb.sys
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.ex
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?
Edit: I did notice that your window path is showing x:\windows\system32\cmd.ex
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?
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.
In place upgrades often cause issues and fail.
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.
ASKER
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).
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).
If the server isn't publicly facing, I would personally push for delay until a more permanent migration can be done.
ASKER
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
* 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
1. Spend the time to Implement correctly.
2. Use Active Support contract to fix the BSOD.
2. Use Active Support contract to fix the BSOD.
ASKER
Any thoughts?
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.
ASKER
How do I do option 2 if windows doesn't boot?
Microsoft will guide you.
ASKER
Ok. Thanks.
If no one else has anything to add can a mod delete the question as no one knows the answer.
If no one else has anything to add can a mod delete the question as no one knows the answer.
Did you try a V2V ?
ASKER
V2V resulted in the same issue. Stopping after crcdisk.sys on boot.
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.
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.
ASKER
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.
ASKER
The suggested solution is missing what they did
I've tried switching the controller without any luck.
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.
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.
if you google, there are many faults it would appear upgrading 2003 to 2008, with this same issue as you have reported.
ASKER
I can't upgrade as it hangs at crcdsk.sys. I see lots of people with similar issues. But none of their solutions work.
So this is 2003 server to 2008 server (32 bit).
Does 2003, have any service packs ?
Does 2003, have any service packs ?
ASKER
The 2003 has all it's patches
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...
I have some lab time booked...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
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....
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....
All my servers upgraded fine with no issues.
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
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