RAID woes
Simon Haddon
simon at sibern.com.au
Tue Mar 11 05:18:15 EST 2003
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 10/03/03, 5:16:26 PM, rob shugg <rshugg at kinetitech.com.au> wrote
regarding RAID woes:
> I can't seem to set up a new raid1 and cant find out why.
> I have included all the relavant info, the kernel is a custom 2.4.20 with
all
> the raid stuff compiled in - no module support either. Can anyone point
me in
> the right direction.
> rob
> /etc/raidtab
> raiddev /dev/md0
> raid-level
I think you need "raid-level 1" here. It looks like it doesn't know
that it is a raid 1 disk array.
> nr-raid-disks 2
> nr-spare-disks 0
> chunk-size 4
> persistent-superblock 1
> device /dev/hde1
> raid-disk 0
> device /dev/hdg1
> raid-disk 1
> dmsg on boot:
> md: raid1 personality registered as nr 3
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> # mkraid /dev/md0
> gives:
> Mar 10 17:01:22 kpt kernel: md: bind<hde1,1>
> Mar 10 17:01:22 kpt kernel: md: bind<hdg1,2>
> Mar 10 17:01:22 kpt kernel: md: hdg1's event counter: 00000000
> Mar 10 17:01:22 kpt kernel: md: hde1's event counter: 00000000
> Mar 10 17:01:22 kpt kernel: md: personality 1 is not loaded!
> Mar 10 17:01:22 kpt kernel: md: md0 still in use.
> /proc/mdstat:
> Personalities : [raid1]
> read_ahead not set
> md0 : inactive hdg1[1] hde1[0]
> 0 blocks
> unused devices: <none>
More information about the linux
mailing list