[Bug 1204360] New: Fix determination for canonical path of “/boot/grub2” (by a distribution upgrade)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204360 Bug ID: 1204360 Summary: Fix determination for canonical path of ���/boot/grub2��� (by a distribution upgrade) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs@suse.de Reporter: Markus.Elfring@web.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 862208 --> http://bugzilla.opensuse.org/attachment.cgi?id=862208&action=edit error logs as background information for another questionable software upgrade attempt I came along the need to try another software repair out by the means of the image ���openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20221013-Media.iso���. I could configure my software repositories then. The screen ���Installation Settings��� was finally presented with the following hint after a promising automatic software package selection. ������ Booting Analysing your system������ The following information was displayed by a dialogue box. ���YaST2 <2> Error Execution of command "[["/usr/bin/grub2-editenv", "list"]]" failed. Exit code: 1 Error output: /usr/bin/grub2-editenv: error: failed to get canonical path of `/boot/grub2'. ��� See also information from previous clarification attempts: * 2022-10-15 Fixing components related to software snapshot ���20221013��� https://forums.opensuse.org/showthread.php/576670-Fixing-components-related-... * 2021-06-17 Execution failure for ���grub2-editenv��� (from snapshot 20210615?) https://bugzilla.opensuse.org/show_bug.cgi?id=1187471#c2 * 2020-10-21 [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc https://bugzilla.opensuse.org/show_bug.cgi?id=1177956 How will the chances evolve to fix the affected software components? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204360 http://bugzilla.opensuse.org/show_bug.cgi?id=1204360#c2 --- Comment #2 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Michael Chang from comment #1)
It seems /boot is a separate partition
I got used to the system configuration approach to store the directory ���/boot��� on a separate partition.
... but didn't get mounted rightfully due to systemd.automount units missing?
My file ���/etc/fstab��� contains appropriate entries. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204360 http://bugzilla.opensuse.org/show_bug.cgi?id=1204360#c5 --- Comment #5 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Michael Chang from comment #4)
I think that was an offline upgrade from SUSE's installation media, therefore suspecting an issue in the live system.
Do you find my hint ���openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20221013-Media.iso��� still unclear? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204360 http://bugzilla.opensuse.org/show_bug.cgi?id=1204360#c6 --- Comment #6 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Franck Bui from comment #3)
can you please run `systemctl status boot.automount` to check whether it's missing or not ?
Does the progress of the upgrade process from the ISO image matter for the determination of mentioned information? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com