Created attachment 1034326 [details]
Data collected by anaconda after error encountered
Description of problem:
When setting the root password anaconda crashes. Debug dialog is entered and data collected. Attached to this report
Version-Release number of selected component (if applicable):
Fedora 22 - s390x
Happened on first attempt, haven't attempted another installation
Steps to Reproduce:
1. Use VNC method for installation
2. Proceed through installation dialogs
3. Set root password
Password set and dialogs continue
Created attachment 1034358 [details]
For some reason, your ECKD-DASDs are recognized as DASDs with the linux disk layout (LDL), although the label is VOL1, which suggests the compatible disk label (CDL):
01:00:56,531 INFO kernel:[ 30.845511] dasd-eckd 0.0.0150: New DASD 3390/0A (CU 3990/04) with 3338 cylinders, 15 heads, 224 sectors
01:00:56,532 INFO kernel:[ 30.857594] dasd-eckd 0.0.0150: DASD with 4 KB/block, 2403360 KB total size, 48 KB/track, linux disk layout
01:00:56,532 INFO kernel:[ 30.862294] dasdb:VOL1/ 0X0150: dasdb1
Anyway, LDL DASDs are not recommended to use during the installation and future versions of the installer should warn you and allow you to format LDL DASD disks with CDL.
A possible work around is to use dasdfmt and format your DASDs with CDL and restart the installation.
You can format them in the installation environment, after switching to shell by pressing <CTRL+b> <2> in your ssh session:
# dasdfmt -d cdl -b 4096 /dev/$device
Now that I've finished the s390 plugin for libblockdev and it's available in rawhide, it should be quite easy to add functionality in the installer to detect and format LDL DASDs to CDL.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.