Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When anaconda asks to format unformatted or LDL DASD disks, it is not clear which DASD disks will be formatted. Anaconda only shows device names (for example /dev/dasdh), which are not persistent and changes across reboots. Anaconda should show the DASD device ID of the disks to be formatted.
This needs to be fixed in both GUI and TUI mode.
Version-Release number of selected component (if applicable):
RHEL-7.1 GA
RHEL-7.2 Snap4 (anaconda-21.48.22.53-1.el7)
How reproducible:
always
Steps to Reproduce:
1. format one or more DASD disks using cpfmtxa in CMS
2. start the installation
3. select all disks
4. let anaconda create the partitions
5. review the list of disks to be formatted using dasdfmt
Actual results:
unable to identify what DASD disks will be formatted
Expected results:
able to identify what DASD disks will be formatted - anaconda should show the device ID in any form, for example "0.0.3024"
Work around:
Log in via ssh during the installation and run "lsdasd" to match device names and device IDs.
Device IDs are shown in GUI installation, but not in TUI installation:
The following unformatted or LDL DASDs have been detected on your system. You
can choose to format them now with dasdfmt or cancel to leave them unformatted.
Unformatted DASDs cannot be used during installation.
/dev/dasde
/dev/dasdd
Warning: All storage changes made using the installer will be lost when you
choose to format.
Tested with anaconda-21.48.22.79-1.el7, moving back to ASSIGNED.
Comment 9Samantha N. Bueno
2016-08-26 16:59:04 UTC
This is actually not going to be simple to fix -- at least, not simple (non-invasive) enough for 7.3 at this point. So I'm going to defer it until 7.4.
This is fixed and anaconda shows the IDs of the disks before running dasdfmt in text UI:
The following unformatted or LDL DASDs have been detected on your system. You
can choose to format them now with dasdfmt or cancel to leave them unformatted.
Unformatted DASDs cannot be used during installation.
/dev/dasdf (0.0.3126)
/dev/dasdb (0.0.3026)
Warning: All storage changes made using the installer will be lost when you
choose to format.
Proceed to run dasdfmt?
Verified with anaconda-21.48.22.128-1.el7.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0671