Description of problem: - Both drives initially had ntfs partitions, however the anaconda installer does give you the option to modify the disks, where I could have deleted, in this case it would not - They are running on a MARVELL SATA III controller - Drives are being run as AHCI devices - Went through and deleted both disks' partitions via fdisk to ensure all was clear, did no re-create parititions and intentionally left them that way - Anaconda failed again, indicating that the drives only had 5.6MB available between the two of them - This time, created new primary partitions with 8e format via fdisk, and it failed with the same error. - The motherboard is not automatically setting the drives as a RAID 0 stripe, however, anaconda continues referring to each drive as being in a stripe The following was filed automatically by anaconda: anaconda 18.37.11 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 832, in initializeDisk raise ValueError("cannot initialize a disk that has partitions") File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 807, in clearPartitions self.initializeDisk(disk) File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 445, in execute storage.clearPartitions() File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1480, in doKickstartStorage ksdata.clearpart.execute(storage, ksdata, instClass) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 399, in _doExecute doKickstartStorage(self.storage, self.data, self.instclass) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) ValueError: cannot initialize a disk that has partitions Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 cmdline_file: initrd=initrd0.img root=live:UUID=5EEE-CA71 rootfstype=vfat ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: python-libs-2.7.3-13.fc18.x86_64 package: anaconda-18.37.11-1.fc18.x86_64 packaging.log: product: Fedora release: Fedora release 18 (Spherical Cow) type: libreport version: 18
Created attachment 701233 [details] File: anaconda.log
Created attachment 701234 [details] File: environ
Created attachment 701235 [details] File: ifcfg.log
Created attachment 701236 [details] File: messages
Created attachment 701237 [details] File: program.log
Created attachment 701238 [details] File: storage.log
Created attachment 701239 [details] File: anaconda-tb
Trying to run /usr/bin/liveinst to install FC18 onto HP Proliant MicroServer that has RAID 1 set up with 2 1TB disks Package: anaconda-18.37.11-1.fc18.x86_64 OS Release: Fedora release 18
Trying to install Fedora 18 on top of an existing Fedora 17 install and reuse the existing partitioning/LVM configuration. System crashed after entering "Let me do my own configuration." Package: anaconda-18.37.11 OS Release: Fedora release 18
Looks like Bug 862613 - ValueError: cannot initialize a disk that has partitions I have two disks in a RAID which due to needing to multi-boot and share these disks I am using BIOS dmraid. No matter what I try (in this instance and initially, manual paritioning on F18 install DVD for the RAID-0 Stripe) when I select the disks with a pre-existing partition with NTFS partitions, anaconda crashes. This is repeatable no matter what I have tried with the install - Will try workaround with F17 install and upgrade or will attempt to hide the partitions, manually partition, then fix the partitions after install if I can get that to work - but as of now, F18 will not install on a disk with existing partitions, which means in a dual-boot environment where disk is shared, this is a problem. Something to note, previously when I dedicated 1 disk to NTFS and 1 disk to F18, trying to partition the blank F18 dedicated disk did not cause issues, only when trying to partition a drive with other filesystem types (NTFS in this case). I later decided to switch to using a stripe with the two disks and dmraid. Package: anaconda-18.37.11 OS Release: Fedora release 18
Boot DVD Test DVD and install choose english lang chose Closest Mirror for source chose Mate desktop environment, picked some packages from the right side of screen chose manual partioning next screen crashed Jeff Package: anaconda-18.37.11 Architecture: i686 OS Release: Fedora release 18
(In reply to comment #11) > Boot DVD > Test DVD and install > choose english lang > chose Closest Mirror for source > chose Mate desktop environment, picked some packages from the right side of > screen > chose manual partioning > next screen crashed > Jeff > > > Package: anaconda-18.37.11 > Architecture: i686 > OS Release: Fedora release 18 These disks didn't have any partitions to begin with but they are attached to a Highpoint raid controller. lspci shows it as HPT372A/372N. raid 0 configuration. JEff
(In reply to comment #12) > (In reply to comment #11) > > Boot DVD > > Test DVD and install > > choose english lang > > chose Closest Mirror for source > > chose Mate desktop environment, picked some packages from the right side of > > screen > > chose manual partioning > > next screen crashed > > Jeff > > > > > > Package: anaconda-18.37.11 > > Architecture: i686 > > OS Release: Fedora release 18 > > These disks didn't have any partitions to begin with but they are attached > to a Highpoint raid controller. lspci shows it as HPT372A/372N. raid 0 > configuration. > > JEff FWIW the installation completed normally using the DVD media as the source, same steps but chose LXDE because MATE is not available from there.
Installing fedora18/KDE-spin on a USB3 disk on a macbook air 2012. Installer crashes on unknown errors in multiple places when attempting to either reclaim space on the external disk or commit changes to its partition table when re-partitioned manually through the installer. * Fedora18 install media booted from USB2 device. * The mac's built-in disk has a (non-hybrid) GPT partition table, which the installer also sees and may be confusing it. Package: anaconda-18.37.11-1.fc18.x86_64 OS Release: Fedora release 18
The external disk I was trying to repartition had an AFS-type partition table too (disk pointed that out). dd if=/dev/zero of=/dev/mysdadevicedonotcopypastethis bs=1M count=1 made problem go away
While installing on a PowerMac PPC G5, manually setting up partitions caused the error. Package: anaconda-18.37.11 Architecture: ppc64 OS Release: Fedora release 18
Select customise partitioning during install of encrypted system Package: anaconda-18.37.11 OS Release: Fedora release 18
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.