Move Windows OS from one platform to another
-
So many of you have already seen my other thread about P2V, but I want to take a crack at this from another angle.
Let's remove virtualization from the question and pretend that I'm trying to restore and image backup on a new server. The new server will of course have a new RAID controller - so what tools do I use to slip in the new drivers and possibly remove the old ones?
At boot I'm getting BSOD 0x0000007B (0xFFFFF880009AE7E8, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)
https://i.imgur.com/7cGIKoD.png
For those finding this in internet searches, there is a solution below.
-
With Server 2008 (SBS 2008 technically), I used Windows Backup many many times. It just worked.
I have no idea what tools Server 2012R2 and 2016 have built in.
-
In most cases, RAID drivers are included. It's been a long time since I needed to add one.
-
@scottalanmiller said in Move Windows OS from one platform to another:
In most cases, RAID drivers are included. It's been a long time since I needed to add one.
Agreed - which is why I don't understand why my restored image is BSODing on new hardware. and I'm not really sure where to look to solve it.
After it BSODs it boots to System Recovery Options. From there I can change to the
drive - so this tells me that the needed drivers are there to see that drive. so if recovery can see the drive (which is running from that drive by the way) why can't the OS? I've run fixmbr and the bcdedit commands to rebuild those items, didn't work.BSOD is 0x0000007B
-
Is there a reason to believe that the BSOD is from not seeing the RAID hardware?
-
@scottalanmiller said in Move Windows OS from one platform to another:
Is there a reason to believe that the BSOD is from not seeing the RAID hardware?
0x0000007B is normally because of a hardare change - so I suppose it could be related to the chipset on the mobo.
-
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
Is there a reason to believe that the BSOD is from not seeing the RAID hardware?
0x0000007B is normally because of a hardare change - so I suppose it could be related to the chipset on the mobo.
That would be my expectation. I've never heard of a system BSODing from lacking a storage driver, it just would not see the storage. I think you almost certainly have a false assumption driving you to go down a rabbit hole. Windows will often BSOD because the HAL can't handle a change in the core hardware, a key reason why virtualization is never, ever to be avoided, because that's the tool that protects against that problem. We used to see this from going from multiprocessor to uniprocessor hardware. Could be anything, are you trying to restore to a VM? If not, why not?
-
@scottalanmiller said in Move Windows OS from one platform to another:
are you trying to restore to a VM? If not, why not?
Because this was a server setup pre my using of hypervisors. (not that it would have mattered, the vendor most likely wouldn't have been willing to support a hypervisor setup in 2007 - and today they don't exist, they were bought out).
-
@scottalanmiller said in Move Windows OS from one platform to another:
Windows will often BSOD because the HAL can't handle a change in the core hardware, ... We used to see this from going from multiprocessor to uniprocessor hardware.
My original system is dual socket 4 core ea setup, new VM is dual socket 2 core (max system will allow). Both Intel architecture.
Old server X5460
New Server i5-4570 -
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
are you trying to restore to a VM? If not, why not?
Because this was a server setup pre my using of hypervisors. (not that it would have mattered, the vendor most likely wouldn't have been willing to support a hypervisor setup in 2007 - and today they don't exist, they were bought out).
I don't mean why wasn't it in the past, I mean the restore target.
-
@scottalanmiller said in Move Windows OS from one platform to another:
I think you almost certainly have a false assumption driving you to go down a rabbit hole.
While I did mention the storage as a possible issue, I wasn't limiting myself solely to that as the problem, but I wasn't really sure where else to look - hence this post.
But now I do have some new things to search for, namely how, if possible, to change the HAL.
-
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
I think you almost certainly have a false assumption driving you to go down a rabbit hole.
While I did mention the storage as a possible issue, I wasn't limiting myself solely to that as the problem, but I wasn't really sure where else to look - hence this post.
But now I do have some new things to search for, namely how, if possible, to change the HAL.
CPU architecture is possible, but unlikely.
-
@scottalanmiller said in Move Windows OS from one platform to another:
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
are you trying to restore to a VM? If not, why not?
Because this was a server setup pre my using of hypervisors. (not that it would have mattered, the vendor most likely wouldn't have been willing to support a hypervisor setup in 2007 - and today they don't exist, they were bought out).
I don't mean why wasn't it in the past, I mean the restore target.
The restore target is a VM - but my other thread was getting bogged down, so it seemed in the virtualization aspect. So I was looking to simplify the discussion.
-
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
are you trying to restore to a VM? If not, why not?
Because this was a server setup pre my using of hypervisors. (not that it would have mattered, the vendor most likely wouldn't have been willing to support a hypervisor setup in 2007 - and today they don't exist, they were bought out).
I don't mean why wasn't it in the past, I mean the restore target.
The restore target is a VM - but my other thread was getting bogged down, so it seemed in the virtualization aspect. So I was looking to simplify the discussion.
Ah, but there is no RAID controller at all in a VM. So that question made things way more confusing. You said that RAID drivers would be needed, which would mean that it is not a VM.
-
What hypervisor are you attempting to restore to? Try more than one. Fire up VBox and see what that does.
-
@scottalanmiller said in Move Windows OS from one platform to another:
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
I think you almost certainly have a false assumption driving you to go down a rabbit hole.
While I did mention the storage as a possible issue, I wasn't limiting myself solely to that as the problem, but I wasn't really sure where else to look - hence this post.
But now I do have some new things to search for, namely how, if possible, to change the HAL.
CPU architecture is possible, but unlikely.
Right - I've rarely (actually never) had an issue going from multi to multi before as long as I was going from Intel to Intel or AMD to AMD. Which is why I pretty much dismissed the HAL problem - but it could be more than that - it could be an instruction set issue - something about the chipset drivers looking for something the old Xeon had that the new i5 doesn't.
-
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
@Dashrender said in Move Windows OS from one platform to another:
@scottalanmiller said in Move Windows OS from one platform to another:
I think you almost certainly have a false assumption driving you to go down a rabbit hole.
While I did mention the storage as a possible issue, I wasn't limiting myself solely to that as the problem, but I wasn't really sure where else to look - hence this post.
But now I do have some new things to search for, namely how, if possible, to change the HAL.
CPU architecture is possible, but unlikely.
Right - I've rarely (actually never) had an issue going from multi to multi before as long as I was going from Intel to Intel or AMD to AMD. Which is why I pretty much dismissed the HAL problem - but it could be more than that - it could be an instruction set issue - something about the chipset drivers looking for something the old Xeon had that the new i5 doesn't.
Right, the Xeon to i5 might do it. Or maybe it is failed detection of some sort.
-
I took a backup using Windows backup utility and restored that into a XS 7 server. I'm getting the exact same BSOD 0x0000007b
When the system then boots into the system recover console I look at the diskpart information for
and it's different from the original machine.
Here is the original machine
https://i.imgur.com/WqNnrAL.pngThe VM does not System listed under Info, everything else is identical.
Any thoughts on this?
They are both Active, I even marked it inactive, then back to active, but that didn't fix anything.
-
This is an interesting post - seems to imply the system just trying to load a driver is causing a problem.
http://www.azmer.my/p2v-windows-server-2008-blue-screen-0x0000007b/How to perform the step:-
- Boot-up your VMs with Windows Server 2008 CD.
- Choose Repair Your System
- Choose Command Prompt
- type : $regedit
- Select HKEY_LOCAL_MACHINE
- Click on File –> Load Hive
- Choose your regedit location : (c:\windows\system32\config\SYSTEM ) (make sure correct location)
- Name it as “p2v”
- Then Expand your “p2v”
- Expand ControlSet001 –> Services –> LSI_SAS
- Change LSI_SAS (Start) Property to (0)
- Change LSI_SAS2 (Start) Property to (0)
p/s: It’s could be LSI_SAS, LSI_FC, atiide, megasas, vmscsi, mptsas but depend on the drivers load.
-
Sadly this didn't fix my situation.
