Bug 1955936
Summary: | Netinstall Error: Failed to Write Boot Loader Configuration | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | ghborrmann | ||||
Component: | grub2 | Assignee: | Javier Martinez Canillas <fmartine> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 34 | CC: | anaconda-maint-list, bootloader-eng-team, bugzilla, fmartine, jonathan, kellin, lkundrak, pgnet.dev, pjones, th.schoel, vanmeeuwen+fedora, vponcova, w | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2021-06-22 15:14:40 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: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
ghborrmann
2021-05-01 14:57:19 UTC
Created attachment 1778164 [details]
/tmp/syslog after error
Reassigning to grub. I have traced the problem to grub2-probe. The script tries to execute: grub2-probe --device /dev/sda1 --target=fs /dev/sda1 is the EFI partition. The result of the above command is grub2-probe: error: ../grub-core/kern/fs.c:120:unknown filesystem. I can now explain the reason why grub2-mkconfig worked when I first managed to get into the new system. Apparently what was installed originally by anaconda was grub2-tools-minimal-2.06~rc1-3.fc34.x86_64, and this version of grub2-probe does not have this bug. When I installed grub2-breeze-theme, dnf installed grub2-tools-minimal-2.06~rc1-4 as a dependency. Executing this version of grub2-probe produces the error. I have identified the cause of the problem. It occurred because the EFI partition contained a file (FSCK000.REC) with a zero time stamp. I'm guessing that the file was probably generated at boot time after a system crash. After changing the time stamp with touch, grub2-mkconfig executed successfully. What needs to be done: the function grub_fat_timestamp() in grub-core/fs/fat.c returns the time stamp, but uses zero as an error return. The function needs to deal with the fact that the time stamp could be zero. I have changed the severity to low because I think it unlikely that many users would ever encounter this situation. However, when it happens the user has no clue about how to work around the problem. Even the -v option of grub2-probe gave no hint of what was wrong. At the least, some informative error message should be generated. Please report this issue to the upstream GRUB project. *** Bug 1945879 has been marked as a duplicate of this bug. *** |