Bug 65192

Summary: anaconda traceback on upgrade of software raid based system
Product: [Retired] Red Hat Linux Reporter: Need Real Name <pbrett>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-19 22:02:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
Anaconda traceback file
/etc/fstab none

Description Need Real Name 2002-05-19 20:52:10 UTC
Description of problem:
Anaconda traceback on upgrade of software raid based system.  

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

How reproducible:

Steps to Reproduce:
1. Follow standard CD rom based upgrade of system

Actual Results:  anaconda traceback

Expected Results:  Should correctly recongnise RAID devices

Additional info:

Comment 1 Need Real Name 2002-05-19 20:54:34 UTC
Created attachment 57924 [details]
Anaconda traceback file

Comment 2 Need Real Name 2002-05-19 20:56:27 UTC
Created attachment 57925 [details]

Comment 3 Need Real Name 2002-05-19 20:59:27 UTC
Created attachment 57926 [details]

Comment 4 Need Real Name 2002-05-19 21:03:49 UTC
Bug was first reported as part of service request #205401

Bug was raised in Bugzilla as #64624 against 7.2, and closed as resolved in 7.3.

Comment 5 Need Real Name 2002-05-19 22:02:52 UTC
Looking at the traceback, I suspect that this may be because my RAID devices are
numbered md1 to md5.  I.E I do not have an md0.

Any thoughts on this?

Comment 6 Jeremy Katz 2002-05-20 15:34:55 UTC
Can you try using the update disk available at
http://people.redhat.com/~katzj/73raid.img?  If you put that on a separate
floppy and boot with 'linux updates', inserting the disk when prompted, it
should fix the problem.

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