Bug 882511

Summary: New Anaconda doesn't shows the device names in custom partitioning
Product: [Fedora] Fedora Reporter: Tapani Björg <tapani.bj>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, stephent98, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 02:56:36 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 Tapani Björg 2012-12-01 15:21:33 UTC 
Description of problem:
New Anaconda (Fedora18 Beta) doesn't shows the device names and labels in custom partitioning. On a system with 3 disks, LVM and 17 Partition it's relay hard to find the partition you like. 

Version-Release number of selected component (if applicable):
Anaconda 18.29.2 Fedora18 Beta

How reproducible:
Just use a system with many other OS and empty partitions.

Steps to Reproduce:
1. go into custom disk layout
2. search an exiting empty partition (sdc4 or sda3...)
3. It's really scary, even for an experienced Fedora admin.
  
Actual results:
You are never ever sure, you selcted the partition you want. You may select the wrong one for formating and delete the home partition with the users data... It's really scary, even for an experienced Fedora admin.

Expected results:
1. Show device names and disklabels for all entry and step in the custom disk layout. 
2. Show a summery (including all effaced device names and disklabels)  of all changes before something is written to disk. Thys would make sure everybody is sure what's going on.
3. Add a graphical overview of the disks.(may like Disk Utility 3.0)

Additional info
Comment 1 Chris Lumens 2012-12-04 02:56:36 UTC 

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