Bug 589150 - Anaconda crashes while formatting a disc with large partition length
Summary: Anaconda crashes while formatting a disc with large partition length
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 12
Hardware: x86_64
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: 2010-05-05 14:14 UTC by Fabio Martins
Modified: 2010-05-10 18:26 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-10 18:26:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
anaconda's log with the unhandled exception being raised (90.72 KB, text/plain)
2010-05-05 14:14 UTC, Fabio Martins
no flags Details

Description Fabio Martins 2010-05-05 14:14:19 UTC
Created attachment 411626 [details]
anaconda's log with the unhandled exception being raised

Description of problem:

An unhandled exception is raised inside anaconda installer when trying to install Fedora in an Areca ARC-1220 storage with 6TB of capacity (5 discs in RAID6), motherboard Intel DP55WB.

Version-Release number of selected component (if applicable):

anaconda version 12.46 on x86_64 starting

How reproducible:

Installing Fedora in a device greater than 6TB.

Steps to Reproduce:
1.Areca ARC-1220 pci raid controller with 5 x 1.5TB discs in RAID6
2.The raid is detected normally by Fedora as scsi
3.Select it and try to install Fedora, the unhandled exception is raised
  
Actual results:

Unhandled Exception. anaconda log attached.

Expected results:

Fedora being installed in the RAID

Additional info:

anaconda log attached.

Comment 1 Chris Lumens 2010-05-05 14:59:42 UTC
Is this still a problem with F13 beta?

Comment 2 Fabio Martins 2010-05-06 04:54:41 UTC
Need 2 days to try with F13 beta

Comment 3 Fabio Martins 2010-05-10 18:11:01 UTC
cant reproduce with F13 beta

Comment 4 Chris Lumens 2010-05-10 18:26:05 UTC
Great, thanks for retesting.


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