Bug 1954472

Summary:	Installer and grub2-mkconfig do not detect the second ssd
Product:	[Fedora] Fedora	Reporter:	Gianluca D'Andrea <info>
Component:	os-prober	Assignee:	Hedayat Vatankhah <hedayatv>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	34	CC:	agk, fmartine, hedayatv, lkundrak, pgnet.dev, pjones
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-07 21:59:24 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:

Description Gianluca D'Andrea 2021-04-28 08:28:00 UTC

Description of problem:

Hi,
during the installation of fedora 34 the second windows sdd was not detected.
grub2-mkconfig do not detect the second ssd.

Linux fedora 5.11.15-300.fc34.x86_64 #1 SMP Fri Apr 16 13:41:48 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux


How reproducible:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
or
sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

The second disk (windows - ntfs) is not detected. (note: ntfs-3g is already installed)

Steps to Reproduce:
1. sudo grub2-mkconfig -o /boot/grub2/grub.cfg
1a. sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg


Actual results:
Generating grub configuration file
Adding boot menu entry for UEFI Firmware Settings
done

Expected results:
Detect the second ssd disk

Regards

Gianluca

Comment 1 Javier Martinez Canillas 2021-06-30 23:26:33 UTC

Do you have any output from os-prober ? I don't think this is an issue in GRUB.

Comment 2 Ben Cotton 2022-05-12 15:29:29 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Hedayat Vatankhah 2022-05-12 19:05:19 UTC

Oh, dear reporter, I somehow missed this bug. If it still happens, please change the Fedora version to a later version and also provide os-prober output and its logs.

Comment 4 Ben Cotton 2022-06-07 21:59:24 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

Thank you for reporting this bug and we are sorry it could not be fixed.