Description of problem: Custom partitioning. Delete all partitions. Automatically configure. Modify LVM to RAID5. Version-Release number of selected component: anaconda-21.48.3-1 The following was filed automatically by anaconda: anaconda 21.48.3-1 exception report Traceback (most recent call first): File "/tmp/updates/blivet/devicelibs/lvm.py", line 223, in pvcreate raise LVMError("pvcreate failed for %s: %s" % (device, msg)) File "/tmp/updates/blivet/formats/lvmpv.py", line 129, in create lvm.pvcreate(self.device) File "/tmp/updates/blivet/deviceaction.py", line 555, in execute options=self.device.formatArgs) File "/tmp/updates/blivet/devicetree.py", line 354, in processActions action.execute() File "/tmp/updates/blivet/__init__.py", line 354, in doIt self.devicetree.processActions() File "/tmp/updates/blivet/__init__.py", line 214, in turnOnFilesystems storage.doIt() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 178, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) LVMError: pvcreate failed for /dev/md/pv00: running lvm pvcreate --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } --dataalignment 1024k /dev/md/pv00 failed Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/ppc/ppc64/vmlinuz inst.vnc inst.sshd ip=9.5.178.25::9.5.178.1:255.255.255.0:ppc64lehamzytest2.rch.stglabs.ibm.com:eth0:none nameserver=9.5.175.8 bootdev=eth0 inst.updates=http://dlehman.fedorapeople.org/updates/updates-1109244.1.img executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.16.1-301.fc21.ppc64le product: Fedora-Server release: Cannot get release name. type: anaconda version: 21 Potential duplicate: bug 950145
Created attachment 938508 [details] File: anaconda-tb
Created attachment 938509 [details] File: anaconda.log
Created attachment 938510 [details] File: environ
Created attachment 938511 [details] File: lsblk_output
Created attachment 938512 [details] File: nmcli_dev_list
Created attachment 938513 [details] File: os_info
Created attachment 938514 [details] File: program.log
Created attachment 938515 [details] File: storage.log
Created attachment 938516 [details] File: syslog
Created attachment 938517 [details] File: ifcfg.log
Created attachment 938518 [details] File: packaging.log
There is evidence here of multiple installs using various subsets of available disks. If we clear a subset of the member devices insufficient to assemble the array, we cannot possibly hope to have cleared the array data from the insufficient subset devices given the structure of raid5 data.
Created attachment 980520 [details] anaconda error LVMError pvcreate failed for /dev/md/1: running lvm pvcreate --dataalignment 1024k /dev/md/1 failed
start point: --snip-- % parted -s /dev/sd[a-b] print Model: ATA ST3000DM001-1CH1 (scsi) Disk /dev/sda: 3001GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 17.4kB 3500MB 3500MB primary 2 3500MB 20.0GB 16.5GB primary --snap-- Aim: --snip-- [root@c7-test ~]# parted /dev/sd[a-b] print Model: ATA ST3000DM001-1CH1 (scsi) Disk /dev/sda: 3001GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 1 1049kB 2097kB 1049kB bios_grub 2 2097kB 264MB 262MB ext2 raid 3 264MB 3001GB 3000GB raid --snap-- Aim is reached only from second attempt(kickstart autoinstall, with the same steps as in first). First attempt stops at attached error.
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.