Windows Server 2003 P2V adventures
-
@momurda said in Windows Server 2003 P2V adventures:
Oh i just noticed. Did this physical vm have more than 1 cpu or 1 cpu core? Your vm is setup as only 1 vcpu. This could be a problem.
If it only had the one cpu... a bit incredible it can read just fine but wont boot. Long shot, but do you have a win2k3 cd/dvd? can you load that and try a Repair Installation? Like the days of yore with xp, that option worked wonders for me fixing things like this.My physical server is 2 socket, 2 core per
https://i.imgur.com/CuZuXrr.pngMy VM settings are:
https://i.imgur.com/jzex26w.png -
@momurda said in Windows Server 2003 P2V adventures:
Your vm is setup as only 1 vcpu.
Good catch seeing this on the BIOS screen inside the VM - but I ask WTH? I have the VM setup as a dual socket dual core system.
-
@Dashrender said in Windows Server 2003 P2V adventures:
@momurda said in Windows Server 2003 P2V adventures:
Your vm is setup as only 1 vcpu.
Good catch seeing this on the BIOS screen inside the VM - but I ask WTH? I have the VM setup as a dual socket dual core system.
In thinking about this - I don't think this is the issue either though - I think it's before this.
I found this link
https://support.microsoft.com/en-us/help/325375/how-to-troubleshoot-startup-problems-in-windows-server-2003 -
Hmmm.
Ok if you can get the thing to boot with Hiren's, what does your windows say the cpu count is when that happens?
Have you tried Safe Mode yet? -
@momurda said in Windows Server 2003 P2V adventures:
Hmmm.
Have you tried Safe Mode yet?I can't press F8 fast enough - or the system isn't reaching that part before it freezes.
-
Have you tried another clean clone? Boot up the hardware, let it settle, cleanly shut it off, then re-image it.
-
Also can you boot from Hirens then run msconfig and check all boot paths?
-
@momurda said in Windows Server 2003 P2V adventures:
Hmmm.
Ok if you can get the thing to boot with Hiren's, what does your windows say the cpu count is when that happens?It sees 4 CPUs inside the VM
https://i.imgur.com/KenEFur.png -
@MattSpeller I don't understand?
I installed a brand new VM from the CD of 2003, and that works just fine on XS 7.
-
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller I don't understand?
I installed a brand new VM from the CD of 2003, and that works just fine on XS 7.
Right, but it fails when you try to restore from your backup... what if it's corrupt? I've had it happen with dodgy old crap before.
-
@MattSpeller said in Windows Server 2003 P2V adventures:
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller I don't understand?
I installed a brand new VM from the CD of 2003, and that works just fine on XS 7.
Right, but it fails when you try to restore from your backup... what if it's corrupt? I've had it happen with dodgy old crap before.
Well, what part do you think might be corrupt? At this point, the only that that appears to be able to be remaining as corrupt is the boot sector or MBR - because as long as I'm able to bypass whichever of those is first, I can boot the VM - using Hirem's boot disk.
-
@MattSpeller said in Windows Server 2003 P2V adventures:
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller I don't understand?
I installed a brand new VM from the CD of 2003, and that works just fine on XS 7.
Right, but it fails when you try to restore from your backup... what if it's corrupt? I've had it happen with dodgy old crap before.
I was wondering if I might have some doggy parts on the original system drive - and the clonezilla isn't getting a good read... I can run a chkdsk there to see if that would solve it.
-
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller said in Windows Server 2003 P2V adventures:
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller I don't understand?
I installed a brand new VM from the CD of 2003, and that works just fine on XS 7.
Right, but it fails when you try to restore from your backup... what if it's corrupt? I've had it happen with dodgy old crap before.
Well, what part do you think might be corrupt? At this point, the only that that appears to be able to be remaining as corrupt is the boot sector or MBR - because as long as I'm able to bypass whichever of those is first, I can boot the VM - using Hirem's boot disk.
I missed that bit. Hmm possible for the MBR I suppose.... ¯\(ツ)/¯
-
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller said in Windows Server 2003 P2V adventures:
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller I don't understand?
I installed a brand new VM from the CD of 2003, and that works just fine on XS 7.
Right, but it fails when you try to restore from your backup... what if it's corrupt? I've had it happen with dodgy old crap before.
I was wondering if I might have some doggy parts on the original system drive - and the clonezilla isn't getting a good read... I can run a chkdsk there to see if that would solve it.
If you're 100% stumped it won't hurt and it will give you time to ponder
-
@MattSpeller said in Windows Server 2003 P2V adventures:
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller said in Windows Server 2003 P2V adventures:
@Dashrender said in Windows Server 2003 P2V adventures:
@MattSpeller I don't understand?
I installed a brand new VM from the CD of 2003, and that works just fine on XS 7.
Right, but it fails when you try to restore from your backup... what if it's corrupt? I've had it happen with dodgy old crap before.
Well, what part do you think might be corrupt? At this point, the only that that appears to be able to be remaining as corrupt is the boot sector or MBR - because as long as I'm able to bypass whichever of those is first, I can boot the VM - using Hirem's boot disk.
I missed that bit. Hmm possible for the MBR I suppose.... ¯\(ツ)/¯
I've run fixboot and fixmbr on the virtual disk many times.... but it's not solving the problem.
When it first happened, I was like oh this is going to be easy, the MBR is broke, just fix and away we go.. but damn if the boot/mbr just wont' be fixed!
-
Informational
http://ntfs.com/boot-sector-damaged.htm
Promising information
http://www.pcc-services.com/windows/guide-noboot.html
and another
https://bobcares.com/blog/windows-server-2003-boot-process-common-errors-solutions/
-
I added a boot option in the boot.ini of one of my restores, and upon booting with Hirem's Boot CD. Now I see this.
https://i.imgur.com/6JklY4X.png
This leads me, but is no promise, that the hold up is before the boot.ini - damn I have to learn more about the boot loading process.
I'm pulling a disk 2 VHD image of my original system currently - some time tomorrow (I hope) I'm going to pull a comparison of the boot sector on the disk between the original and the VM.
-
Something I just considered.
To ensure that the partitions where large enough, when I created the partitions for the VM, I made them 1 GB larger than the originals. This leaves slack space in the drive that will not be used by the restore.
I looking through the defaults when in expert mode, it looks like Clonezilla grows your disk to fit the space...more trial and error.
-
Did you try the command
chkdsk c: /pas shown in the one article? -
@Dashrender said in Windows Server 2003 P2V adventures:
Yes I did - I found that my 2003 server was (I think) missing one of the IDE drivers, so I put it in c:\windows\system32\drivers but that didn't help. I checked the registry, all looked well there.
The fact that it booted when using the boot sector from the Hirem CD implies to me that the boot sector in the VDI isn't properly pointing to the ntldr, so it's not booting. Somehow the boot to local media option of Hirem's CD gets past the hurtle and allows the system to boot.Did you load the drivers with the system still up, or just inject them in to the system image after it was powered down?
I remember once I had a VM that someone else P2Ved and VMware thought it had IDE drives. I couldn't expand the drive until I switched the drive type. The solution was to add another drive to the system of the same type as the new drive so that they system would load the new driver. Then I was able to change the drive type because the system was loading the drivers, they weren't just sitting on the drive waiting to be searched for.
That doesn't seem to be the root of your problem though.
