linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Corrupted RAID 50 (aparently?) array. Help needed.
@ 2008-02-28 15:42 mella.nicolas
  0 siblings, 0 replies; 9+ messages in thread
From: mella.nicolas @ 2008-02-28 15:42 UTC (permalink / raw)
  To: linux-raid

Hi list,

Hope someone can give me the right direction on how to resolve this.

I have 12 hard drives with RAID software. (250 GB each disk) I just know it was a 2 TB array. The old operating system which supported the array is no longer online. (just in case someone asks me to check the mdadm.conf file)

From what I can see with mdadm,is that there are 2 x RAID5 arrays of 990.72 GB each. (2 TB the whole array). So I believed that there is a RAID0 between both RAID5 arrays. Right? (RAID 50) The first RAID5 group is composed by 5 discs, all of them active. Here is the post: (all /dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4 are similar and have the same UUID)

# mdadm --examine /dev/sdb4

----------------------------
/dev/sdb4:
          Magic : a92b4efc
        Version : 00.91.00
           UUID : 48b86fc7:adbd7bbe:df7c7359:36df38af
  Creation Time : Tue Apr 24 18:14:28 2007
     Raid Level : raid5
  Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
     Array Size : 967495168 (922.68 GiB 990.72 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0

  Reshape pos'n : 0
      New Level : raid0
     New Layout : left-asymmetric
  New Chunksize : 0

    Update Time : Mon Nov 29 21:01:33 1999
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 42da3120 - correct
         Events : 0.61

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       3        4        0      active sync

   0     0       3        4        0      active sync
   1     1      22        4        1      active sync
   2     2      33        4        2      active sync
   3     3      34        4        3      active sync
   4     4      56        4        4      active sync
---------------------

But If I try to assemble this 1st RAID5 array:

# mdadm --assemble /dev/md0 /dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Failed to restore critical section for reshape, sorry.

Is not possible. I also try the build option:

# mdadm --build /dev/md0 -l5 -n5 --assume-clean /dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Raid level 5 not permitted with --build.

On the other hand there is the second RAID5 group which outputs the following:

------------------
# mdadm --examine /dev/sdg4 
/dev/sdg4:
          Magic : a92b4efc
        Version : 00.91.00
           UUID : 384bd728:158c759c:e9be7911:01187b1f
  Creation Time : Tue Apr 24 18:14:48 2007
     Raid Level : raid5
  Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
     Array Size : 967495168 (922.68 GiB 990.72 GB)
   Raid Devices : 5
  Total Devices : 6
Preferred Minor : 1

  Reshape pos'n : 0
      New Level : raid0
     New Layout : left-asymmetric
  New Chunksize : 0

    Update Time : Mon Nov 29 21:01:36 1999
          State : active
 Active Devices : 4
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 2
       Checksum : 6eb7dc84 - correct
         Events : 0.65

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     1      89        4        1      active sync

   0     0       0        0        0      faulty removed
   1     1      89        4        1      active sync
   2     2      90        4        2      active sync
   3     3      91        4        3      active sync
   4     4     120        4        4      active sync
   5     5     121        4        5      spare
   6     6      88        4        6      spare
------------------------------------

The 2nd RAID5 group was composed by 7 disks (I believed, as shown above). 1 disks is faulty and 2 disks are spare. But even though with the remaining 4 disks I could try to assemble this RAID5, but I have the same result as with the 1st RAID5. (mdadm: Failed to restore critical section for reshape, sorry.)

Do you have any idea on how to re-assemble this RAID 50 array ?

Thanks for any advice & help.

Nicolas

PS:

# mdadm -V
mdadm - v2.6 - 21 December 2006

Linux lab-suse 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux

--
This message was sent on behalf of mella.nicolas@gmail.com at openSubscriber.com
http://www.opensubscriber.com/messages/linux-raid@vger.kernel.org/topic.html

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

* Corrupted RAID 50 (aparently?) array. Help needed.
@ 2008-02-28 16:04 Nicolas Mella
  0 siblings, 0 replies; 9+ messages in thread
From: Nicolas Mella @ 2008-02-28 16:04 UTC (permalink / raw)
  To: linux-raid

Hi list,

Hope someone can give me the right direction on how to resolve this.

I have 12 hard drives with RAID software. (250 GB each disk) I just
know it was a 2 TB array. The old operating system which supported the
array is no longer online. (just in case someone asks me to check the
mdadm.conf file)

From what I can see with mdadm,is that there are 2 x RAID5 arrays of
990.72 GB each. (2 TB the whole array). So I believed that there is a
RAID0 between both RAID5 arrays. Right? (RAID50) The first RAID5 group
is composed by 5 discs, all of them active. Here is the post: (all
/dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4 are similar and have
the same UUID)

# mdadm --examine /dev/sdb4

----------------------------
/dev/sdb4:
          Magic : a92b4efc
        Version : 00.91.00
           UUID : 48b86fc7:adbd7bbe:df7c7359:36df38af
  Creation Time : Tue Apr 24 18:14:28 2007
     Raid Level : raid5
  Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
     Array Size : 967495168 (922.68 GiB 990.72 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0

  Reshape pos'n : 0
      New Level : raid0
     New Layout : left-asymmetric
  New Chunksize : 0

    Update Time : Mon Nov 29 21:01:33 1999
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 42da3120 - correct
         Events : 0.61

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       3        4        0      active sync

   0     0       3        4        0      active sync
   1     1      22        4        1      active sync
   2     2      33        4        2      active sync
   3     3      34        4        3      active sync
   4     4      56        4        4      active sync
---------------------

But If I try to assemble this 1st RAID5 array:

# mdadm --assemble /dev/md0 /dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Failed to restore critical section for reshape, sorry.

Is not possible. I also try the build option:

# mdadm --build /dev/md0 -l5 -n5 --assume-clean /dev/sdb4 /dev/sdc4
/dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Raid level 5 not permitted with --build.

On the other hand there is the second RAID5 group which outputs the following:

------------------
# mdadm --examine /dev/sdg4
/dev/sdg4:
          Magic : a92b4efc
        Version : 00.91.00
           UUID : 384bd728:158c759c:e9be7911:01187b1f
  Creation Time : Tue Apr 24 18:14:48 2007
     Raid Level : raid5
  Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
     Array Size : 967495168 (922.68 GiB 990.72 GB)
   Raid Devices : 5
  Total Devices : 6
Preferred Minor : 1

  Reshape pos'n : 0
      New Level : raid0
     New Layout : left-asymmetric
  New Chunksize : 0

    Update Time : Mon Nov 29 21:01:36 1999
          State : active
 Active Devices : 4
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 2
       Checksum : 6eb7dc84 - correct
         Events : 0.65

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     1      89        4        1      active sync

   0     0       0        0        0      faulty removed
   1     1      89        4        1      active sync
   2     2      90        4        2      active sync
   3     3      91        4        3      active sync
   4     4     120        4        4      active sync
   5     5     121        4        5      spare
   6     6      88        4        6      spare
------------------------------------
The 2nd RAID5 group was composed by 7 disks (I believed, as shown
above). 1 disks is faulty and 2 disks are spare. But even though with
the remaining 4 disks I could try to assemble the RAID5, but I have
the same result as with the 1st RAID5. (mdadm: Failed to restore
critical section for reshape, sorry.)

Do you have any idea on how to re-assemble this RAID 50 array ?

Thanks for any advice & help.

Nicolas

PS:

# mdadm -V
mdadm - v2.6 - 21 December 2006

Linux lab-suse 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007
x86_64 x86_64 x86_64 GNU/Linux

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

* Corrupted RAID 50 (aparently) array. Help needed.
@ 2008-02-28 16:15 Nicolas Mella
  0 siblings, 0 replies; 9+ messages in thread
From: Nicolas Mella @ 2008-02-28 16:15 UTC (permalink / raw)
  To: linux-raid

Hi list,

Hope someone can give me the right direction on how to resolve this.

I have 12 hard drives with RAID software. (250 GB each disk) I just
know it was a 2 TB array. The old operating system which supported the
array is no longer online. (just in case someone asks me to check the
mdadm.conf file)

From what I can see with mdadm,is that there are 2 x RAID5 arrays of
990.72 GB each. (2 TB the whole array). So I believed that there is a
RAID0 between both RAID5 arrays. Right? (RAID50) The first RAID5 group
is composed by 5 discs, all of them active. Here is the post: (all
/dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4 are similar and have
the same UUID)

# mdadm --examine /dev/sdb4

----------------------------
/dev/sdb4:
          Magic : a92b4efc
        Version : 00.91.00
           UUID : 48b86fc7:adbd7bbe:df7c7359:36df38af
  Creation Time : Tue Apr 24 18:14:28 2007
     Raid Level : raid5
  Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
     Array Size : 967495168 (922.68 GiB 990.72 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0

  Reshape pos'n : 0
      New Level : raid0
     New Layout : left-asymmetric
  New Chunksize : 0

    Update Time : Mon Nov 29 21:01:33 1999
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 42da3120 - correct
         Events : 0.61

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       3        4        0      active sync

   0     0       3        4        0      active sync
   1     1      22        4        1      active sync
   2     2      33        4        2      active sync
   3     3      34        4        3      active sync
   4     4      56        4        4      active sync
---------------------

But If I try to assemble this 1st RAID5 array:

# mdadm --assemble /dev/md0 /dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Failed to restore critical section for reshape, sorry.

Is not possible. I also try the build option:

# mdadm --build /dev/md0 -l5 -n5 --assume-clean /dev/sdb4 /dev/sdc4
/dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Raid level 5 not permitted with --build.

On the other hand there is the second RAID5 group which outputs the following:

------------------
# mdadm --examine /dev/sdg4
/dev/sdg4:
          Magic : a92b4efc
        Version : 00.91.00
           UUID : 384bd728:158c759c:e9be7911:01187b1f
  Creation Time : Tue Apr 24 18:14:48 2007
     Raid Level : raid5
  Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
     Array Size : 967495168 (922.68 GiB 990.72 GB)
   Raid Devices : 5
  Total Devices : 6
Preferred Minor : 1

  Reshape pos'n : 0
      New Level : raid0
     New Layout : left-asymmetric
  New Chunksize : 0

    Update Time : Mon Nov 29 21:01:36 1999
          State : active
 Active Devices : 4
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 2
       Checksum : 6eb7dc84 - correct
         Events : 0.65

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     1      89        4        1      active sync

   0     0       0        0        0      faulty removed
   1     1      89        4        1      active sync
   2     2      90        4        2      active sync
   3     3      91        4        3      active sync
   4     4     120        4        4      active sync
   5     5     121        4        5      spare
   6     6      88        4        6      spare
------------------------------------
The 2nd RAID5 group was composed by 7 disks (I believed, as shown
above). 1 disks is faulty and 2 disks are spare. But even though with
the remaining 4 disks I could try to assemble the RAID5, but I have
the same result as with the 1st RAID5. (mdadm: Failed to restore
critical section for reshape, sorry.)

Do you have any idea on how to re-assemble this RAID 50 array ?

Thanks for any advice & help.

Nicolas

PS:

# mdadm -V
mdadm - v2.6 - 21 December 2006

Linux lab-suse 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007
x86_64 x86_64 x86_64 GNU/Linux

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

* Corrupted RAID 50 (aparently?) array. Help needed.
@ 2008-02-28 16:22 nmella
  2008-03-01 20:31 ` Bill Davidsen
  0 siblings, 1 reply; 9+ messages in thread
From: nmella @ 2008-02-28 16:22 UTC (permalink / raw)
  To: linux-raid

Hi list,

Hope someone can give me the right direction on how to resolve this.

I have 12 hard drives with RAID software. (250 GB each disk) I just  
know it was a 2 TB array. The old operating system which supported the  
array is no longer online. (just in case someone asks me to check the  
mdadm.conf file)

 From what I can see with mdadm,is that there are 2 x RAID5 arrays of  
990.72 GB each. (2 TB the whole array). So I believed that there is a  
RAID0 between both RAID5 arrays. Right? (RAID50) The first RAID5 group  
is composed by 5 discs, all of them active. Here is the post: (all  
/dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4 are similar and have  
the same UUID)

# mdadm --examine /dev/sdb4

----------------------------
/dev/sdb4:
           Magic : a92b4efc
         Version : 00.91.00
            UUID : 48b86fc7:adbd7bbe:df7c7359:36df38af
   Creation Time : Tue Apr 24 18:14:28 2007
      Raid Level : raid5
   Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
      Array Size : 967495168 (922.68 GiB 990.72 GB)
    Raid Devices : 5
   Total Devices : 5
Preferred Minor : 0

   Reshape pos'n : 0
       New Level : raid0
      New Layout : left-asymmetric
   New Chunksize : 0

     Update Time : Mon Nov 29 21:01:33 1999
           State : clean
  Active Devices : 5
Working Devices : 5
  Failed Devices : 0
   Spare Devices : 0
        Checksum : 42da3120 - correct
          Events : 0.61

          Layout : left-symmetric
      Chunk Size : 64K

       Number   Major   Minor   RaidDevice State
this     0       3        4        0      active sync

    0     0       3        4        0      active sync
    1     1      22        4        1      active sync
    2     2      33        4        2      active sync
    3     3      34        4        3      active sync
    4     4      56        4        4      active sync
---------------------

But If I try to assemble this 1st RAID5 array:

# mdadm --assemble /dev/md0 /dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Failed to restore critical section for reshape, sorry.

Is not possible. I also try the build option:

# mdadm --build /dev/md0 -l5 -n5 --assume-clean /dev/sdb4 /dev/sdc4  
/dev/sdd4 /dev/sde4 /dev/sdf4
mdadm: Raid level 5 not permitted with --build.

On the other hand there is the second RAID5 group which outputs the following:

------------------
# mdadm --examine /dev/sdg4
/dev/sdg4:
           Magic : a92b4efc
         Version : 00.91.00
            UUID : 384bd728:158c759c:e9be7911:01187b1f
   Creation Time : Tue Apr 24 18:14:48 2007
      Raid Level : raid5
   Used Dev Size : 241873792 (230.67 GiB 247.68 GB)
      Array Size : 967495168 (922.68 GiB 990.72 GB)
    Raid Devices : 5
   Total Devices : 6
Preferred Minor : 1

   Reshape pos'n : 0
       New Level : raid0
      New Layout : left-asymmetric
   New Chunksize : 0

     Update Time : Mon Nov 29 21:01:36 1999
           State : active
  Active Devices : 4
Working Devices : 6
  Failed Devices : 0
   Spare Devices : 2
        Checksum : 6eb7dc84 - correct
          Events : 0.65

          Layout : left-symmetric
      Chunk Size : 64K

       Number   Major   Minor   RaidDevice State
this     1      89        4        1      active sync

    0     0       0        0        0      faulty removed
    1     1      89        4        1      active sync
    2     2      90        4        2      active sync
    3     3      91        4        3      active sync
    4     4     120        4        4      active sync
    5     5     121        4        5      spare
    6     6      88        4        6      spare
------------------------------------
The 2nd RAID5 group was composed by 7 disks (I believed, as shown  
above). 1 disks is faulty and 2 disks are spare. But even though with  
the remaining 4 disks I could try to assemble the RAID5, but I have  
the same result as with the 1st RAID5. (mdadm: Failed to restore  
critical section for reshape, sorry.)

Do you have any idea on how to re-assemble this RAID 50 array ?

Thanks for any advice & help.

Nicolas

PS:

# mdadm -V
mdadm - v2.6 - 21 December 2006

Linux lab-suse 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007  
x86_64 x86_64 x86_64 GNU/Linux



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

* Corrupted RAID 50 (aparently?) array. Help needed.
@ 2008-02-28 16:35 nmella
  2008-02-28 20:50 ` Janek Kozicki
  0 siblings, 1 reply; 9+ messages in thread
From: nmella @ 2008-02-28 16:35 UTC (permalink / raw)
  To: linux-raid

Hi list,

I just could not pass my email through "mayordomo" so here is my post:

http://www.mella.cl/a.txt

Nicolas


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

* Re: Corrupted RAID 50 (aparently?) array. Help needed.
  2008-02-28 16:35 nmella
@ 2008-02-28 20:50 ` Janek Kozicki
  0 siblings, 0 replies; 9+ messages in thread
From: Janek Kozicki @ 2008-02-28 20:50 UTC (permalink / raw)
  To: nmella; +Cc: linux-raid

nmella@kepler.cl said:     (by the date of Thu, 28 Feb 2008 10:35:18 -0600)

> Hi list,
> 
> I just could not pass my email through "mayordomo" so here is my post:
> 
> http://www.mella.cl/a.txt

well, I received this post, like, four times already.

-- 
Janek Kozicki                                                         |

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

* Re: Corrupted RAID 50 (aparently?) array. Help needed.
  2008-02-28 16:22 Corrupted RAID 50 (aparently?) " nmella
@ 2008-03-01 20:31 ` Bill Davidsen
  2008-03-03  0:28   ` Nicolas Mella
  0 siblings, 1 reply; 9+ messages in thread
From: Bill Davidsen @ 2008-03-01 20:31 UTC (permalink / raw)
  To: nmella; +Cc: linux-raid

nmella@kepler.cl wrote:
> Hi list,
>
> Hope someone can give me the right direction on how to resolve this.

Were you under the impression that this list is a professional service 
where people are paid to give you good response? You sent the first copy 
of your question at 10:42, got impatient and resent at 11:04, then 11:15 
and 11:22. Sorry we don't respond fast enough for you, perhaps you 
should take your business elsewhere.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



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

* Re: Corrupted RAID 50 (aparently?) array. Help needed.
  2008-03-01 20:31 ` Bill Davidsen
@ 2008-03-03  0:28   ` Nicolas Mella
  2008-03-03 17:42     ` Bill Davidsen
  0 siblings, 1 reply; 9+ messages in thread
From: Nicolas Mella @ 2008-03-03  0:28 UTC (permalink / raw)
  To: linux-raid

On Sat, Mar 1, 2008 at 5:31 PM, Bill Davidsen <davidsen@tmr.com> wrote:
> nmella@kepler.cl wrote:
>  > Hi list,
>  >
>  > Hope someone can give me the right direction on how to resolve this.
>
>  Were you under the impression that this list is a professional service
>  where people are paid to give you good response? You sent the first copy
>  of your question at 10:42, got impatient and resent at 11:04, then 11:15
>  and 11:22. Sorry we don't respond fast enough for you, perhaps you
>  should take your business elsewhere.
>
>  --
>  Bill Davidsen <davidsen@tmr.com>
>   "Woe unto the statesman who makes war without a reason that will still
>   be valid when the war is over..." Otto von Bismark


Sorry list. I know my mistake  and I am totally embarrassed.....

I just read everywhere that majordomo filter almost everything....so I
thought my emails where been filtered.... (list emails are dispatch
with a very long delay).

Sorry.

For sure I don't think this is a professional service. I just wanted
help on my problem which this list seem to be the right solution.

Well, anyway I could re-assemble the RAID myself.

If is it useful for someone here goes the solution:

Using Winhex software, I assemble  both RAID5 groups considering the
sequence that was detail by the "mdadm --examine option". (RAID5 type
AMI backward dynamic)

Having both 1,0 TB disks the Testdisk program said they had LVM partion.

So I activated them using "vgscan" and "vgchange -a y" and then I just
mount the partion. ufffff

Sorry for all the trouble.

Have a nice day.

Nicolas

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

* Re: Corrupted RAID 50 (aparently?) array. Help needed.
  2008-03-03  0:28   ` Nicolas Mella
@ 2008-03-03 17:42     ` Bill Davidsen
  0 siblings, 0 replies; 9+ messages in thread
From: Bill Davidsen @ 2008-03-03 17:42 UTC (permalink / raw)
  To: Nicolas Mella; +Cc: linux-raid

Nicolas Mella wrote:
> On Sat, Mar 1, 2008 at 5:31 PM, Bill Davidsen <davidsen@tmr.com> wrote:
>   
>> nmella@kepler.cl wrote:
>>  > Hi list,
>>  >
>>  > Hope someone can give me the right direction on how to resolve this.
>>
>>  Were you under the impression that this list is a professional service
>>  where people are paid to give you good response? You sent the first copy
>>  of your question at 10:42, got impatient and resent at 11:04, then 11:15
>>  and 11:22. Sorry we don't respond fast enough for you, perhaps you
>>  should take your business elsewhere.
>>
>>  --
>>  Bill Davidsen <davidsen@tmr.com>
>>   "Woe unto the statesman who makes war without a reason that will still
>>   be valid when the war is over..." Otto von Bismark
>>     
>
>
> Sorry list. I know my mistake  and I am totally embarrassed.....
>
> I just read everywhere that majordomo filter almost everything....so I
> thought my emails where been filtered.... (list emails are dispatch
> with a very long delay).
>
> Sorry.
>
> For sure I don't think this is a professional service. I just wanted
> help on my problem which this list seem to be the right solution.
>
> Well, anyway I could re-assemble the RAID myself.
>
>   
Did you try just specifying "partitions" to mdadm and letting the 
software determine the members and assembly order? While this is not as 
exciting a challenge as assembling with data from examined partitions, 
it is a lot more convenient. ;-)

> If is it useful for someone here goes the solution:
>
> Using Winhex software, I assemble  both RAID5 groups considering the
> sequence that was detail by the "mdadm --examine option". (RAID5 type
> AMI backward dynamic)
>
> Having both 1,0 TB disks the Testdisk program said they had LVM partion.
>
> So I activated them using "vgscan" and "vgchange -a y" and then I just
> mount the partion. ufffff
>
>   
Good job, glad you got it going again.

> Sorry for all the trouble.
>
> Have a nice day.
>
> Nicolas
> --
> 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
>
>   


-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



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

end of thread, other threads:[~2008-03-03 17:42 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-28 15:42 Corrupted RAID 50 (aparently?) array. Help needed mella.nicolas
  -- strict thread matches above, loose matches on Subject: below --
2008-02-28 16:04 Nicolas Mella
2008-02-28 16:15 Corrupted RAID 50 (aparently) " Nicolas Mella
2008-02-28 16:22 Corrupted RAID 50 (aparently?) " nmella
2008-03-01 20:31 ` Bill Davidsen
2008-03-03  0:28   ` Nicolas Mella
2008-03-03 17:42     ` Bill Davidsen
2008-02-28 16:35 nmella
2008-02-28 20:50 ` Janek Kozicki

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).