Regarding this problem, I have encountered this problem when I installed the notebook win7. Just remember to change the hard disk mode when changing the bios. I did not go into it. In fact, it is my ignorance. I just know that the installation system will appear when many motherboards start to support uefi This situation.
Some time ago I installed an old notebook, Lenovo’s E4430. Since there is no msata interface, only an optical drive can be installed with a solid state drive. I thought about installing a system on the solid state drive so that it can be a dual system. As a result, installing several systems is all started. No, just when I was about to give up, I installed furyBSD, which aroused my interest! I searched the Internet for the reasons and solutions, only to find that I was so ignorant of uefi! This new startup method has many features and benefits. To sum it up, it is versatility and speed!
EFI is conceptually very similar to a low-level operating system and has the ability to control all hardware resources. ESP is used for BIOS boot in UEFI mode and is a small partition on the hard disk. The partition identifier of the eps partition is EF (hexadecimal du) instead of the conventional 0E or 0C. The partition contains tools such as boot management programs, drivers, and system maintenance. Computers that support EFI mode need to boot the system from ESP, and EFI firmware can load EFI from ESP to start programs and applications. The esp partition is a boot partition, and one more system is actually an additional boot directory and corresponding boot files under the esp partition. Moreover, the ESP partition uses the FAT format, which can accommodate multiple systems. Moreover, a boot file is not big, so even if there are more systems, the esp partition will try to be slightly larger to store each boot of the multiple systems. UEFI only supports 64-bit systems, so choose 64 when making a U disk Bit system
By default, the installation program uses the ESP on the HDD, which means that the boot file is on the HDD, and the SSD can only have one primary partition. You can also manually create an ESP on the SSD and format it as FAT32. Then use the bcdboot or bcdedit command to create a boot file on it. Then, in the BIOS setting/F12 (some brands may be ESC, f1/f8, etc.) boot menu/UEFI boot sequence of BOOTICE, you can see two Boot Managers, one for HDD and one for SSD. In other words, just plug in either HDD or SSD and it will boot normally. You can also add two boot options to the BCD in the HDD/SSD, so that it can boot regardless of whether it is booting from the HDD or the SSD, and then a menu is displayed, you can use this menu to choose to boot the system on the HDD or the SSD.
PS: But since Win8, Microsoft has made a bootim.exe "fake operating system selection menu". This hurts the egg. The bootloader actually skips the "display menu" step, and then directly starts the default operating system. When it is halfway up, use bootim.exe to make a fake operating system selection menu. look. At this time, if you directly press Enter, then continue to start the default operating system; if you make other choices, the execution is actually to modify the booter settings -> restart this action. This kind of speechless design has a lot of painful problems. For example, if you set Win10 on the SSD by default in the BCD on the HDD, and then unplug the SSD, the boot will directly report an error "winload not found" ".efi", or just enter WinRE "diagnosing your computer" (then it still reports an error, and there is no X used). Originally, a menu was displayed for you to choose and it was OK. As a result, Microsoft had to go around like this. To avoid this problem, you can use bcdedit /set {default} bootmenupolicy legacy to disable the "fake operating system selection menu", but the bootmenupolicy may be changed back when the major version of Win10 is updated...
There are many installation disks that do not automatically install UEFI and require manual intervention! Although it does support UEFI, it is not user-friendly, so many systems cannot be started during installation. For example, if your hard disk mode is MBR, it cannot be started by uefi, but the installation program does not know how to convert the hard disk table to GPT. , But the same partition into a GPT-like partition table, the result is a variety of startup problems. Because it does not know whether your bios automatically choose UEFI boot or regular boot, and some bios do not support regular boot from hard disk, but can boot from uefi from hard disk, such as my E4430 this time, if it is not furyBSD The installation supports automatic creation of ESP partitions and handles them by myself, I still can't find the reason.
It’s easy to know the reason. When installing other systems, you only need to partition manually. First create an ESP partition and save it, and then install the system to other area partitions. (Of course, the previous question is that your installation system supports UEFI. Most distributions support), you can also use diskgenius to create an ESP partition by yourself. The previous topic is to convert the partition to GPT first. You can use xorboot to repair the esp. It feels easy to use. Just Baidu it yourself!
