== Comment: #0 - MANAS K. NAYAK <maknayak.com> - 2013-05-09 02:34:19 == While installing Fedora19 Alpha ppc64 on P7 LPAR , 4 times I removed the files systems ,reclaimed & again created. When I returned back to Installation summary page, noticed "An unknown error occurred" (see the attached screen shot file "Screenshot-8.png"). --- Steps to Reproduce --- 1) Boot F19 Alpha ppc64 from Virtual DVD to install P7 LPAR 2) Select 3 or 4 Disks 3) reclaim all the spaces 4) went to custom partitioning (select "I want to review/modify my disks partitions before continuing") partitioning scheme as LVM. 5) Again clicked on "create them automatically " , then click on done. 6) Now again you came back to Installation summary page. 7) repeat step-2 to step-5, several times (may be three times), 8) Once you are done with step-7, repeat step-2 to step-5 once more and do not click on done. 9) Now change the device type to RAID for mount point / , and click on "Update setting" 10) again change RAID level "RAID1" to "RAID5" and click on "Update setting" . 11) Now click on done ... and you will see "Unknown Error occurred" error message on the install screen. --- Attached Files --- 1) Anaconda console logs captured during "Unknown error Occurred" anaconda.log anaconda-tb-KmNMuV program.log syslog storage.log 2) Installation Screenshots: Screenshot-1.png Screenshot-3.png Screenshot-5.png Screenshot-7.png Screenshot-2.png Screenshot-4.png Screenshot-6.png Screenshot-8.png Thanks... Manas == Comment: #16 - Kamalesh Babulal <kamaleshb.com> - 2013-05-09 07:43:47 == It looks similar to the bug raised on Fedora18 https://bugzilla.redhat.com/show_bug.cgi?id=862947
Created attachment 745633 [details] anaconda.log
Created attachment 745634 [details] anaconda-tb-KmNMuV
Created attachment 745635 [details] program.log
Created attachment 745636 [details] syslog
Created attachment 745637 [details] storage.log
Created attachment 745638 [details] Screenshot-1.png
Created attachment 745639 [details] Screenshot-2.png
Created attachment 745640 [details] Screenshot-3.png
Created attachment 745641 [details] Screenshot-4.png
Created attachment 745642 [details] Screenshot-5.png
Created attachment 745643 [details] Screenshot-6.png
Created attachment 745644 [details] Screenshot-7.png
Created attachment 745645 [details] Screenshot-8.png
------- Comment From maknayak.com 2013-05-29 13:39 EDT------- This issue is reproducible on Fedora 19 Beta ppc64. I selected automatic partition on a multipath device ...and the same issue got reproduced.
Created attachment 812781 [details] 93154_bug_reproduible ------- Comment on attachment From khusriva.com 2013-10-16 06:50 EDT------- I am able to reproduce this bug on fedora20. Please find the attachment for the screenshot.
Created attachment 813622 [details] anaconda logs tarball ------- Comment on attachment From khusriva.com 2013-10-18 06:38 EDT------- Please find the attachment for logs.tar for all the related logs.
------- Comment From gusld.com 2013-10-22 19:55 EDT------- *** Bug 98803 has been marked as a duplicate of this bug. ***
------- Comment From gusld.com 2013-10-22 20:34 EDT------- Khushboo, you have hit a different issue than the original bug reported here during the F19 cycle. For the F20 bug, see https://bugzilla.redhat.com/show_bug.cgi?id=1020849 Given we can't fix bugs in the installer after the release, I'm closing this bug. If you encounter this same issue on F20 please file another bug.