Bug 484528 - Fedora 11 install failed
Summary: Fedora 11 install failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: hal
Version: 11
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-07 23:24 UTC by Les Hazelton
Modified: 2010-06-28 11:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 11:12:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Les Hazelton 2009-02-07 23:24:26 UTC
Description of problem:
I tried to install the Fedora 11 - Alpha DVD on my IBM ThinkCentre (8183) system but could not. The DVD boots corectly and gets past the language selection and media check. It then notices that one of the drives in the system is partitioned GUID/GPT for apple HPFS+.

I select "ignore the drive" since I plan to install on one of the MBR partitioned drives. At that point I get an error panel and the install fails. This did not happen with fedora 10 using the same drive configurations.


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


How reproducible:
I tried 3 times - same result each time

Steps to Reproduce:
1. as stated in description
2.
3.
  
Actual results:
install failed in early stages

Expected results:
a clean install as I had in Fedora 10

Additional info:

Comment 1 Scott Glaser 2009-04-23 18:56:21 UTC
Have you tried the F11 Beta or have you tried installing latest version of Rawhide? In either case, can you let us know whether the issue is still happening, and give the current version of the HAL packages you're using?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Les Hazelton 2009-04-23 23:48:03 UTC
I had not tried the F11-Beta.  I am DL the DVD now and will test as soon as it finishes.  Should have an answer by 2009-04-24.  Sorry for delay.

Comment 3 Les Hazelton 2009-04-24 19:26:46 UTC
(In reply to comment #2)
> I had not tried the F11-Beta.  I am DL the DVD now and will test as soon as it
> finishes.  Should have an answer by 2009-04-24.  Sorry for delay.  

I tested with the F11-Beta-DVD this afternoon. I have no idea if the original problem is still there.  It failed much earlier this time.

I selected the media test option and it passed.

I selected Install / Upgrade, selected the default language (En), Keyboard etc.., then selected "Install Anyway" when asked.  I saw a panel about searching for storage devices and then the screen went to text.  It ended with a statement that is was safe to re-boot.

I paged back as far as I could and copied some of the error text.  It said in part:

Installer Exited Abnormally [1/1]
Info: Possible Circular Locking Dependency
2.6.29-0.258.2.3.RC8_Git2.F11.i586
SH/1665 Is trying to acquire a lock
(&type->S_umount_Key#26 {---},at [<c04ab8a6>] Deactivate_Supper

But Task is already holding lock ...
which lock already depends on new lock

2 locks held
#0 (&bdev->bd-mutex)
#1 (&lo->lo_ctl11.5.0.38-mutex)

There were lots of register address/contents in there, but way too many for me to copy down unless absolutely required.

Sorry I couldn't provide better results.

Comment 4 Bug Zapper 2009-06-09 11:07:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Scott Glaser 2009-09-09 13:06:11 UTC
Have you tried with the latest hal package in Fedora 11 or tried Rawhide? In
either case, can you let us know whether the issue is still happening, and give
the current version of the HAL packages you're using?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Les Hazelton 2009-09-10 21:02:47 UTC
I just downloaded a copy of the released fedora 11 i386 DVD iso and tried another install. The bug is still there.  You asked if I had tried the latest hal package.  I have no idea what you mean.  I cot the latest fedora 11 install DVD and tried to use it to install fedora.  It failed just as I described in the first bug report and it was using whatever version of hal is on the dvd.

Comment 7 Bug Zapper 2010-04-27 12:52:49 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2010-06-28 11:12:34 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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