Hey there! You're having trouble getting Arch Linux to start up. Let's troubleshoot together!
Hey there! You're having trouble getting Arch Linux to start up. Let's troubleshoot together!
Last night I set up Arch on an SSD without issues. Today when I accessed my Windows drive, it reported the SSD wasn’t a bootable device even though it worked last night. I used the USB installer, selected Arch, and after a brief error screen, the installation resumed. The partitions appeared intact in fdisk -l. I’m reaching out for help to avoid a full OS reinstall. Attached are my fdisk results and the video of the boot attempt.
You might attempt to check the Linux disk (/dev/sda3) using fsck. The video fails to display, making it unclear what the test should reveal. Previously, for persistent Arch Linux boot problems, I've switched into a live environment, mounted my root filesystem on /mnt, then used arch-chroot to /mnt and launched my services from there. This helps confirm whether the issue lies in the boot process or if the drive itself is faulty. While the mount stays at /mnt, you can also attach your EFI partition to verify proper installation. Also consider reviewing the Arch Wiki: https://wiki.archlinux.org/index.php/Uni...Interface; with UEFI I've encountered many problems where the system skips grub or places the .efi file incorrectly.
Yes, I did it—I used a torrent for a friend on Windows because I hadn’t installed a GUI yet.
You can locate it in the newest MSI Click BIOS 5 version by checking the official download page or the software’s installation guide.
Certain motherboards might remove the EFI Entry if the partition or file isn't found during startup. In such scenarios, you'll need to switch into your Arch installation and reinstall Grub manually, or add the entry back yourself. Without this Entry, the system won't have a valid boot point from EFI. This situation could be the cause. It's unclear exactly where it appears in MSI's BIOS documentation.