Linux raid de software (mdadm) array RAID5 de 3 discos, 2 dispositivos “desatualizados”

1

Estou tendo problemas ao tentar recuperar uma matriz de disco RAID5 3, onde parece que dois discos estão desatualizados.

root@mindstorm4: mdadm -E /dev/sd[bcd]
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 6a243319:84b8f9a9:355f027e:58b8a6fb
           Name : md_stripey
  Creation Time : Sun Feb 23 22:08:02 2014
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 3907028992 (1863.02 GiB 2000.40 GB)
     Array Size : 3907028992 (3726.03 GiB 4000.80 GB)
    Data Offset : 16 sectors
   Super Offset : 8 sectors
   Unused Space : before=0 sectors, after=160 sectors
          State : clean
    Device UUID : 7299f928:b1105a5c:f89d8600:0f944324

    Update Time : Sun Jun  5 09:43:12 2016
       Checksum : efcdeccc - correct
         Events : 4375

         Layout : parity-last
     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 6a243319:84b8f9a9:355f027e:58b8a6fb
           Name : md_stripey
  Creation Time : Sun Feb 23 22:08:02 2014
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 3907028992 (1863.02 GiB 2000.40 GB)
     Array Size : 3907028992 (3726.03 GiB 4000.80 GB)
    Data Offset : 16 sectors
   Super Offset : 8 sectors
   Unused Space : before=0 sectors, after=160 sectors
          State : clean
    Device UUID : f403f8da:b4eec381:fbcf9628:b562ad94

    Update Time : Wed Feb  1 00:15:25 2017
       Checksum : 60f42d25 - correct
         Events : 574913

         Layout : parity-last
     Chunk Size : 512K

   Device Role : Active device 2
   Array State : ..A ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdd:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 6a243319:84b8f9a9:355f027e:58b8a6fb
           Name : md_stripey
  Creation Time : Sun Feb 23 22:08:02 2014
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 3907028992 (1863.02 GiB 2000.40 GB)
     Array Size : 3907028992 (3726.03 GiB 4000.80 GB)
    Data Offset : 16 sectors
   Super Offset : 8 sectors
   Unused Space : before=0 sectors, after=160 sectors
          State : active
    Device UUID : a69bf0c5:49d75e40:2ad555a4:fe6d68c3

    Update Time : Wed Feb  1 00:13:22 2017
       Checksum : b504bd62 - correct
         Events : 574909

         Layout : parity-last
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : .AA ('A' == active, '.' == missing, 'R' == replacing)

Quando tento ativar;

root@mindstorm4: mdadm -A --scan -v
mdadm: looking for devices for further assembly
<snip>
mdadm: no RAID superblock on /dev/sda
mdadm: /dev/sdd is identified as a member of /dev/md/md_stripey_0, slot 1.
mdadm: /dev/sdc is identified as a member of /dev/md/md_stripey_0, slot 2.
mdadm: /dev/sdb is identified as a member of /dev/md/md_stripey_0, slot 0.
mdadm: added /dev/sdb to /dev/md/md_stripey_0 as 0 (possibly out of date)
mdadm: added /dev/sdd to /dev/md/md_stripey_0 as 1 (possibly out of date)
mdadm: added /dev/sdc to /dev/md/md_stripey_0 as 2
mdadm: /dev/md/md_stripey_0 assembled from 1 drive - not enough to start the array.
mdadm: looking for devices for further assembly
mdadm: No arrays found in config file or automatically

Mas, o arquivo de dispositivo / dev / md / md_stripey_0 não existe, portanto não posso verificar o status da matriz usando --detail.

Além disso, estou preocupado em executar mdadm -A --force ... porque a página man diz que isso é potencialmente destrutivo.

    
por xconspirisist 01.02.2017 / 14:07

0 respostas