Bug 494386 - F11 beta crashes at disk.commit step
Summary: F11 beta crashes at disk.commit step
Keywords:
Status: CLOSED DUPLICATE of bug 492154
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: powerpc
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-06 16:59 UTC by Tom Lane
Modified: 2013-07-03 03:22 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-04-06 17:04:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
traceback (170.30 KB, text/plain)
2009-04-06 16:59 UTC, Tom Lane
no flags Details

Description Tom Lane 2009-04-06 16:59:31 UTC
Created attachment 338359 [details]
traceback

Description of problem:
I'm trying to install from the F11 beta ppc netinst CD onto an Apple Powerbook Pismo (yeah, it's
ancient, but it's the only spare hardware I've got).  It gets to the "writing partitioning to disk"
stage and then fails, but not before having wiped the old disk partition info :-(

The machine had had F-9 as well as OS9 and OSX on it in different partitions.  I first tried the
"replace existing Linux system" option; that crashed in the same place, but with a traceback
that I think was different from the one attached (unfortunately I did not save it).  I then tried
the "use entire drive" option, but that still crashes.  I was able to save off the traceback using
the "scp trace to someplace" function, so I'll attach it.

Version-Release number of selected component (if applicable):
whatever's on the beta ISO

How reproducible:
100%

Steps to Reproduce:
1. try to install ...
2.
3.
  
Actual results:


Expected results:


Additional info:
I'm using text mode install because graphical install doesn't work at all (screen is unreadable)

Comment 1 Chris Lumens 2009-04-06 17:04:27 UTC

*** This bug has been marked as a duplicate of bug 492154 ***


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