Bug 30637

Summary:	grub2 config with initial installation offers inappropriate choices.
Product:	Mageia	Reporter:	Tony Blackwell <tablackwell>
Component:	Installer	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lewyssmith, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	grub menu naming options the output of inxi -Dop

Description Tony Blackwell 2022-07-15 02:47:56 CEST

I've my main working M8 in partition nvme0n1p3. Put another one into adjacent partition nvme0n1p2 with intention ov converting it to cauldron.  Configuring grub2 menu late in the install offers initial label of Mageia, which works as expected.  

The drop-down list of a myriad suggested other possible names for this new install, e.g. to ssee from the menu label which mageia is in which partition, all point at the wrong (old) partition /dev/nvme0n1p3.  Selecting any of these (obviously) boots that old partition, rendering the new install inaccessible from the grub2 menu.

(I note in passing that the menu label offered is only selectable from the long and almost entirely inappropriate list, not editable in itself at this point...)

Seems like a bug to me.
Tony

Comment 1 Lewis Smith 2022-07-15 21:10:40 CEST

Are you able to post the appropriate Grub2 menu/config file? I do not have Grub to be able to be more precise; perhaps another Bugsquader can.

Also perhaps the output of
 $ inxi -Dop

This is likely to end up with tv.

CC: (none) => lewyssmith

Comment 2 Lewis Smith 2023-06-02 20:35:22 CEST

Tony, is this still an issue?

Comment 3 Lewis Smith 2024-01-22 15:01:45 CET

Closing Old.

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

Comment 4 Tony Blackwell 2024-01-24 08:19:02 CET

Hmmm, I've had the guilts about not responding to Lewis's reasonalbe request for info.  Getting bad when the only way to attract my attention is to kill the bug report.
Sorrry!

Its still a real issue.
On a laptop with old M8 in /dev/nvme0n1p4 and m9 in /dev/nvme0n1p5, I deleted the M8, installed another copy of M9 there, formatting the partition in the process.

At the en of install, during grub installation, the drop-down menu offering alternatives to Magei as a name, has a variety of entries pointing to /dev/nvme0n1p5, the wrong partition, not the one we are installing on.  Same issue as per opening this bug.  See screenpic I'll attach now.

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

Comment 5 Tony Blackwell 2024-01-24 08:23:29 CET

Created attachment 14287 [details]
grub menu naming options

see prior comment.  The drop-down naming options point to the wrong disk partition, not the one we have just installed on.

Comment 6 Tony Blackwell 2024-01-24 08:25:40 CET

Created attachment 14288 [details]
the output of inxi -Dop

Hmmm, hardly fast processing time for the request from months ago, but here is the output of inxi -Dop

Comment 7 Tony Blackwell 2024-01-24 08:31:00 CET

I think this is clearly a significant bug.  If installing grub is offering alternative names to boot the just-installed M9 on /dev/nvme0n1p4, it has no business at all offering a whole batch of options all pointing to the wrong partition.

I note in passing it would be really useful to have an option for user inputting free text to the boot menu name for this partition.  Not useful to have only pre-defined names most of which point to the wrong partition.

Comment 8 Lewis Smith 2024-02-01 12:19:34 CET

Passing on to MageiaTools for the Installer, CC'ing Martin in case he has some wisdom to offer.

Assignee: bugsquad => mageiatools
CC: (none) => mageia

Comment 9 Martin Whitaker 2024-02-01 15:32:54 CET

The menu options are generated by grub2-mkconfig/os-prober, so that's the province of the grub2 package, not the Mageia tools. If you don't want the entries for other installed systems, uncheck the box "Probe Foreign OS".

Or just use rEFInd instead of GRUB.

Comment 10 Tony Blackwell 2024-02-09 21:50:03 CET

Ah well, if this is regarded as a fature rather than a bug, I've re-opened in error.  Thanks for the polite reception.  Closing again.
With thanks,
Tony

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