Red Hat Bugzilla – Bug 1010017
Anaconda crashes manipulating custom partitions and just generally misbehaves
Last modified: 2014-09-16 09:33:04 EDT
Description of problem:
Trying to install on a 1/2T Passport USB3 from a Fedora 19 DVD.
In short I can't:
- create a custom install target partitions
- assume a preconfigured install target partitioning
- delete existing install target partition maps
All of these options lead to completely erroneous error messages and crashes...
Anadonda (19-30.13.1) refuses to let me use custom partitioning. I tried two approaches, using the interface to create custom partitioning and pre partitioning the disk on another linux box.
In both cases, I have swap, boot, root(/) and home created and assigned as target partitions, anaconda then complains that there is no room to install.
Your current Fedora software selection requires 6.74 gigabytes of available space including 2.89
GB for software and ....blah blah
I've told it to reformat, but there is still a preserve flag on it that crashed anaconda when I try to remove it. Anaconda Crashes when I delete all partitions on the drive and try to recreate the partition table. (2x)
Installing on a usb3 drive on a Mac Air. Sorry, I don't have the confidence in this installer to let it do what it wants, and it refuses to do what I want.
This is a showstopper for installing fedora 19 in this way. It appears to be a my way or the highway thing.
(Also no wireless because if incomplete connection interface, but this has been deemed not a bug)
Try to create a custom partition table (non LVM) in a usb3 drive (WD Passport 1/2T) and install to it. Anaconda says there is no room in spite of having a partition table that looks like this:
/home 363GB sdb4
swap 4GB sdb2
/boot 10GB sdb1
/ 100GB sdb3 (insists on reformat, although it is clean, still, no joy)
Manipulation of the partitioning leads to crashes.
Please attach the traceback file from the crash along with any other log files that are in /tmp
I'm installing from a USB DVD to a USB3 drive with a Mac Air in the middle.
Is there a way to configure this so I have a /tmp I can read after a crash?
You can switch to a virtual terminal after the crash by hitting Ctrl+Alt+F2, or you can use the exception dialog to report a bug with the log files attached.
Please read through the storage portion of the installation guide:
I can't supply the data requested.