Move Windows OS from one platform to another

scottalanmiller

Is there a reason to believe that the BSOD is from not seeing the RAID hardware?

Dashrender

@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.

scottalanmiller

@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?

Dashrender

@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).

Dashrender

@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

scottalanmiller

@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.

Dashrender

@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.

scottalanmiller

@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.

Dashrender

@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.

scottalanmiller

@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.

scottalanmiller

What hypervisor are you attempting to restore to? Try more than one. Fire up VBox and see what that does.

Dashrender

@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.

scottalanmiller

@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.

Dashrender

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.png

The 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.

Dashrender

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.

Dashrender

Sadly this didn't fix my situation.

Dashrender

Found this https://support.citrix.com/article/CTX124961

https://i.imgur.com/MfFB5vs.png

The following workaround is required to repair a virtual machine that meets this scenario:

After importing the virtual appliance attach a WinPE x64 boot disk ISO to the VM (or use the Server 2003 installation media and drop to a command prompt).

Boot the VM.
At the WinPE console type the following command: chkdsk c: /f
When chkdsk is finished shut down the VM.
Eject the WinPE ISO.
Attach the xenserver-linuxfixup-disk.iso to the VM.
Start the VM.
The VM shuts down when the fixup process is complete and the ISO can be ejected.

Dashrender

I'm trying this now, even though I've done these things separately already in the past.

Dashrender

Nope didn't work - I found that If I shrink the partitions I can just barely squeeze it into my ESXi host. trying that now.

Dashrender

OK I think I've licked it - it was a storage related issue.

I originally found this page http://www.justandrew.net/2009/10/stop-0x0000007b-on-p2vd-windows-7.html

Which lead to this currently none working thread, but using the wayback machine I was able to see the page and the referenced post.
https://i.imgur.com/pdhnOIT.png

I booted into recovery mode, launched regedit, I loaded the hive off the drive, made the following changes

hklm\loaded hive\SYSTEM\ControlSet001\services\Intelide\Start = 0
hklm\loaded hive\SYSTEM\ControlSet001\services\pciide\Start = 3

https://i.imgur.com/csYNpSC.png
https://i.imgur.com/8tAmiYs.png

Now in my case I had previously disabled the HP RAID services in hopes of solving this, so you might have to do that as well.