Bug 300721

Summary: Reusing existing partitions during install gets exception
Product: [Fedora] Fedora Reporter: Barry Scott <barry.scott>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 8   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-05 15:36:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 235703, 257221    
Attachments:
Description Flags
saved exception from anaconda none

Description Barry Scott 2007-09-21 16:18:31 UTC 
Description of problem:

Anaconda exception using custom partitioning.

How reproducible:

Install F8 with default disk layout + partition for /home.

Install F8 again this time choose custom disk config and setup
the existing partitions to be reformated with the exception of /home.
I think I missed off assigning /boot.

Click Next get the attached exception.
Comment 1 Barry Scott 2007-09-21 16:18:31 UTC 
Created attachment 202521 [details]
saved exception from anaconda
Comment 2 Linus Torvalds 2007-09-29 00:42:10 UTC 
I seem to be getting something very similar, using the KDE LiveCD.

However, I don't even need to do any custom disk config, but I started with
a totally wiped disk that had no partition table at all. Anaconda correctly
warned me about having to create a whole new partition table, but then when
it was supposed to do the partitioning, it warned that it couldn't invalidate
the kernel partition support on /dev/sda2 (which didn't exist originally,
so I'm not surprised - you need to open /dev/sda).

I pressed "ignore", but that just caused an exception when trying to actually
mount the newly created partitions.

Re-doing the install didn't help, but rebooting the box entirely did: at that
point the kernel noticed the new partitioning and it's now installing.
Comment 3 Jeremy Katz 2007-10-05 15:33:26 UTC 
Actually, I see what's going on here.  Fix coming up in a minute.
Comment 4 Jeremy Katz 2007-10-05 15:36:16 UTC 
Okay, tested and works.  Fix committed to CVS and should be in rawhide of tomorrow