Bug 710550

Summary: Red Hat 5.6 x86 can't read a driver disk from internal CDROM
Product: Red Hat Enterprise Linux 5 Reporter: apfeiffe
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6CC: anthony.cheung, anthony.cheung, apfeiffe, atodorov, bharath.bhushan, ddettke, huangj, matt.woempner, nkattang, ovasik, pbokoc, phinchman, sapna.francis, william.gens
Target Milestone: rcKeywords: OtherQA
Target Release: ---Flags: bcl: needinfo? (apfeiffe)
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-18 23:19:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 921048, 928844    
Attachments:
Description Flags
Requested logs none

Description apfeiffe 2011-06-03 16:48:49 UTC
Description of problem:
I am installing Red Hat 5.6 x86 and need to load a driver update disk.  At the install screen, I specify: linux mpath dd

On the screen that asks if I have a driver disk to load I choose yes. It proceeds to move forward with the install and does not prompt for which drive has the driver update disk.  The driver update disk is never loaded.

Version-Release number of selected component (if applicable):
Red Hat 5.6 x86

How reproducible:
Always

Steps to Reproduce:
1. Start RH 5.6 x86 installer on DL380 G7
2. At install screen, type: linux mpath dd
3. When it asks if you have a driver disk, choose 'yes' and then it continues with the install without loading a driver update.
  
Actual results:
Fails to load a driver update disk

Expected results:
Should prompt for which driver the driver update disk is in and install the driver.

Additional info:
Workaround is to use an external cdrom drive for the driver update.

Comment 1 apfeiffe 2011-06-03 16:49:35 UTC
Adding to the cc list.

Comment 2 Chris Lumens 2011-06-03 19:47:29 UTC
Please attach /tmp/anaconda.log and /tmp/syslog from after the prompting should have taken place to this bug report.  Thanks.

Comment 3 apfeiffe 2011-08-01 22:53:52 UTC
I can't seem to get a command line prompt to be able to copy the requested logs.  I have tried alt-f1 through alt-f12 and none of them give me a command line prompt.

Comment 4 Martin Sivák 2011-08-29 12:59:21 UTC
Can you use external cdrom to get further and then give us the logs in debug mode (linux dd mpath debug debug=1)? It may contain enough information about device enumeration.

Comment 5 apfeiffe 2011-08-29 15:57:11 UTC
The vendor I am performing this test for is no longer supporting Red Hat 6.1 x86.  Therefore I will not be providing any further information on this issue.  Feel free to close out this defect.

Thanks

Comment 6 apfeiffe 2011-08-29 16:04:04 UTC
My last comment (Comment 5) was intended for a different defect and should be ignored.  

I will reproduce this using the issue with debug=1 and provide the logs.

Thanks

Comment 7 apfeiffe 2011-08-30 16:04:53 UTC
Created attachment 520632 [details]
Requested logs

I have gathered the requested logs.  Here are the steps taken:

- Booted up with the following options: linux mpath dd debug debug=1
- When it asked if I wanted to load a driver disk, I inserted the driver disk into  the drive and clicked on 'yes'.  The installer did not load the driver moved to the next step of the installer without any messages
- Once the installer GUI was loaded, I was able to copy the logs off and bundle them up into the logs.zip file which I am uploading now.

Comment 10 Brian Lane 2013-05-15 21:51:58 UTC
I don't see anything obviously wrong in the logs. If using the same cd in an external drive then the problem is likely the internal drive. I've seen drives that refuse to read cds that were written on different systems.

After booting the system with the external drive can you mount the driver disk on the internal drive?