Bug 678823

Summary: can't find installation device
Product: [Fedora] Fedora Reporter: No Importa <fbarbera>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 14CC: anaconda-maint-list, fbarbera, jonathan, mmaslano, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 606299 Environment:
Last Closed: 2011-02-21 02:35:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description No Importa 2011-02-20 00:51:02 UTC
+++ This bug was initially created as a clone of Bug #606299 +++

Description of problem:
The installation of Fedora failed choosing of language, because anaconda had asked where is image/stage2 stored. I had ATA disc with three nfts partitions and one clean without file system. 
Anaconda offer choose from /dev/sda{1,2,3} even if it booted from /dev/sdb. sdb wasn't found during installation process. 

Version-Release number of selected component (if applicable):
anaconda-13.42-1.fc13

How reproducible:
On flash disc create boot minimal installation by standart procedure documented on fedoraproject documentation.

Steps to Reproduce:
1. choose lanaguage
2. try to find right device
3. repeat :)
  
Actual results:


Expected results:


Additional info:

--- Additional comment from mmaslano on 2010-06-21 08:00:41 EDT ---

Probably every ~10th installation was able find sdb and was successful until this #606307. When I had to choose which disc will be used for installation I had to check both sda and sdb, because if I choose only sda (ATA disc), then the disc couldn't be found, even if later it was possible to install. If I choose both discs, I was able continue in installation. IMHO there is some problem with detection of discs during the installation process.

--- Additional comment from mmaslano on 2010-06-21 08:06:04 EDT ---

My hardware profile if this is any help:
http://www.smolts.org/client/show/pub_d36889b8-c8ee-4a65-8710-f9e459ec5718

--- Additional comment from clumens on 2010-08-11 13:09:57 EDT ---

Please attach /tmp/anaconda.log from your failed installation attempt in the original comment to this bug report.  Comment #1 describes a different problem.  If you can describe how you booted and what kind of installation you are trying to perform (HTTP/FTP, HD ISO, etc.) that would also be helpful.

--- Additional comment from fbarbera on 2011-02-19 19:41:34 EST ---

I've found this error from version 11 to the actual core 14 (not on Fedora 10 Cambridge), and it's caused by a "timeout" on the SATA while trying to identify the type of drive. It seems like the driver or the communications buffer doesn't negotiate the information on the right mode. Curiously, this doesn't happens on core 8 to 10 (checked on those versions)

Maybe, the info about the drive can be useful:
(Reported by Device Manager of Fedora 10)
Model: ST3320813AS
Vendor: ATA
Device File: /dev/sda
Serial Number: SATA_ST3320813AS_9xxxxxxx (Modified for sec reasons)
FirmWare version: SD23
Connection type: Internal
Removable media: no
Drive capacity: xxx gb
Partitioning: Master Boot Record

Comment 1 No Importa 2011-02-20 00:55:53 UTC
Found this problem on other linux based systems (Ubuntu)

Comment 2 Chris Lumens 2011-02-21 02:35:15 UTC

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