RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 593399 - Second install does not allow selecting target partitions
Summary: Second install does not allow selecting target partitions
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-18 18:00 UTC by Bill Burns
Modified: 2010-05-18 20:21 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-18 20:12:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Bill Burns 2010-05-18 18:00:15 UTC 
Description of problem:
Install RHEL snapshot from scratch on a local disk. Selected
partitions, all went well. Decided to install a different
section and it does not give the same options to select
disk partitions, just blasts through and updates.

Version-Release number of selected component (if applicable):
DVD made from RHEL6.0-20100512.n.0

How reproducible:
Happened every time I tried it (3)

Steps to Reproduce:
1. install
2. try to do it again
3.
  
Actual results:
A useless exercise.

Expected results:
Should allow all options, even if the system was previously
installed.


Additional info:
none
Comment 2 David Lehman 2010-05-18 19:46:54 UTC 
Can you please describe in greater detail what series of selections you made?

> "Decided to install a different section"

I don't think I understand what you mean by this.

> and it does not give the same options to select
> disk partitions, just blasts through and updates.

What screens were displayed, which buttons did you click, and what did you see happening? Can you attach /tmp/anaconda.log (or /var/log/anaconda.log) from the second/subsequent install?
Comment 3 Bill Burns 2010-05-18 20:00:05 UTC 
Well I installed something like server and got no graphics, no X. So I started over to pick something else. And I was never able to see the screen to pick a different group to install and never able to see the screen that allows me to choose a custom partition layout. I worked around it by dd'ing a meg of zeros to /boot.
Comment 4 David Lehman 2010-05-18 20:05:51 UTC 
Please grab /var/log/anaconda.log from the newly installed system and attach it to this bug report.
Comment 5 David Lehman 2010-05-18 20:12:11 UTC 
On second thought, I guess your having somehow changed the behavior makes the log less than useful. There's no need to attach it if it's from a successful/normal install.

The behavior you describe is not normal, nor is it intended. I don't see how zeroing out any partition, especially /boot, could make the difference in whether or not this occurs.

I would need to know *exactly* what screens you saw, which options you selected, and what messages you saw or else be able to see the anaconda.log from the install attempt that never presented the partitioning choices in order to do anything with this bug report.

If you can provide that information, please reopen this bug.
Comment 6 Bill Burns 2010-05-18 20:21:02 UTC 
Right, I did a fresh install and all was well. Will try and reproduce when I can...
Note You need to log in before you can comment on or make changes to this bug.