Bug 30178 - Grub may try to resume wrong system.
Summary: Grub may try to resume wrong system.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords: FOR_ERRATA8
Depends on:
Blocks:
 
Reported: 2022-03-16 12:14 CET by Elmar Stellnberger
Modified: 2024-08-22 22:59 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
setboot - script for dual boot between Mageia and Debian (1.18 KB, application/x-shellscript)
2022-04-09 12:01 CEST, Elmar Stellnberger
Details

Description Elmar Stellnberger 2022-03-16 12:14:07 CET
All the time I boot I have to hit return on an error message after selecting to boot Mageia: "error: ../../grub-core/commands/loadenv.c:216: sparse file not allowed".
  The error seems to stem from when Grub had been compiled but it does not impair functionality. It is just somewhat annoying.

> rpm -q grub2-common grub2-efi grub2-mageia-theme
grub2-common-2.06-1.1.mga8
grub2-efi-2.06-1.1.mga8
grub2-mageia-theme-2.06-1.1.mga8
Comment 1 Elmar Stellnberger 2022-03-16 12:36:19 CET
list of related issues: https://bugs.mageia.org/show_bug.cgi?id=30180
Comment 2 sturmvogel 2022-03-16 14:26:59 CET
Duplicate of bug 27117

*** This bug has been marked as a duplicate of bug 27117 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 3 Elmar Stellnberger 2022-03-29 12:22:30 CEST
As I have posted yesterday for bug 27117 disabling the error message is not the solution. If you need to resume from hibernation and the timeout elapses or you do not know the last booted system any more then it will worse than crash your system if the last boot entry is not selected again automatically. As I have found out this is possible by storing the grubenv in /boot/efi rather than /boot/grub. Please look forward to issue an update/patch for my fix. It is an issue that should really be resolved and that has already been reported for many distributions.
Comment 4 Elmar Stellnberger 2022-04-09 12:01:29 CEST
Created attachment 13215 [details]
setboot - script for dual boot between Mageia and Debian

  I do also have a solution for when you have btrfs, no BIOS computer and no UEFI partition: Set the system to be booted next with grub[2]-setenv. The script has the boot-ids from /boot/grub/grub.conf for Mageia and Debian configured statically (automizing that fully one would have to parse grub.conf).
  This could f.i. be useful for coreboot-machines or whenever you wanna set the system to be booted next manually. You could do so to automatically reboot to another distribution without anyone having to manually select a Grub entry on boot.
Comment 5 Morgan Leijström 2022-04-09 16:42:21 CEST
Reopening per Comment 3: it may try to resume wrong system after hibernation.

Assigning to tools maintainers for comment, or more.

This may be worth an errata entry.

Resolution: DUPLICATE => (none)
Keywords: (none) => FOR_ERRATA8
CC: (none) => fri
Status: RESOLVED => REOPENED
Summary: odd looking error message displayed by grub: sparse file not allowed => Grub may try to resume wrong system.
Assignee: bugsquad => mageiatools

Comment 6 Marja Van Waes 2024-08-22 22:59:59 CEST
We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: REOPENED => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.