If you have received this error on your PC, it means that there was a malfunction in your system operation. The error using this code may occur in many different locations within the system, so even though it carries some details in its name, it is still difficult for a user to pinpoint and fix the error cause without specific technical knowledge or appropriate software. The numerical code in the error name contains data that can be deciphered by the manufacturer of the component or application that malfunctioned. No motherboards can read ext or BTRFS the UEFI standard defines FAT as the ESP filesystem.What is WinRE? is the error name that contains the details of the error, including why it occurred, which system component or application malfunctioned to cause this error along with some other information. There is absolutely no problem using a FAT filesystem to house the kernel image - if there is any corruption, you just re-install the linux package to regenerate the kernel image & initramfs. It is standard Arch practice to mount /boot to the ESP as this allows the use of gummiboot and direct EFISTUB loading of the kernel image without further work-arounds. So far, as you don't wanna run the kernel from a fat32 fs, you need seperate fs (which basically means seperate partitions) for the kernel and efi. And because of this, it's usually a fat32 fs - I'm not shure if there is any mainboard's firmware out there which can access ext2/3/4 or btrfs by default. However, to get things work, the efi partition should be readable from your mainboard's firmware.
The efi partition is where your bootloader resides, so it should be mounted on /boot/efi, I guess.
boot is where the kernel and initramfs-image reside. Why mounting the efi partition on /boot ?
0 kommentar(er)
