Description of problem: During an installation using the VNC method, when I select the option to manually partition disks as part of the Disk dialog results in the VNC pane going blank and a message "Pane has failed" (or similar) appearing in the bottom left corner of the ssh session started as part of the installation. Version-Release number of selected component (if applicable): Fedora 21 s390x How reproducible: Problem encountered both times attempted. (Reverted to text option to perform installation successfully.) Steps to Reproduce: 1. Begin installation as normal 2. ssh as user install 3. Select VNC as the method to install Fedora 4. Select the Disk dialog 5. Choose disks 6. Click on the checkbox for manual partitioning 7. Click on the "Done" button Actual results: VNC window goes black. Message "Pane has failed" (I may be paraphrasing) appears in bottom left of the ssh session Installation goes no further Expected results: Dialog for manually partitioning selected disks Additional info:
Neale, could you download the logs that are stored in /tmp in the running installation and attach them here?
Created attachment 966952 [details] Installation logs from /tmp Contents: tmp/anaconda.log tmp/ifcfg.log tmp/packaging.log tmp/program.log tmp/sensitive-info.log tmp/storage.log tmp/vncserver.log tmp/anaconda-yum.conf tmp/storage.state tmp/syslog
Something crashed in libparted. 19:01:14,016 WARNING kernel:[ 400.962738] User process fault: interruption code 0x40009 in libparted.so.2.0.1[3fff512f000+55000] 19:01:14,016 WARNING kernel:[ 400.962878] CPU: 0 PID: 1973 Comm: anaconda Not tainted 3.17.4-301.fc21.s390x #1 19:01:14,016 WARNING kernel:[ 400.962936] task: 0000000003143070 ti: 000000007a168000 task.ti: 000000007a168000 19:01:14,016 WARNING kernel:[ 400.962981] User PSW : 0705000180000000 000003fff5154d64 19:01:14,016 WARNING kernel:[ 400.963031] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 EA:3 19:01:14,016 WARNING kernel:[ 400.963031] User GPRS: 0000000000000200 0000000000000000 0000000000000000 0000000000000060 19:01:14,016 WARNING kernel:[ 400.963105] 0000000000000200 0000000000000000 0000000000000017 00000000a155d210 19:01:14,016 WARNING kernel:[ 400.963149] 0000000000495840 00000000a1c20740 00000000a057dca0 000003ffff83d060 19:01:14,016 WARNING kernel:[ 400.963257] 000003fffd07d000 000003fff5173028 000003fff5154b4e 000003ffff83ccf0 19:01:14,016 WARNING kernel:[ 400.963468] User Code: 000003fff5154d56: eb120004000d sllg %r1,%r2,4 19:01:14,016 WARNING kernel:[ 400.963468] 000003fff5154d5c: b9090012 sgr %r1,%r2 19:01:14,016 WARNING kernel:[ 400.963468] #000003fff5154d60: b90d0021 dsgr %r2,%r1 19:01:14,016 WARNING kernel:[ 400.963468] >000003fff5154d64: e310f0e80002 ltg %r1,232(%r15) 19:01:14,017 WARNING kernel:[ 400.963468] 000003fff5154d6a: 4030b0d2 sth %r3,210(%r11) 19:01:14,017 WARNING kernel:[ 400.963468] 000003fff5154d6e: a744004b brc 4,3fff5154e04 19:01:14,017 WARNING kernel:[ 400.963468] 000003fff5154d72: eba1000c000a srag %r10,%r1,12 19:01:14,017 WARNING kernel:[ 400.963468] 000003fff5154d78: e3b0d0080004 lg %r11,8(%r13) 19:01:14,017 WARNING kernel:[ 400.963813] Last Breaking-Event-Address: 19:01:14,017 WARNING kernel:[ 400.963908] [<000003fff5154b64>] 0x3fff5154b64
from syslog: 18:56:20,317 INFO kernel:[ 29.039212] dasd-eckd 0.0.0150: DASD with 4 KB/block, 2403360 KB total size, 48 KB/track, linux disk layout 18:56:20,317 INFO kernel:[ 29.245937] dasd-eckd 0.0.0151: DASD with 4 KB/block, 2403360 KB total size, 48 KB/track, linux disk layout 18:56:20,317 INFO kernel:[ 29.506263] dasd-eckd 0.0.0153: DASD with 4 KB/block, 2403360 KB total size, 48 KB/track, linux disk layout LDL disks caused this issue, see similar bugs 960523 or 707037. It is recommended to format DASD disks with CDL (compatible disk layout) before starting the installation: # dasdfmt -d cdl -b 4096 <device> There are RHEL-7 RFEs to show a warning message and format LDL disks with CDL: Bug 1170653 - [RFE] Anaconda warning for LDL low level formatted disks. Bug 1170656 - [RFE] Anaconda action for CDL formatting for LDL low level formatted disks. This bug can be used to track the same RFE in Fedora.
Isn't formatting the disk usually part of the installation process?
(In reply to Neale Ferguson from comment #5) > Isn't formatting the disk usually part of the installation process? If you have LDL DASDs, no. There is no official support for LDL DASDs and never has been, and the installer does not properly detect or handle them. See the RFEs Jan linked in comment 4; those fixes will be pushed upstream and make their way into Fedora once I complete the work for them.
Moving this to anaconda for f23, LDL patches need to be ported.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Reopening since this issue is still present in Fedora 23. I was able to reproduce it as described in comment 0 with LDL DASD, but it is also possible to reproduce it right after starting VNC, without any user interaction in GUI. Logs will be attached.
Created attachment 1101475 [details] backtrace
Created attachment 1101478 [details] storage.log
As we just discovered in bug 1244833 today, this bug is actually in parted, so reassigning.
parted-3.2-19.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-25836bb5b0
parted-3.2-18.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-3bd8d28f89
parted-3.2-19.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-25836bb5b0
parted-3.2-18.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-3bd8d28f89
parted-3.2-19.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
parted-3.2-18.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.