I’m gonna do you one better than sending you to the arch forums, but because you were posting on the hacker news forum about arch I am not going to baby you more than the arch forum would. I’m not going to define any of these words that I’m about to use. I am only going to tell you what you needed to do. It is on you to understand and do it.
Did you set up your file system table correctly?
You needed to edit /etc/fstab to point /boot to the partition UUID for your bootloader partition and the “/“ root level to the partition id of the root partition. You can get the partition ids using the blkid command.
The reason I ask this first is that it is common for users when setting up their first arch install to use /dev/sdx where x is a,b,c etc. as that’s how drives are assigned.
Noobs (including myself the first few times) will use the guest (pen drive) operating system’s device path assignments in the fstab, leading to failure when the installed boot drive is /dev/sdb1 under the guest OS but is recognized as /dev/sda1 on boot with the pendrive removed.
No matter what installation of Linux reads the partition ID of the drive, it should remain the same, meaning that if you carried that drive into another computer with multiple drives and selected that drive as boot it would still boot correctly.
If you use the device path method, if you plug that drive into another computer with multiple drives, it will be assigned a different device path and probably not boot.
If it’s not that, give us more information.
Bios no drive error? Nothing but a blinking cursor? A kernel level error complaining about a missing root? Did you install the intel-ucode package and add it to the boot loader entry before the kernel load?
Godspeed. Fuck Windows.
