Problema dun colega con RAID 5 por software - GALPon

10 Mar 2006

Hola, xente, vos reenvío esta mensaxe por se alguén lle pode axudar.
Un cordial saúdo,
----------  Mensaje reenviado  ----------
Subject: Re: XGN: camisetas
Date: Viernes, 10 de Marzo de 2006 13:54
From: Carlos Ces &lt;carlos(a)arume.net&gt;
To: Jose Manuel Rodriguez &lt;insjrf02(a)ucv.udc.es&gt;
Cc: Carlos Rodriguez &lt;capri99(a)gmail.com&gt;om>, daniel(a)compostelawireless.net,
denis(a)glug.es, sdocio(a)usc.es, fabian(a)aulusc.org.es, kabute(a)gulo.org,
paco(a)compostelawireless.net, carlos(a)rianxosencabos.com, brenlla(a)agnix.org,
paulobreogan(a)tadice.es, emilioj(a)gpul.org, alex(a)rianxosencabos.com
Ola!
Son Carlos, de RianxoSenCabos.
Xurdiume un problemón, algún de vós me podería axudar ?
O problema venme cun RAID5 software, que me deu un fallo nun dos disco;
substituíno, e reconstruíuse o RAID, pero agora non son capaz de
montalo, dame erro. Nese RAID hai moita información importante que non
ten backup xusto porque coincidiu coas miñas vacacións (e ninguén se
quixo encargar de facelo).
Coñecedes a alguén dalgunha das asociacións que controle de RAIDs ou
recuperación de datos ???
Por favor, é urxente.
Grazas, un millón delas...
------------------------------------------------------------------------
A continuación, as respostas dalgúns comandos:
[root@server /]# less /etc/mdadm.conf
DEVICE /dev/hd[ghi]1
ARRAY /dev/md0 devices=/dev/hde1,/dev/hdg1,/dev/hdi1
------------------------------------------------------------------------
[root@server /]# mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Fri Mar 10 12:31:03 2006
     Raid Level : raid5
     Array Size : 320159104 (305.33 GiB 327.84 GB)
    Device Size : 160079552 (152.66 GiB 163.92 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 0
    Persistence : Superblock is persistent
    Update Time : Fri Mar 10 13:36:13 2006
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0
         Layout : left-asymmetric
     Chunk Size : 64K
           UUID : b855dd45:f23b5fa3:1448cf10:03ad44dd
         Events : 0.19956142
    Number   Major   Minor   RaidDevice State
       0      56        1        0      active sync   /dev/hdi1
       1      34        1        1      active sync   /dev/hdg1
       2      33        1        2      active sync   /dev/hde1
------------------------------------------------------------------------
[root@server /]# mdadm --examine /dev/hde1
/dev/hde1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : b855dd45:f23b5fa3:1448cf10:03ad44dd
  Creation Time : Fri Mar 10 12:31:03 2006
     Raid Level : raid5
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 0
    Update Time : Fri Mar 10 13:36:13 2006
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0
       Checksum : ffc21951 - correct
         Events : 0.19956142
         Layout : left-asymmetric
     Chunk Size : 64K
      Number   Major   Minor   RaidDevice State
this     2      33        1        2      active sync   /dev/hde1
   0     0      56        1        0      active sync   /dev/hdi1
   1     1      34        1        1      active sync   /dev/hdg1
   2     2      33        1        2      active sync   /dev/hde1
------------------------------------------------------------------------
[root@server /]# mdadm --examine /dev/hdg1
/dev/hdg1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : b855dd45:f23b5fa3:1448cf10:03ad44dd
  Creation Time : Fri Mar 10 12:31:03 2006
     Raid Level : raid5
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 0
    Update Time : Fri Mar 10 13:36:13 2006
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0
       Checksum : ffc21950 - correct
         Events : 0.19956142
         Layout : left-asymmetric
     Chunk Size : 64K
      Number   Major   Minor   RaidDevice State
this     1      34        1        1      active sync   /dev/hdg1
   0     0      56        1        0      active sync   /dev/hdi1
   1     1      34        1        1      active sync   /dev/hdg1
   2     2      33        1        2      active sync   /dev/hde1
------------------------------------------------------------------------
[root@server /]# mdadm --examine /dev/hdi1
/dev/hdi1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : b855dd45:f23b5fa3:1448cf10:03ad44dd
  Creation Time : Fri Mar 10 12:31:03 2006
     Raid Level : raid5
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 0
    Update Time : Fri Mar 10 13:36:13 2006
          State : clean
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0
       Checksum : ffc21964 - correct
         Events : 0.19956142
         Layout : left-asymmetric
     Chunk Size : 64K
      Number   Major   Minor   RaidDevice State
this     0      56        1        0      active sync   /dev/hdi1
   0     0      56        1        0      active sync   /dev/hdi1
   1     1      34        1        1      active sync   /dev/hdg1
   2     2      33        1        2      active sync   /dev/hde1
------------------------------------------------------------------------
[root@server /]# cat /proc/mdstat
Personalities : [raid5]
md0 : active raid5 hde1[2] hdg1[1] hdi1[0]
      320159104 blocks level 5, 64k chunk, algorithm 0 [3/3] [UUU]
unused devices: <none>
------------------------------------------------------------------------
Ata aquí, todo perfecto, pero:
[root@server /]# mount /dev/md0
mount: tipo de sistema de ficheros incorrecto, opción incorrecta,
superbloque incorrecto en /dev/md0,
       o número de sistemas de ficheros montados excesivo
------------------------------------------------------------------------
[root@server /]# fsck -nv /dev/md0
fsck 1.34 (25-Jul-2003)
e2fsck 1.34 (25-Jul-2003)
fsck.ext3: Filesystem revision too high while trying to open /dev/md0
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
------------------------------------------------------------------------
[root@server /]# e2fsck -nv /dev/md0
e2fsck 1.34 (25-Jul-2003)
e2fsck: Filesystem revision too high while trying to open /dev/md0
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
Vamos, que parece que o sistema de arquivos está corrompido. Algunha
idea de como poder comprobar se queda algunha información recuperable?
-------------------------------------------------------
--
-----------------------------------------
Carlos Rodríguez &lt;capri99(a)gmail.com&gt;
GALPon.org - "Abrindo as portas do Sofware Libre"