Bug 568910 - Anaconda 13-Alpha.RC4: unable to partition
Summary: Anaconda 13-Alpha.RC4: unable to partition
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-26 21:45 UTC by Milan Kerslager
Modified: 2010-03-02 15:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-02 15:58:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Anaconda backtrace log (partition failed) (104.27 KB, text/plain)
2010-02-26 21:45 UTC, Milan Kerslager
no flags Details

Description Milan Kerslager 2010-02-26 21:45:52 UTC
Created attachment 396685 [details]
Anaconda backtrace log (partition failed)

I booted 13-Alpha.RC4 in VirtualBox 3.1.4 (booted from Fedora-13-Alpha-i386-netinst.iso file). The autopartition failed (no room for LVM) with the same message like I reported in bug #567889, ie message:

The last window with failing message from anaconda was:

Could not allocate requested partitions:

not enough space for LVM requests.

[ OK ]

Then Anaconda backtraced (log attached), but the different way than in the bug #567889.

In the end I was unable to installl two latest Alpha prereleases.

Comment 1 David Lehman 2010-03-01 17:59:27 UTC
You are trying to install with a single disk with a capacity of 512MB? If so, it's going to take some effort to get Fedora installed. At the very least you will have to select "create custom layout" to set up your storage. If there is more than the one 512MB disk in the system, please switch to tty2 (ctl+alt+f2) and run 'parted -l' and then attach the full output to this bug report. Thanks.

Comment 2 Milan Kerslager 2010-03-02 06:16:33 UTC
Sorry this is my fault. When I recreated virtual machine, I pointed F13 to the wrong image (FreeDOS image).

Maybe there should be more descriptive error message.


Note You need to log in before you can comment on or make changes to this bug.