From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Void Linux grub disappears (?) after switching from UEFI to Legacy in BIOS
Date: Thu, 30 Sep 2021 17:46:49 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33192@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
New issue by UsernameRandomlyGenerated on void-packages repository
https://github.com/void-linux/void-packages/issues/33192
Description:
### System
* xuname:
Void 5.14.8_1 x86_64-musl AuthenticAMD uptodate rFF
* package:
grub-x86_64-efi-2.06_2
### Expected behavior
After switching from UEFI to Legacy and back to UEFI again in bios config, Void Linux grub shows up.
### Actual behavior
When I switch back to UEFI, Void Linux install disappears and I have to boot from USB drive, chroot into my install and reinstall grub again.
### Steps to reproduce the behavior
So I have an external MBR HDD with Debian + Windows 10 on it. When I want to use it, I switch my bios settings from UEFI only to Legacy+UEFI. After the work is done, I go to settings again and switch back to UEFI only mode, but then Void Linux grub is not there anymore, so it shows the standard "no system found". To fix that, I need to boot from USB stick, chroot and use "grub-install" command again. I've installed Void Linux manually, according to official docs for full disk encryption (so I have dev/sda1 for /boot/efi and /dev/sda2 for root, home and swap in lvm).
Couple things that I found out:
-I don't even need to boot that MBR HDD to make void linux grub disappear, simply toggling Legacy Mode in BIOS, rebooting and toggling back UEFI only will result in disappearance after reboot.
-Before Void Linux, I've used Fedora, Pop!OS and Debian, all with disk encryption but I never saw that problem there, I could freely switch between Legacy and UEFI mode in bios without my main system disappearing.
next reply other threads:[~2021-09-30 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 15:46 UsernameRandomlyGenerated [this message]
2022-06-06 2:15 ` github-actions
2022-06-21 2:12 ` [ISSUE] [CLOSED] " github-actions
2022-08-23 14:17 ` Dani3I
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33192@inbox.vuxu.org \
--to=usernamerandomlygenerated@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).