Gave away my i5 2500k and Asrock z68 motherboard in exchange for a Asus Sabertooth 990FX and an 8350. Not thinking or caring what could go wrong with just exchanging motherboards without bothering to back up our not so precious data, we simply changed it all over in an afternoon.
To my ignorant surprise Windows 10 from the other PC's HDD booted just fine on an i5 and GTX 680 pushing to an a399u @ 4k after living in a sterile AMD environment its whole life.
I was prepared to do some swearing at the bootloader after changing every aspect of the system sans the GPU and storage, but I have reached the end of my rope on this one.
It is running Arch/Antegros with kernel 4.3, Gnome 3.18, and lightdm.
How can I restore a bootloader to my arch install?
Update: I've been at this all day. I have a grub console but vmlinuz-linux is nowhere to be found.
Can you boot from a live CD and check if your /etc/fstab is using UUID to identify the drives? I suspect that the UUIDs have changed and thus /boot is not found where the vmlinuz-linux image is (as far as I know).
I had that problem when I had to clone a server remotely, and forgot about that... had to pay for a KVMoverIP to be hooked up to the damn machine to fix that :(
mount your root / and boot /boot partitions onto /mnt/os for example your system may or may not be EFI and may or may not have a separate EFI partition (check with fdisk -l, if you only have one small partition, the boot and EFI partition are one and the same, if you have two, one will be /boot and the EFI will be /boot/efi and should be mounted there also.
chroot into your system
root # mount -t proc proc /mnt/os/proc
root # mount --rbind /sys /mnt/os/sys
root # mount --make-rslave /mnt/os/sys
root # mount --rbind /dev /mnt/os/dev
root # mount --make-rslave /mnt/os/dev
You might also need to do a new grub.cfg but this is unlikely, do this next step if it installed grub but it still didnt give you the right options to boot.
It might be the fact that your using device paths rather than UUID. switch your /etc/fstab to using UUID, and run the grub2-mkconfig as I suggest above (skip the installing grub part) and see if that works.
Arch may have renamed it, i cant remember off the top of my head. which ever is installed is the one to use, the command options are the same.
It might be worth trying, if found gummiboot/systemd-boot easier to use. Youll likely need to the the chroot I mentioned above to get into the system, if you have the arch install cd you can just use .. whats it called..arch-chroot? the one used during install. remember to mount your partitions first.
