Hutchison Win10 - Archlinux - Archlinux (Emergency) three systems installation / configuration Notes

Archlinux cause is normally used to make rollover, the result looks like there is a bad disk block write (?).
Do not have U disk, can not enter linux, do not fsck. So directly on the direct use of win10.

Cancel Fast Boot

That night into linux find problems

Loading kernel...
error: invalid cluster 0

The efi partition should be the win10 disk blocks ruined, as long as the BIOS Fast Boot cancel to prevent this problem.
But obviously my plate block has been broken, with cdlive looked into and found vmlinux is broken.

Step just mention here the linux grub guide (please refer to /boot/grub/grub.cfg, or health grub menu press c):
the load necessary modules
disposed root (i.e., the partition efi)
Loading vmlinux
performed initrd

Find problems like say, livecd into the root directory can reinstall linux

...
arch-chroot /mnt
pacman -S linux

So far the problem is solved.

linux dual system installation win10 +

When taking into account each system problems, do not have the embarrassment of u disk, I decided to install a linux system emergency.
Limited disk space, to let out a good (mainly because of the addition of a memory is probably no need to change it) swap partition.

swapoff /dev/sda5
mkfs.ext4 /dev/sda5

Then you can install with just livecd.

EFI partition too small

My efi partition share was very small, only 100M, as well as content from other systems. So vmlinux and install a new initramfs space is absolutely not enough.
Think of ways to delete something.
/ the Boot / the Boot / Fonts
/ the Boot / EFI / in the Microsoft / the Boot / Fonts
initramfs-fallback.img
these in addition to which the Chinese font (comes with English font), I have not had

Installation Considerations boot

Please note that during installation guide :

1. Installation os-prober, used to discover other two systems (i.e., normal and win10 Archlinux)
2. Normal generation grub.cfg
3. Vmlinux systems and distinguish between normal and initrmfs Emergency systems, and modify grub.cfg

pacman -S os-prober
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=emergency
grub-mkconfig -o /boot/grub/grub.cfg

# 首先区分vmlinux, initramfs
mv /boot/vmlinux /boot/vmlinux-emergency
mv /boot/initrmfs.img /boot/initramfs-emergency.img

# 其次修改grub.cfg
# 把emergency对应的内容改为vmlinux-emergency, initramfs-emergency.img
vim /boot/grub/grub.cfg

So far completed live.

Sure some people ask why not share vmlinux and initramfs it?
I take into account normal and emergency systems kernel version is likely to be different, in fact, I try to start the normal system fails in the case of sharing.

[Failed] Failed to mount /boot

# 看看boot.mount
systemctl status boot.mount
# 发现报错信息：
# mount: unknown filesystem type 'vfat'

First thought grub fat load module if there are problems, but the startup script obviously written isnmod fat
followed by linux own modules loaded

modprobe vfat
# 报错：/lib/modules/5.1.15-arch1-1-ARCH不存在

Joke, my normal system kernel version is 5.1.14, 5.1.15 version should be urgent, there is the problem here vmlinux and share initramfs caused.

So distinction is inevitable.