Bug 902617 - Unable to determine what disk is /dev/sda when identical disk models installed
Summary: Unable to determine what disk is /dev/sda when identical disk models installed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 906428 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-22 05:20 UTC by Shawn Starr
Modified: 2013-10-08 00:17 UTC (History)
8 users (show)

Fixed In Version: anaconda-19.3-1
Clone Of:
Environment:
Last Closed: 2013-03-21 13:49:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Duplicate disks (18.66 KB, image/jpeg)
2013-01-22 05:20 UTC, Shawn Starr 		no flags Details
View All

Description Shawn Starr 2013-01-22 05:20:07 UTC 
Created attachment 684848 [details]
Duplicate disks

Description of problem:
If you have duplicate disks of same name you don't know which is /dev/sda

Version-Release number of selected component (if applicable):
anaconda-18.37.11-1.fc18.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Have identical disks, installer doesn't tell you which is /dev/sda when partitioning
  
Actual results: 

Unable to determine which disk is /dev/sda

Expected results:

User is able to see which disk is listed as /dev/sda, /dev/sdb etc

Additional info:

We should include this in the disk screen
Comment 1 Chris Lumens 2013-01-23 15:16:39 UTC 
We're talking about what changes we can make (and I'm sure I've seen a bug for this before) but for now, you can also hover over the widgets and it'll pop up the names.
Comment 2 Chris Lumens 2013-01-31 16:10:00 UTC 
*** Bug 906428 has been marked as a duplicate of this bug. ***
Comment 3 Máirín Duffy 2013-03-20 22:15:01 UTC 
Looks like you fixed this in F19 - on the F19 boot iso I have, the device name is prominently displayed under each disk. Close nextrelease?
Note You need to log in before you can comment on or make changes to this bug.