Created attachment 687675 [details] full log I was doing a kickstart installation of F-18 in the Hercules emulator to a FBA disk. Version-Release number of selected component (if applicable): anaconda 18.37.11
FWIW F-16 could be installed on FBA disk correctly
I've tried to update the installation environment with parted-3.1-10.fc18 using updates.img, still no change from an installation in progress: [anaconda root@s390x ~]# cat /proc/partitions major minor #blocks name 7 0 160632 loop0 7 1 1048576 loop1 7 2 524288 loop2 94 0 8388608 dasda 94 1 204800 dasda1 94 2 2097152 dasda2 94 3 6086528 dasda3 253 0 1048576 dm-0 [anaconda root@s390x ~]# fdisk -l /dev/dasda Disk /dev/dasda: 8589 MB, 8589934592 bytes, 16777216 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes [anaconda root@s390x ~]#
Created attachment 687953 [details] hercules.log
Created attachment 687954 [details] anaconda.log
Created attachment 687955 [details] storage.log
Created attachment 687956 [details] program.log
Created attachment 687957 [details] packaging.log
Created attachment 687958 [details] kickstart
I suspect the FBA DASD support in parted being wrong. It can be demonstrated on VDISK (virtual FBA disk) where parted and fdisk behave differently. I will open a new bug for it.
Or there can be a difference between LPAR (that's what Hercules emulates) and z/VM guest. Please see also the thread on the Fedora/s390x list - http://lists.fedoraproject.org/pipermail/s390x/2013-January/000574.html
Reproduced with F19/s390x in hercules-3.09-1.fc19.x86_64. For some reason, permission of /sys/firmware/reipl/ccw/loadparm is set to 444 during installation in hercules. On a real hardware running in z/VM, permission is set to 644. Dan gave me an advise to change the permission to 644 during the installation and it resolved this issue, installation finished without any traceback.
It looks as a deficiency in Hercules itself, the default permission for /sys/firmware/reipl/ccw/loadparm is 0644, but it's reduced to 0444 if diag308 is not working. from arch/s390/kernel/ipl.c ... static int __init reipl_ccw_init(void) { int rc; reipl_block_ccw = (void *) get_zeroed_page(GFP_KERNEL); if (!reipl_block_ccw) return -ENOMEM; if (MACHINE_IS_VM) { if (!diag308_set_works) sys_reipl_ccw_vmparm_attr.attr.mode = S_IRUGO; rc = sysfs_create_group(&reipl_kset->kobj, &reipl_ccw_attr_group_vm); } else { if(!diag308_set_works) sys_reipl_ccw_loadparm_attr.attr.mode = S_IRUGO; rc = sysfs_create_group(&reipl_kset->kobj, &reipl_ccw_attr_group_lpar); } if (rc) return rc; reipl_block_ccw_init(reipl_block_ccw); if (ipl_info.type == IPL_TYPE_CCW) { reipl_block_ccw->ipl_info.ccw.devno = ipl_devno; reipl_block_ccw_fill_parms(reipl_block_ccw); } reipl_capabilities |= IPL_TYPE_CCW; return 0; }
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.