Nas últimas três noites, um dos meus controladores USB ficou offline no meio da noite, deixando 4 dos meus 8 discos offline. Nas duas primeiras vezes, consegui fazê-lo funcionar novamente com o mdadm -A /dev/md0 -f /dev/sd[hgeflkji]. Tentei isso esta manhã e não está funcionando. Alguma ideia?
[root@dl380g5 ~]# mdadm --examine /dev/sd[efghijkl] |egrep 'Event'
Events : 37261
Events : 37261
Events : 37261
Events : 37261
Events : 37249
Events : 37248
Events : 37249
Events : 37248
[root@dl380g5 ~]# mdadm -A /dev/md0 --force -v /dev/sd[hgeflkji]
mdadm: looking for devices for /dev/md0
mdadm: /dev/sde is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdf is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sdg is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdh is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdi is identified as a member of /dev/md0, slot 7.
mdadm: /dev/sdj is identified as a member of /dev/md0, slot 6.
mdadm: /dev/sdk is identified as a member of /dev/md0, slot 5.
mdadm: /dev/sdl is identified as a member of /dev/md0, slot 4.
mdadm: added /dev/sdg to /dev/md0 as 1
mdadm: added /dev/sde to /dev/md0 as 2
mdadm: added /dev/sdf to /dev/md0 as 3
mdadm: added /dev/sdl to /dev/md0 as 4 (possibly out of date)
mdadm: added /dev/sdk to /dev/md0 as 5 (possibly out of date)
mdadm: added /dev/sdj to /dev/md0 as 6 (possibly out of date)
mdadm: added /dev/sdi to /dev/md0 as 7 (possibly out of date)
mdadm: added /dev/sdh to /dev/md0 as 0
mdadm: /dev/md0 assembled from 4 drives - not enough to start the array.
[root@dl380g5 ~]# mdadm --detail /dev/md0
mdadm: cannot open /dev/md0: No such file or directory
[root@dl380g5 ~]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
unused devices: <none>
[root@dl380g5 ~]# cat /etc/mdadm.conf
ARRAY /dev/md0 metadata=1.2 name=fs2.internal.xxxxxxxxx.xxx:0 UUID=a3521a6d:596057f0:87205aac:3aab2ef2
[root@dl380g5 ~]#
Responder1
Na minha experiência, o mdadm forçará a atualização da contagem de eventos. Vejo casos assim com frequência. Certifique-se de estar usando a versão mais recente do mdadm.
Se tudo mais falhar, você pode executar um mdadm --create mas deve ter 100% de certeza de usar os parâmetros corretos do mdadm ou estará cavando um buraco mais fundo.