mdadm 2x Raid 5 unidades ausentes

Question

Espero que alguém possa me orientar aqui com um problema de reconstrução / sincronização. Eu tenho um 3 RAID 5's construído em mdadm 4 discos em cada md0 (ativo, degradado), md1 (ativo, degradado) e md2 (limpo) -no dados nele, então eu não me importo com isso.

Todas as 12 unidades estão conectadas a uma placa LSI 9750-8i. Os mergulhos foram todos anexados a este cartão como "unidades" únicas. Uma unidade falhou e foi mostrada como ausente na interface LSI 3dm2. Dentro do Mdadm, a matriz também mostra a unidade como 'removida'.

Para complicar ainda mais, o segundo array também mostra como Ativo, degradado com um mergulho 'removido'

Encerrei o sistema e substituí a unidade com falha de 3TB por outra nova. Como sei quais unidades estavam presentes antes da falha, sei quais duas unidades não estão mais separadas das matrizes. sdh = drive que saltou de um dos arrays. sd0 = a nova unidade física que foi instalada. Os Superblocks são persistentes.

Problema # 1. Posso consultar os mergulhos para seus números de série, mas não consigo descobrir de qual array o sdh foi originalmente separado, com a esperança de poder adicioná-lo de volta ao array correto.

Problema # 2. adicione sdo no array md'x 'dependendo de qual sdf pertencia.

Ocorreram alguns erros de unidade física relatados dentro de 3dm2 de LSI, mas após a varredura novamente, eles desapareceram e todas as unidades neste nível agora estão reportando "OK". No entanto, isso pode ter sido parte do problema para o sdf 'cair' do array inicialmente?

Sdo eu assumo, vou ter que usar o gpart para formatar o drive de 3TB e depois adicioná-lo ao outro array? Eu tenho backups para isso é produção NAS. Eu prefiro não cortá-lo e cometer um erro causando uma reconstrução ...

Se alguém puder fazer algumas sugestões sobre como proceder, isso seria ótimo! TIA

Do cat / proc

  [root@pithos dev]# cat /proc/mdstat   Personalities : [raid6] [raid5 [raid4]
   md0 : active raid5 sdc1[0] sdd1[4] sde1[2]
        8789025216 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [U_UU]

   md1 : active raid5 sdf1[0] sdi1[4] sdg1[1]
       8789025216 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [UU_U]

   md2 : active raid5 sdj1[0] sdm1[4] sdl1[2] sdk1[1]
       8789025216 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

 unused devices: <none>

Md0

[root@pithos dev]# mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Fri May 31 10:46:54 2013
     Raid Level : raid5
     Array Size : 8789025216 (8381.87 GiB 8999.96 GB)
  Used Dev Size : 2929675072 (2793.96 GiB 2999.99 GB)
   Raid Devices : 4
  Total Devices : 3
    Persistence : Superblock is persistent

    Update Time : Fri Jul  8 18:07:27 2016
          State : active, degraded
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : pithos.dougallmedia.com:0  (local to host pithos.dougallmedia.com)
           UUID : f1e42a86:7fc791f8:7cf63ab8:065ffa92
         Events : 3543

    Number   Major   Minor   RaidDevice State
       0       8       33        0      active sync   /dev/sdc1
       1       0        0        1      removed
       2       8       65        2      active sync   /dev/sde1
       4       8       49        3      active sync   /dev/sdd1

Md1

[root@pithos dev]# mdadm -D /dev/md1
/dev/md1:
        Version : 1.2
  Creation Time : Fri May 31 17:44:49 2013
     Raid Level : raid5
     Array Size : 8789025216 (8381.87 GiB 8999.96 GB)
  Used Dev Size : 2929675072 (2793.96 GiB 2999.99 GB)
   Raid Devices : 4
  Total Devices : 3
    Persistence : Superblock is persistent

    Update Time : Tue Jul 12 11:31:52 2016
          State : clean, degraded
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : pithos.dougallmedia.com:1  (local to host pithos.dougallmedia.com)
           UUID : 58ba8949:bed7be0b:ba4dcc3e:8e6bc5e2
         Events : 9779

    Number   Major   Minor   RaidDevice State
       0       8       81        0      active sync   /dev/sdf1
       1       8       97        1      active sync   /dev/sdg1
       2       0        0        2      removed
       4       8      129        3      active sync   /dev/sdi1


[root@pithos dev]# mdadm --assemble --scan -v
mdadm: looking for devices for /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdo
mdadm: cannot open device /dev/dm-10: Device or resource busy
mdadm: cannot open device /dev/dm-9: Device or resource busy
mdadm: cannot open device /dev/dm-8: Device or resource busy
mdadm: cannot open device /dev/dm-7: Device or resource busy
mdadm: cannot open device /dev/dm-6: Device or resource busy
mdadm: cannot open device /dev/dm-5: Device or resource busy
mdadm: cannot open device /dev/md0: Device or resource busy
mdadm: cannot open device /dev/md1: Device or resource busy
mdadm: no recogniseable superblock on /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdn
mdadm: cannot open device /dev/dm-4: Device or resource busy
mdadm: cannot open device /dev/dm-3: Device or resource busy
mdadm: cannot open device /dev/dm-2: Device or resource busy
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: cannot open device /dev/sdk1: Device or resource busy
mdadm: cannot open device /dev/sdk: Device or resource busy
mdadm: cannot open device /dev/sdm1: Device or resource busy
mdadm: cannot open device /dev/sdm: Device or resource busy
mdadm: cannot open device /dev/sdl1: Device or resource busy
mdadm: cannot open device /dev/sdl: Device or resource busy
mdadm: cannot open device /dev/sdj1: Device or resource busy
mdadm: cannot open device /dev/sdj: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sdg: Device or resource busy
mdadm: cannot open device /dev/sdi1: Device or resource busy
mdadm: cannot open device /dev/sdi: Device or resource busy
mdadm: /dev/sdh1 has wrong uuid.
mdadm: Cannot assemble mbr metadata on /dev/sdh
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: looking for devices for /dev/md1
mdadm: Cannot assemble mbr metadata on /dev/sdo
mdadm: cannot open device /dev/dm-10: Device or resource busy
mdadm: cannot open device /dev/dm-9: Device or resource busy
mdadm: cannot open device /dev/dm-8: Device or resource busy
mdadm: cannot open device /dev/dm-7: Device or resource busy
mdadm: cannot open device /dev/dm-6: Device or resource busy
mdadm: cannot open device /dev/dm-5: Device or resource busy
mdadm: cannot open device /dev/md0: Device or resource busy
mdadm: cannot open device /dev/md1: Device or resource busy
mdadm: no recogniseable superblock on /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdn
mdadm: cannot open device /dev/dm-4: Device or resource busy
mdadm: cannot open device /dev/dm-3: Device or resource busy
mdadm: cannot open device /dev/dm-2: Device or resource busy
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: cannot open device /dev/sdk1: Device or resource busy
mdadm: cannot open device /dev/sdk: Device or resource busy
mdadm: cannot open device /dev/sdm1: Device or resource busy
mdadm: cannot open device /dev/sdm: Device or resource busy
mdadm: cannot open device /dev/sdl1: Device or resource busy
mdadm: cannot open device /dev/sdl: Device or resource busy
mdadm: cannot open device /dev/sdj1: Device or resource busy
mdadm: cannot open device /dev/sdj: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sdg: Device or resource busy
mdadm: cannot open device /dev/sdi1: Device or resource busy
mdadm: cannot open device /dev/sdi: Device or resource busy
mdadm: /dev/sdh1 has wrong uuid.
mdadm: Cannot assemble mbr metadata on /dev/sdh
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sdo
mdadm: cannot open device /dev/dm-10: Device or resource busy
mdadm: cannot open device /dev/dm-9: Device or resource busy
mdadm: cannot open device /dev/dm-8: Device or resource busy
mdadm: cannot open device /dev/dm-7: Device or resource busy
mdadm: cannot open device /dev/dm-6: Device or resource busy
mdadm: cannot open device /dev/dm-5: Device or resource busy
mdadm: cannot open device /dev/md0: Device or resource busy
mdadm: cannot open device /dev/md1: Device or resource busy
mdadm: no recogniseable superblock on /dev/md2
mdadm: Cannot assemble mbr metadata on /dev/sdn
mdadm: cannot open device /dev/dm-4: Device or resource busy
mdadm: cannot open device /dev/dm-3: Device or resource busy
mdadm: cannot open device /dev/dm-2: Device or resource busy
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: cannot open device /dev/sdk1: Device or resource busy
mdadm: cannot open device /dev/sdk: Device or resource busy
mdadm: cannot open device /dev/sdm1: Device or resource busy
mdadm: cannot open device /dev/sdm: Device or resource busy
mdadm: cannot open device /dev/sdl1: Device or resource busy
mdadm: cannot open device /dev/sdl: Device or resource busy
mdadm: cannot open device /dev/sdj1: Device or resource busy
mdadm: cannot open device /dev/sdj: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sdg: Device or resource busy
mdadm: cannot open device /dev/sdi1: Device or resource busy
mdadm: cannot open device /dev/sdi: Device or resource busy
mdadm: no recogniseable superblock on /dev/sdh1
mdadm: Cannot assemble mbr metadata on /dev/sdh
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sda: Device or resource busy

    

Answer 1

Problem #1. I can query the dives for their serial numbers but I can't seem to find out which array sdh was originally apart of, with the hope I can add it back to the correct array.

Use mdadm -E /dev/sdh1 (examine). Então você pode usar mdadm --re-add ... ou --add .

Além disso, se os outros discos estiverem com boa saúde, você pode simplesmente recriar esse disco mesmo que ele já tenha dados.

Se isso não funcionar, talvez seja necessário usar mdadm --create --assume-clean ... para criar uma nova matriz sobre os dados antigos, reutilizando os dados, o que é perigoso. Certifique-se de salvar seus detalhes ( -D ) e examine a saída para todos os discos primeiro. Você precisa definir explicitamente muitas das coisas que você vê na saída do exame ou detalhe, como o layout, o nível, a ordem da unidade, o tamanho do bloco, etc. Para usar --create com segurança, teste bem com as sobreposições em vez de arriscar seu dados. Usar --assume-clean significa que você manterá seus dados antigos.

Problem #2. add sdo into the md'x' array depending on which one sdf belonged to.

Você pode fazer isso depois de usar mdadm -E para saber para qual array adicioná-lo, mesmo que você não tenha terminado com as sobreposições, e também seja apenas mdadm --add /dev/md0 /dev/sdo

E também recomendo que você execute testes longos e inteligentes em seus discos com frequência, e dessa forma você pode substituir os discos antes que eles causem problemas de invasão. (Também discos Seagate Barracuda 3TB são muito não confiáveis ... meu palpite é que é o que você tem, e não é culpa do mdadm; adicionar testes inteligentes também ajudará com esses tipos de problemas.)

E eu recomendo que você venha ao irc.freenode.net # linux-raid para obter a melhor ajuda em tempo real com problemas como esses.