Bug 2242750 - anaconda ignores some hard drives without giving reason
Summary: anaconda ignores some hard drives without giving reason
Keywords:
Status: CLOSED DUPLICATE of bug 2243206
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 38
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-08 17:45 UTC by Michael Hennebry
Modified: 2023-10-17 15:23 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-10-17 15:23:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Hennebry 2023-10-08 17:45:45 UTC
Anaconda sees, but ignores, a hard drive *without explanation*.
The anaconda is the one with the F39 workstation live .iso .

I tried a trick that used to work, at least sometimes:
I copied the .iso to a partition on my hard drive.
Could not get it to boot.
grub2-mkconfig could not find it or did not believe in it.
Other attempts at booting did not work either.
Leaving the .iso partition alone, I burned a DVD.
The DVD booted just fine.
The Live OS ran just fine.
When I clicked on install,
the hard drive became invisible.

I've been told that the above behavior is deliberate.
Not telling the user what is going on is just plain nasty.

Steps to Reproduce:
1. Copy the F39 workstation live .iso file to a partition on a hard disk.
2. Burn said file to a DVD.
3. Try to install using said DVD.

Actual results:
An invisible hard drive without explanation.

Expected results:
A usable hard drive or an explanation.

Additional info:
I found out about it (and that it was deliberate)
by asking on a fedora mailing list.
The provider of the information did not
suggest that it was documented anywhere.

Comment 2 Katerina Koukiou 2023-10-17 15:23:34 UTC
Upstream fix: https://github.com/rhinstaller/anaconda/pull/5243 - see duplicate bug #2243206 for the status.

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


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