You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
Pop installer
Issue/Bug Description:
I was running 21.10, wanted to install 22.04 but be able to access my 21.10 install as needed while transitioning. Unfortunately, after attempting to install 22.04 alongside it, I can no longer boot into 21.10. I've installed rEFInd, but that also fails to boot into the 21.10 install. A few days into trying to figure out how to fix this EFI boot record now.
Steps to reproduce (if you know):
install 21.10, UEFI
install 22.04, selecting the existing EFI gpt partition for boot and a new pre-formatted partition for root
21.10 boot record is now broken
Expected behavior:
Should still be able to boot into 21.10
Other Notes:
The text was updated successfully, but these errors were encountered:
I installed rEFInd, which allowed me to see the install, and then had to clear some space, as checking the logs showed that the 4 gigs I left it was (somehow???) not enough to prevent the log out of space errors...?
Distribution (run
cat /etc/os-release
):22.04
Related Application and/or Package Version (run
apt policy $PACKAGE NAME
):Pop installer
Issue/Bug Description:
I was running 21.10, wanted to install 22.04 but be able to access my 21.10 install as needed while transitioning. Unfortunately, after attempting to install 22.04 alongside it, I can no longer boot into 21.10. I've installed rEFInd, but that also fails to boot into the 21.10 install. A few days into trying to figure out how to fix this EFI boot record now.
Steps to reproduce (if you know):
install 21.10, UEFI
install 22.04, selecting the existing EFI gpt partition for boot and a new pre-formatted partition for root
21.10 boot record is now broken
Expected behavior:
Should still be able to boot into 21.10
Other Notes:
The text was updated successfully, but these errors were encountered: