Red Hat Bugzilla – Bug 1269174
Unable to identify DASD devices before formatting them with dasdfmt
Last modified: 2017-08-22 06:57:37 EDT
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.2 Snap4 (anaconda-22.214.171.124-1.el7)
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
unable to identify what DASD disks will be formatted
able to identify what DASD disks will be formatted - anaconda should show the device ID in any form, for example "0.0.3024"
Log in via ssh during the installation and run "lsdasd" to match device names and device IDs.
Created attachment 1080245 [details]
Created attachment 1080254 [details]
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.
Warning: All storage changes made using the installer will be lost when you
choose to format.
Tested with anaconda-126.96.36.199-1.el7, moving back to ASSIGNED.
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.
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/1147