| Summary: | Updating or reinstalling grub2-efi will cause grub2 boot into rescue mode on ASUS TX300 laptop | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | LiuYan <lovetide> | ||||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 26 | CC: | bugzilla, lkundrak, mads, pjones, samuel-rhbugs | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-01-19 18:01:54 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
LiuYan
2016-01-13 10:16:11 UTC
I still can't figure out why this happened on my laptop, while it works fine on my desktop machine (EFI, x86_64). Maybe it's related to the MicroSD/TF card, but I'm not sure. When TF card is in the internal card reader, it often caused the block device name not fixed: sometimes it's `/dev/sdb` (HDD is `/dev/sdc`, SSD is `/dev/sda`), sometimes it's `/dev/sdc` (HDD is `/dev/sdb`, SSD is `/dev/sda`).
A little deeper analysis shows that `/boot/efi/EFI/fedora/grubx64.efi` file does not contain root (partition) information. In the following hexdump (copied from hexedit actually) of `/boot/efi/EFI/fedora/grubx64.efi` file, "**(,gpt6)/grub2**" string in `0001D2B0` line does not exists when grub2-efi package updated/reinstalled.
0001D290 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................
0001D2A0 00 00 00 00 00 00 00 00 03 00 00 00 18 00 00 00 ................
0001D2B0 28 2C 67 70 74 36 29 2F 67 72 75 62 32 00 00 00 (,gpt6)/grub2...
0001D2C0 01 00 00 00 00 00 5A 5B 5D C3 41 56 41 55 41 54 ......Z[].AVAUAT
0001D2D0 55 48 89 F5 53 49 89 FC 48 8B 76 08 FF 55 00 85 UH..SI..H.v..U..
0001D2E0 C0 BB 01 00 00 00 0F 85 BC 00 00 00 4C 89 E7 89 ........L...L...
Created attachment 1171618 [details]
grubx64.efi file after upgraded to Fedora 24
again, after upgraded to Fedora 24, grub2 entered rescue mode.
attachment is the grubx64.efi file after upgraded to Fedora 24
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. After upgraded Fedora 25 to Fedora 26 Alpha, grub2 went to rescue/minimalist mode too. You should not be running grub2-install on an EFI system. Grub going to rescue mode means that it can't find the grub config file. Look in /boot/efi/EFI/fedora and see if there is a grub.cfg file there. Thanks Samuel, you're right, there's no grub.cfg in /boot/efi/EFI/fedora. I remembered that I moved(or copied then deleted later) grub.cfg to /boot/grub2 from /boot/efi/EFI/fedora long time ago. Move grub.cfg back to /boot/efi/EFI/fedora do fixed my problem. By the way, debian doesn't put grub.cfg in /boot/efi/EFI/debian. |