linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 2 partition kicked from 6 raid5
@ 2005-08-30 18:10 Deak Krisztian
  2005-08-30 19:57 ` Deak Krisztian
  2005-08-31 19:32 ` Michael Tokarev
  0 siblings, 2 replies; 3+ messages in thread
From: Deak Krisztian @ 2005-08-30 18:10 UTC (permalink / raw)
  To: linux-raid

Hi,

i have a big problem. A had a sw raid5 array with 6 partition. The array
has been damaged because problems of power connectors. 2 partitions/disks don't work,
because during the time the SATA power connections didn't work. 
Some write/read operations where running. Now when i want to
run the array loading the kernel, i get the next message:

raid5: device sdl1 operational as raid disk 0
raid5: device sdj1 operational as raid disk 5
raid5: device sdh1 operational as raid disk 3
raid5: device sdg1 operational as raid disk 2
raid5: not enough operational devices for md0 (2/6 failed)
RAID5 conf printout:
 --- rd:6 wd:4 fd:2
 disk 0, o:1, dev:sdl1
 disk 2, o:1, dev:sdg1
 disk 3, o:1, dev:sdh1
 disk 5, o:1, dev:sdj1
raid5: failed to run raid set md0

I think, that the dammaged partitions have to be used anyway, to get the
datas back.

I attached the result of "mdadm --examine".
Could somebody help me?

Chris     

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2 partition kicked from 6 raid5
  2005-08-30 18:10 2 partition kicked from 6 raid5 Deak Krisztian
@ 2005-08-30 19:57 ` Deak Krisztian
  2005-08-31 19:32 ` Michael Tokarev
  1 sibling, 0 replies; 3+ messages in thread
From: Deak Krisztian @ 2005-08-30 19:57 UTC (permalink / raw)
  To: linux-raid

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

Sorry, the attachement was missing.


On Tue, Aug 30, 2005 at 08:10:15PM +0200, dechris wrote:
> Hi,
> 
> i have a big problem. A had a sw raid5 array with 6 partition. The array
> has been damaged because problems of power connectors. 2 partitions/disks don't work,
> because during the time the SATA power connections didn't work. 
> Some write/read operations where running. Now when i want to
> run the array loading the kernel, i get the next message:
> 
> raid5: device sdl1 operational as raid disk 0
> raid5: device sdj1 operational as raid disk 5
> raid5: device sdh1 operational as raid disk 3
> raid5: device sdg1 operational as raid disk 2
> raid5: not enough operational devices for md0 (2/6 failed)
> RAID5 conf printout:
>  --- rd:6 wd:4 fd:2
>  disk 0, o:1, dev:sdl1
>  disk 2, o:1, dev:sdg1
>  disk 3, o:1, dev:sdh1
>  disk 5, o:1, dev:sdj1
> raid5: failed to run raid set md0
> 
> I think, that the dammaged partitions have to be used anyway, to get the
> datas back.
> 
> I attached the result of "mdadm --examine".
> Could somebody help me?
> 
> Chris     

[-- Attachment #2: raid --]
[-- Type: text/plain, Size: 6074 bytes --]

/dev/sdg1:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : 19745837:e74d1c46:842c4d41:b427d24d
  Creation Time : Fri Jul 22 01:45:23 2005
     Raid Level : raid5
   Raid Devices : 6
  Total Devices : 5
Preferred Minor : 0

    Update Time : Mon Aug 29 11:19:59 2005
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 3
  Spare Devices : 0
       Checksum : 7196c5c4 - correct
         Events : 0.559485

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     2       8       97        2      active sync   /dev/sdg1

   0     0       8      161        0      active sync   /dev/sdk1
   1     1       0        0        1      faulty removed
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8      113        3      active sync   /dev/sdh1
   4     4       0        0        4      faulty removed
   5     5       8      145        5      active sync   /dev/sdj1
/dev/sdh1:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : 19745837:e74d1c46:842c4d41:b427d24d
  Creation Time : Fri Jul 22 01:45:23 2005
     Raid Level : raid5
   Raid Devices : 6
  Total Devices : 5
Preferred Minor : 0

    Update Time : Mon Aug 29 11:19:59 2005
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 3
  Spare Devices : 0
       Checksum : 7196c5d6 - correct
         Events : 0.559485

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     3       8      113        3      active sync   /dev/sdh1

   0     0       8      161        0      active sync   /dev/sdk1
   1     1       0        0        1      faulty removed
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8      113        3      active sync   /dev/sdh1
   4     4       0        0        4      faulty removed
   5     5       8      145        5      active sync   /dev/sdj1
/dev/sdi1:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : 19745837:e74d1c46:842c4d41:b427d24d
  Creation Time : Fri Jul 22 01:45:23 2005
     Raid Level : raid5
   Raid Devices : 6
  Total Devices : 5
Preferred Minor : 0

    Update Time : Mon Aug 29 10:14:59 2005
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 71969cd2 - correct
         Events : 0.556184

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     4       8      129        4      active sync   /dev/sdi1

   0     0       8      161        0      active sync   /dev/sdk1
   1     1       0        0        1      faulty removed
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8      113        3      active sync   /dev/sdh1
   4     4       8      129        4      active sync   /dev/sdi1
   5     5       8      145        5      active sync   /dev/sdj1
/dev/sdj1:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : 19745837:e74d1c46:842c4d41:b427d24d
  Creation Time : Fri Jul 22 01:45:23 2005
     Raid Level : raid5
   Raid Devices : 6
  Total Devices : 5
Preferred Minor : 0

    Update Time : Mon Aug 29 11:19:59 2005
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 3
  Spare Devices : 0
       Checksum : 7196c5fa - correct
         Events : 0.559485

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     5       8      145        5      active sync   /dev/sdj1

   0     0       8      161        0      active sync   /dev/sdk1
   1     1       0        0        1      faulty removed
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8      113        3      active sync   /dev/sdh1
   4     4       0        0        4      faulty removed
   5     5       8      145        5      active sync   /dev/sdj1
/dev/sdk1:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : 19745837:e74d1c46:842c4d41:b427d24d
  Creation Time : Fri Jul 22 01:45:23 2005
     Raid Level : raid5
   Raid Devices : 6
  Total Devices : 6
Preferred Minor : 0

    Update Time : Sun Jul 31 17:40:32 2005
          State : clean
 Active Devices : 6
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 71604ecd - correct
         Events : 0.16054

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     1       8      161        1      active sync   /dev/sdk1

   0     0       8      177        0      active sync   /dev/sdl1
   1     1       8      161        1      active sync   /dev/sdk1
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8      113        3      active sync   /dev/sdh1
   4     4       8      129        4      active sync   /dev/sdi1
   5     5       8      145        5      active sync   /dev/sdj1
/dev/sdl1:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : 19745837:e74d1c46:842c4d41:b427d24d
  Creation Time : Fri Jul 22 01:45:23 2005
     Raid Level : raid5
   Raid Devices : 6
  Total Devices : 5
Preferred Minor : 0

    Update Time : Mon Aug 29 11:19:59 2005
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 3
  Spare Devices : 0
       Checksum : 7196c600 - correct
         Events : 0.559485

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       8      161        0      active sync   /dev/sdk1

   0     0       8      161        0      active sync   /dev/sdk1
   1     1       0        0        1      faulty removed
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8      113        3      active sync   /dev/sdh1
   4     4       0        0        4      faulty removed
   5     5       8      145        5      active sync   /dev/sdj1

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2 partition kicked from 6 raid5
  2005-08-30 18:10 2 partition kicked from 6 raid5 Deak Krisztian
  2005-08-30 19:57 ` Deak Krisztian
@ 2005-08-31 19:32 ` Michael Tokarev
  1 sibling, 0 replies; 3+ messages in thread
From: Michael Tokarev @ 2005-08-31 19:32 UTC (permalink / raw)
  To: Deak Krisztian; +Cc: linux-raid

Deak Krisztian wrote:
> Hi,
> 
> i have a big problem. A had a sw raid5 array with 6 partition. The array
> has been damaged because problems of power connectors. 2 partitions/disks don't work,
> because during the time the SATA power connections didn't work. 
> Some write/read operations where running. Now when i want to
> run the array loading the kernel, i get the next message:
> 
> raid5: device sdl1 operational as raid disk 0
> raid5: device sdj1 operational as raid disk 5
> raid5: device sdh1 operational as raid disk 3
> raid5: device sdg1 operational as raid disk 2
> raid5: not enough operational devices for md0 (2/6 failed)

Are you using raid autostart (in-kernel auto-activating of raid
arrays) or bring it up using mdadm?  If the latter, try adding
--run option.  If the former, your only choice is to use some
rescue CD or something, and again, to try this same mdadm --run...

Depending on where/how you got to this state, your data may
be just fine.

/mjt

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-08-31 19:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-30 18:10 2 partition kicked from 6 raid5 Deak Krisztian
2005-08-30 19:57 ` Deak Krisztian
2005-08-31 19:32 ` Michael Tokarev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).