A small note on the solution to the infinite loop paradox of a server installation

It is said that I recently built a new server in the company, XEON E5 V3, 32G ECC DDR4, Supsermicro motherboard, H730P+4*4T Seagate SAS hard drive, and then I found it embarrassing when I installed the system.

The hard disk is made Raid10, and then there is 8T, so it must be partitioned with GPT, and EFI must be booted for installation.

The old rule made a Windows 2012 R2 system booted from a U disk, and then found the following infinite loop:

The GPT of the 1.8T hard disk must be EFI boot

2. EFI only recognizes FAT32

3. The maximum file size of FAT32 is 4G, but the install.wim of the 2012 installation disk is 4.5G; that is to say, NTFS must be started.

At this point, it can be seen that Daweinuan's brain is disabled... But it's not over yet.

4. The solution of PE or rufus is used, one NTFS + one hidden FAT32, but it is found that it still does not work, and the EFI boot crashes

5. Change to the pure EFI boot solution of Windows 10's EFI+FAT32, but it still crashes after booting into EFI mode.

6. Consult Supermicro customer service, the answer is to set the slot corresponding to PCIE to EFI (the default is Legacy). After setting, the hard disk can't be seen at all... Consult again, the answer is that the SCSI card does not support EFI mode.

Did you see that, so far, it has completely entered a dead end. . . Fortunately, a friend, Lao Sang, is a professional in doing this. After consulting, he learned that HP's customer service had suggested to him before that he should make two Virtual Disks on the SCSI card, install an MBR system, and then install the system and enter the system. GPT another Virtual Disk in the system; after trying it, it was solved perfectly.

After I finished speaking, I thought about it carefully and found that this turned out to be the only solution...


Guess you like