Re: sw_raid5-failed_disc(s)-2

[Ronny Plattner <ronny_p@gmx.net>]

Hi !

Guy schrieb:
> It seems like a trick question! :)
> You don't use "missing" on assemble, it is a keyword for the create command.

Oh!

> For assemble. just don't list that device.
> mdadm --assemble --run --force /dev/md2 /dev/hdi1 /dev/hdk1 /dev/hdo1
> 
> mdadm will know which disk is which.

OKay, thank you

-snip-
server:~# cat /proc/mdstat
Personalities : [raid1] [raid5]
md1 : active raid1 hdg2[1] hde2[0]
      75709248 blocks [2/2] [UU]

md0 : active raid1 hdg1[1] hde1[0]
      2441280 blocks [2/2] [UU]

unused devices: <none>
server:~# mdadm  --assemble --run --force /dev/md2 /dev/hdi1 /dev/hdk1
/dev/hdo1
mdadm: failed to RUN_ARRAY /dev/md2: Invalid argument
server:~# cat /proc/mdstat
Personalities : [raid1] [raid5]
md1 : active raid1 hdg2[1] hde2[0]
      75709248 blocks [2/2] [UU]

md2 : inactive hdk1[1] hdi1[4] hdo1[3]
      735334848 blocks
md0 : active raid1 hdg1[1] hde1[0]
      2441280 blocks [2/2] [UU]

unused devices: <none>
-snap-


and


-snip-
server:~# mdadm  --detail /dev/md2
/dev/md2:
        Version : 00.90.01
  Creation Time : Mon Jun 14 18:43:20 2004
     Raid Level : raid5
    Device Size : 245111616 (233.76 GiB 250.99 GB)
   Raid Devices : 4
  Total Devices : 3
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Sun Mar  6 16:40:29 2005
          State : active, degraded
 Active Devices : 2
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 64K

           UUID : 72c49e3a:de37c4f8:00a6d8a2:e8fddb2c
         Events : 0.60470022

    Number   Major   Minor   RaidDevice State
       0       0        0        -      removed
       1      57        1        1      active sync   /dev/hdk1
       2       0        0        -      removed
       3      89        1        3      active sync   /dev/hdo1

       4      56        1        -      spare   /dev/hdi1
server:~#
-snap-


Why is hdi1 (the drive which was built out and after troubles with hdm
again built back in the server) a spare device?
Why isn´t it marked as active device?
Is it hopeless to get the raid working?

Not much information in the logfile (/var/log/messages)...


-snip-
Mar 12 19:33:57 server kernel: md: md2 stopped.
Mar 12 19:33:57 server kernel: md: bind<hdo1>
Mar 12 19:33:57 server kernel: md: bind<hdi1>
Mar 12 19:33:57 server kernel: md: bind<hdk1>
Mar 12 19:33:57 server kernel: raid5: device hdk1 operational as raid disk 1
Mar 12 19:33:57 server kernel: raid5: device hdo1 operational as raid disk 3
Mar 12 19:33:57 server kernel: RAID5 conf printout:
Mar 12 19:33:57 server kernel:  --- rd:4 wd:2 fd:2
Mar 12 19:33:57 server kernel:  disk 1, o:1, dev:hdk1
Mar 12 19:33:57 server kernel:  disk 3, o:1, dev:hdo1
-snap-


So, looks bad.


-snip-
server:~# mdadm --detail --scan
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=83effa33:2b40093b:84150bda:54575d43
   devices=/dev/hde2,/dev/hdg2
ARRAY /dev/md2 level=raid5 num-devices=4 spares=1
UUID=72c49e3a:de37c4f8:00a6d8a2:e8fddb2c
   devices=/dev/hdk1,/dev/hdo1,/dev/hdi1
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=7131d3b3:6e026b72:52e66138:1401e760
   devices=/dev/hde1,/dev/hdg1
-snap-


Is there a way to get the raid working?

Regards
Ronny

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html