Bug 191715

Summary: Can't install OS on SCSI system
Product: [Fedora] Fedora Reporter: Joseph Perrin <jap>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-19 03:13:53 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:
Attachments:
Description Flags
/tmp/anaconda.log
none
The file: /tmp/syslog none

Description Joseph Perrin 2006-05-15 13:25:47 UTC 
Description of problem:
Installation of FC5 fails to find any system disks to install on.  


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

How reproducible:
Each install attempt!


Steps to Reproduce:
1. Begin FC5 install via CD (non-SCSI)  I choose "Skip", (Media is fine),
"English"...
2. It says: "Warning: No hard drives have been found.  You probably need to
manually..."  I say "Yes".
3. I choose "Add Device", and pick "Adaptec 29xx series (aic7xxx)", and say "Done".
4. After it searches for existing installations, it fails with: "No drives Found".
  
Actual results:
A simple upgrade is now an extended downed server.  :-(


Expected results:
Need I say it?


Additional info:
Had similar goofy FC5 install issues on a machine with an Adaptec AVA-2906 card,
(for a scanner).  I had to physically remove the card to install OS.  Can't
easily do that in this case.  ;-)  (Or is that the whole point?)
Comment 1 David Cantrell 2006-05-15 13:31:05 UTC 
Can you attach /tmp/anaconda.log?
Comment 2 Joseph Perrin 2006-05-15 13:52:05 UTC 
Created attachment 129056 [details]
/tmp/anaconda.log
Comment 3 Jeremy Katz 2006-05-15 18:52:23 UTC 
Can you also attach /tmp/syslog?
Comment 4 Joseph Perrin 2006-05-15 19:20:44 UTC 
Created attachment 129110 [details]
The file: /tmp/syslog
Comment 5 Joseph Perrin 2006-05-15 19:57:06 UTC 
I've heard some discussions about this being a BIOS related issue.  The BIOS on
the Adaptec is up to snuff, but the MB is another question.  I'm flashing it
just to make sure.  It certainly can't hurt!
Comment 7 Joseph Perrin 2006-05-16 16:40:01 UTC 
*Any* useful status update would be greatly appreciated.  Tell me to bag my SCSI
gear if it means I'll be up any time soon!
Comment 8 Joseph Perrin 2006-05-18 22:31:17 UTC 
After bagging my SCSI hardware, (which pissed me off greatly), I bought 2 new
IDE disks, which then worked.  *However*, after successfully loading OS, my NIC
card couldn't be found.  Seriously folks, It's a 3c59x...  I put 7 different
brands of NIC card in that machine, and BIOS finds all of 'em, but this
stinkining OS doesn't see a blasted thing!  FC4 finds them just fine, FC3, FC1,
RH9, RH8 all find them.  --My Dog can even find 'em!  It's clear FC5 is PCI blind!  

After a couple of hundred dollars in new hardware, bought out of desperation and
now *two* weeks offline, I need a frickin' work around so I can get this blasted
web server back online!  At some point you have to give *back* some information!
 Now is the time!  I've been around since kernel 0.96, but I'm *so* completely
disappointed as of late.  :-(
Comment 9 Joseph Perrin 2006-05-19 03:13:53 UTC 
Fixed by boot kernel option: pci=noacpi.  Something must've changed that broke
this in FC5!