Bug 22342
Summary: | No drives found | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <martin> |
Component: | installer | Assignee: | Matt Wilson <msw> |
Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | ||
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: | 2000-12-28 14:58:31 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: |
Description
Need Real Name
2000-12-15 12:45:27 UTC
Are there any messages on VC3 or VC4 when you see this dialog box (hit cntl-alt f3 and cntl-alt-f4)? no messages on VC3 and VC4. what i've done: boot from cd with update discette until window new install: server, ws, upgrade existing, etc. press enter -> then failure comes. before pressing "ok" looking for changes on vc3 and vc4 -> nothing. the last few lines on vc3 BEFORE pressing "update existing system": "going to insmod raidx (path is NULL)" "going to insmod fat.o (path is NULL)" "going to insmod vfat.o (path is NULL)" "going to insmod ext3.o (path is NULL)" the last few lines on vc4 BEFORE pressing "update existing system": "raidx personality registred" i have the feeling that something with the raid driver is not ok. a "cat /proc/scsi/xx" doesn't show the raid adapter a "cat /proc/modules" shows: megaraid (initializing) Assigning to a developer. Check to make sure that you have the latest MegaRAID firmware on your card. problem can be resolved by updating firmware of megaraid perc2/sc controller. i had version 3.00. DELL has 3.14 on their support site which fixes the problem. That's what I thought it was. The older firmware had a bug that caused data corruption, so we forced the driver to fail to initialize if the buggy firmware is detected. |