Differences between revisions 1 and 2
Revision 1 as of 2022-09-02 22:49:35
Size: 1948
Editor: scot
Comment:
Revision 2 as of 2022-09-02 22:50:16
Size: 1958
Editor: scot
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
{{InsertPicture.jpg}} {{attachment:reboot_error.png}}

Problems Installing Windows 2022 Server

I am running ProxMox 7.2-7 using Ceph files system across 8 AMD EPYC servers (7402P 24 core/256 GB RAM, 8 TB of Ceph space each) . Kernel 5.13.19-6-pve. I have been able to install most OS types without problem (Ubuntu, Arch Linux, OpnSense, pfSense, Windows 10, etc.)

But when it comes to Windows Server 2022, and carefully following the best practices page (I've tried two different ISOs both of which passed their sha256 hash match - August update and the February Update just to get some variety), it fails on the first reboot after installing the OS. Specifically, I am able to get through the windows install step that loads the drivers and runs the install. All of which is successful (apparently). Then on the first reboot, I get the following:

reboot_error.png

I don't know what is going on here, but I have successfully installed Windows 2022 on ProxMox VE on a different serer (an older intel I7), which does not use the Ceph file system. But its a stand alone ProxMox VE server and uses local disks.

Variations: I've tried with IDE, SATA, SCSI, VirtIO Block device, some of these got through the install process only to fail as above. None of them were successful. Does nvraid.sys get changed by the driver? I don't think so, because I've done SATA and IDE installs without the VirtIO drivers and had the same result. Therefore, it must be something in ProxMox itself (e.g. Cephfs), or some manipulation of the virtual drive that causes a change in maybe the size. I haven't dug into the actually code and would prefer not to.

Other Troubleshooting Efforts: I am able to boot into the DVD and go into troubleshooting mode. The automatic repair finds, or at least fixes, nothing. The working version of nvraid.sys in c:\windows\system32\driver appears to be the same as the working one that I have installed. Copying the working driver does not make a difference.

ProxMoxWindows2022 (last edited 2022-09-09 14:15:46 by scot)