Bug 10097 - Disk devices are not assigned in proper order
Summary: Disk devices are not assigned in proper order
Keywords:
Status: CLOSED DUPLICATE of bug 6772
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: raidtools
Version: 6.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-03-09 19:28 UTC by yencheng kang
Modified: 2018-07-11 15:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-03-09 19:50:17 UTC
Embargoed:


Attachments (Terms of Use)

Description yencheng kang 2000-03-09 19:28:06 UTC
I am not sure this is raidtools problem. I believe this is the problem in
the installation program of the Red Hat 6.1.

I am using Dell PowerEdge 2300/400 with 2 internal drives (8 GB) and 1
external raid tower that has 4 disk drives and configured as RAID5 (17 GB).
When I installed the Red Hat 6.1, it shows the devices as follows:

    sda        17GB (external drives)
    sdb         8GB (internal drive)
    sdc         8GB (internal drive)

The actual order of devices after the boot are:

    sda         8GB (internal drive)
    sdb         8GB (internal drive)
    sdc        17GB (external drives)

The partion devices are also re-arranged in the decending order of the
partition size when a new partition is created during the installation.


This cause the problem when I create raid devices (software raid - RAID1)
from the internal drives.

Comment 1 Bill Nottingham 2000-03-09 19:50:59 UTC
*** This bug has been marked as a duplicate of 6772 ***

Comment 2 openshift-github-bot 2018-07-11 15:16:47 UTC
Commit pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/aa49331537238eebe091ea328de5f4cb2c4df000
Merge pull request #10597 from tmorriso-rh/Issue10097

Change title to encrypting traffic


Note You need to log in before you can comment on or make changes to this bug.