☰

La matriz RAID5 suave de Linux con eventos no coincidentes no se ensambla

tag-icon • tag-icon linux raid mdadm
La matriz RAID5 suave de Linux con eventos no coincidentes no se ensambla

Las últimas tres noches, uno de mis controladores USB se desconectó en medio de la noche, dejando fuera de línea 4 de mis 8 discos. Las dos primeras veces pude hacerlo funcionar nuevamente con mdadm -A /dev/md0 -f /dev/sd[hgeflkji]. Lo intenté esta mañana y no funciona. ¿Algunas ideas?

[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 ~]#

Respuesta1

En mi experiencia, mdadm forzará la actualización del recuento de eventos. Veo casos como este a menudo. Asegúrese de estar utilizando la última versión de mdadm.

Si todo lo demás falla, puede realizar mdadm --create pero debe estar 100% seguro de utilizar los parámetros mdadm correctos o cavará un agujero más profundo.

información relacionada