That's where the ESP backup comes in handy if you make things work, you can restore your ESP to its current state using an emergency system, and with any luck it will begin to work as it does now and you'll be able to try something else. It's conceivable it will make everything much worse, though. The worst likely scenario is that re-installing GRUB in this way will reverse your problem - you'll be able to boot Ubuntu but not Arch. Note that re-installing GRUB from Ubuntu is something of a gamble, particularly with respect to its ability to boot Arch. I recommend running Boot Info Script, posting its RESULTS.txt file to a pastebin site, and posting the URL to your file here. If Arch boots from rEFInd but Ubuntu doesn't, or if neither OS boots from rEFInd, then you've got a bigger problem.If Ubuntu and Arch both boot from rEFInd, you can do as above or you can install rEFInd from its PPA or Debian package and use it as your primary boot manager instead of GRUB.Note that you'll need to adjust /etc/fstab to mount your new ESP at /boot/efi and then run sudo grub-install. If Ubuntu boots from rEFInd but Arch doesn't, try re-installing GRUB from Ubuntu.A file-level backup (using cp or tar) to a USB flash drive should be sufficient. Connect and share knowledge within a single location that is structured and easy to search. Find centralized, trusted content and collaborate around the technologies you use most. If you can boot either OS, back up your EFI System Partition (ESP). Create free Team Collectives on Stack Overflow.Depending on how you installed, you might be able to boot by selecting a kernel and hitting the Enter key or you might need to hit F2 or Insert twice and add a root= option to work, too. Test rEFInd's ability to boot both Arch and Ubuntu.
#Archlinux create boot partition how to
In a sense, that's an Arch problem, not an Ubuntu problem but I do have a suggestion for how to repair the problem using Ubuntu:
It sounds like Arch hasn't set up its GRUB to handle Ubuntu properly.
0 kommentar(er)
