Bug 129086 - Bad: Anaconda does not like on-unique disk LABELs during installation
Bad: Anaconda does not like on-unique disk LABELs during installation
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2004-08-03 17:37 EDT by Hans-Olof Hansson
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-03 17:50:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Hans-Olof Hansson 2004-08-03 17:37:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
Bad: When I installed (upgraded) my computer to FC2 Anaconda reported
that the disk LABELs on the disk-partitions was not unique; ie.
identitical LABELs found for different partitions in the system. I
then was told to quit the installation and go fix the problem myself. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Mount a disk with LABELS / and /usr in your PC
2. Mount a second disk with LABELS / and /usr in your PC
3. Start Installation/upgrade using a CD/DVD 
4. Step through the installation process

Actual Results:  At last Anaconda report the problem and tells you to
abort the installation and go fix the problem yourself. All setups
done so far in Anaconda is thus lost, not good...

Expected Results:  RFE: Wouldn't it be nice if Anaconda, when finding
non-unique LABELs, reported all partitions and disk-LABELs found in
the system and then allow the user to remove or rename LABELs as he
see fit? 

Additional info:

This bug seems related to

Reported on Anaconda-devel-list as below
Comment 1 Jeremy Katz 2004-08-03 17:50:19 EDT
Making changes to the handling of this within anaconda is very
difficult as you're not in a good environment to be able to look and
see what is on the disks which is really required for making any sort
of distinction like this.  Hence, why we just tell you that your
system is not set up correctly and leave it to be fixed in a *real*
environment where you have a full set of tools to be able to
accurately assess what belongs where.

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