Title: RE: help, help, help

**** Here is the main clue as to what is wrong ******

>#cat /proc/mdstat
>Personalities : [1 linear] [2 raid0] [3 raid1]
>read_ahead not set
>md0 : inactive
>md1 : inactive
>md2 : inactive
>md3 : inactive

Any time you see a /proc/mdstat listing md0 through md3 with all of them inactive,
it means that the kernel has NOT been patched with the latest raid code.  Even the
latest 2.2.XX kernels need to be patched up to the raid 0.90 version.

The patch for the 2.2.14 kernel can be found at http://www.redhat.com/~mingo
Patches for earlier 2.2 kernels can be found at ftp://ftp.us.kernel.org in the deamons/raid/alpha directory, I forget the full path.

Clay


-----Original Message-----
From: "Hübner, Dietmar, VMD-TWR-IEA" [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 11, 2000 7:57 AM
To: '[EMAIL PROTECTED]'
Subject: help, help, help


Hi ,

I have linux 2.2.13 (SuSE) and a problem with a raid1.
I included 2 new SCSI-HD, in my system, created 3 Partitions sda1..3,
sdb1..3 (3x3GB),  and i will use only a part of this, so I created
/etc/raidtab
----------------

raiddev /dev/md0
        raid-level      1
        nr-raid-disks   2
        nr-spare-disks  0
        persistent-superblock     1
        chunk-size                4
        device          /dev/sda1
        raid-disk       0
        device          /dev/sdb1
        raid-disk       1

# mkraid  /dev/md0
----------------------------
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sda1, 3084448kB, raid superblock at 3084352kB
/dev/sda1 appears to contain an ext2 filesystem -- use -f to override
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.


so what i do is
---------------------


# mkraid --really-force /dev/md0
----------------------------------------------
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sda1, 3084448kB, raid superblock at 3084352kB
disk 1: /dev/sdb1, 3084448kB, raid superblock at 3084352kB
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.

I can't find any wrong messages in /var/log/messages
----------------------------------------------------------------------------
-

Feb 11 16:17:19 nameserv -- MARK --
Feb 11 16:19:22 nameserv kernel: SCSI device sda: hdwr sector= 512 bytes.
Sectors= 17916240 [8748 MB] [8.7 GB]
Feb 11 16:19:22 nameserv kernel:  sda: sda1 sda2 sda3
Feb 11 16:19:24 nameserv kernel: SCSI device sda: hdwr sector= 512 bytes.
Sectors= 17916240 [8748 MB] [8.7 GB]
Feb 11 16:19:24 nameserv kernel:  sda: sda1 sda2 sda3
Feb 11 16:20:58 nameserv kernel: SCSI device sdb: hdwr sector= 512 bytes.
Sectors= 17916240 [8748 MB] [8.7 GB]
Feb 11 16:20:58 nameserv kernel:  sdb: sdb1 sdb2 sdb3
Feb 11 16:21:00 nameserv kernel: SCSI device sdb: hdwr sector= 512 bytes.
Sectors= 17916240 [8748 MB] [8.7 GB]
Feb 11 16:21:00 nameserv kernel:  sdb: sdb1 sdb2 sdb3

#cat /proc/mdstat
Personalities : [1 linear] [2 raid0] [3 raid1]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive

Do you have a idea what is wrong ???

dietmar



----------------------------------------------------------------------
This Mail has been checked for Viruses
Attention: Encrypted Mails can NOT be checked !

* * *

Diese Mail wurde auf Viren ueberprueft
Hinweis: Verschluesselte Mails koennen NICHT geprueft werden !
----------------------------------------------------------------------

Reply via email to