Bug 23896 - kernel panic - unable to mount root FS after install
Summary: kernel panic - unable to mount root FS after install
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: Brock Organ
URL:
Whiteboard: Florence Beta-3
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-12 16:55 UTC by Bryan Leopard
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-01-15 21:46:59 UTC
Embargoed:

Attachments (Terms of Use)

Description Bryan Leopard 2001-01-12 16:55:13 UTC 
Linux Version		: Redhat 7.1 beta 2
Server Model		: Compaq ML330 with single channel UltraWide scsi 
(adaptec) card added, 4 port nic also added

Description	: kernel panic - unable to mount root FS

Steps to reproduce the issue:
1. Perform a normal install
2. The adaptec driver is loaded and all drives seen
3. all files are loaded properly during the install - no errors on any 
other console screens
4. When you reboot you get the kernel panic.
5. The server installed fine with just the integrated scsi.
6. controller order verfied correct
Comment 1 Glen Foster 2001-01-15 21:32:56 UTC 
Re-assigning to Michael Johnson
Comment 2 Glen Foster 2001-01-15 21:46:56 UTC 
This defect is considered MUST-FIX for Florence Beta-3
Comment 3 Michael K. Johnson 2001-01-18 23:53:59 UTC 
By "adaptec driver" I assume you mean aic7xxx.  Please let us know
if you mean anything else.

We have changed the aic7xxx driver to the newer version; please
re-open this bug if this continues in any kernel 2.4.0-0.99.5 or
later.
Comment 4 Laurie Austin-Brown 2001-02-09 16:37:17 UTC 
RH beta 3 is not even detecting that the compaq 64bit (adaptec) scsi controller 
is installed, therefore it never loads the driver and cant see any hard 
drives.  Still not working with Beta 3.
Comment 5 Michael K. Johnson 2001-02-13 21:47:49 UTC 
Try with our next beta, and re-open the bug (don't just add a comment
and leave it closed) if it isn't fixed.
Note You need to log in before you can comment on or make changes to this bug.