Bug 505519 - Manual disk partitioning misbehaves (unbootable /boot, "too many primary partitions" etc)
Summary: Manual disk partitioning misbehaves (unbootable /boot, "too many primary part...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 11
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-12 08:14 UTC by Miroslav Pragl
Modified: 2009-06-16 16:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-16 16:07:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miroslav Pragl 2009-06-12 08:14:16 UTC
Description of problem:
This is really hard to describe. I just wanted to install F11 over my existing F10 system. There were three existing primary partitions (Win XP, Win7, Linux /boot (GRUB)) and two logical drives in extended partition (swap and /)

I didn't want to upgrade so I chosen manual disk partitioning, assigned existing partitions to /boot (EXT3) / (EXT4) and swap with formating.

First time installer HUNG formatting swap (really frozen so no way to switch to textual screen)

Second time everything SEEMED to be OK but GRUB didn't launch on bootup (MBR showed "Missing operating system" message. I re-checked /boot partition using live CD and it had FAT filesystem (!)

Third time I got "Too many partition tables" error message although I CHOSEN 3 primary and rest in extended.

Fourth time disk was OK

I didexactly SAME layout every time but I played A LOT with everything (deleting and creating partitions over...)

I know this is some BFM and agree it's virtualli impossible to reproduce. Just hope other users will be able to comment more precisely.

MP

Comment 1 Andy Lindeberg 2009-06-16 16:07:11 UTC
Without more data, we can't do anything to fix this. If anybody can update with more precise information, please feel free to reopen this bug.


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