Estou tentando configurar uma invasão de 4 TB usando o fakeraid (gerenciador de armazenamento da matriz de intel) como armazenamento secundário.
Eu sou capaz de montar o ataque manualmente usando o mdadm com os seguintes comandos:
sudo mdadm --assemble --scan
Eu então executo o seguinte para atualizar a imagem do initramfs:
sudo update-initramfs -u -k all
Após a reinicialização, a invasão desapareceu.
Eu então tentei montar o ataque manualmente com os seguintes comandos:
sudo mdadm -C /dev/md/imsm /dev/sd[b-c] -n 2 -e imsm
sudo mdadm -C /dev/md/vol0 /dev/md/imsm -n 2 -l 1
sudo /usr/share/mdadm/mkconf >> /etc/mdadm/mdadm.conf
sudo update-initramfs -u -k all
O ataque estava presente e eu consegui acessar o sistema de arquivos, mas após a reinicialização, eu preciso remontar o ataque.
Seguido é o /etc/mdadm/mdadm.conf:
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY metadata=imsm UUID=771c1d7d:f06bccc3:9f0e4f61:1ecffe38
ARRAY /dev/md/vol0 container=771c1d7d:f06bccc3:9f0e4f61:1ecffe38 member=0 UUID=6b4bd4ee:81bdc61a:30663fed:35b62326
sudo mdadm --example a saída para ambos os discos sdb e sdc:
sudo mdadm --examine /dev/sdb
/dev/sdb:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.3.00
Orig Family : aeceb881
Family : aeceb881
Generation : 00000003
Attributes : All supported
UUID : 7163688a:ffbbddc9:a1ef9d17:c8c62c84
Checksum : 97950a1f correct
MPB Sectors : 1
Disks : 2
RAID Devices : 1
Disk00 Serial : S300ZMX0
State : active
Id : 00000002
Usable Size : 7814030862 (3726.02 GiB 4000.78 GB)
[Volume1]:
UUID : 560af17d:e7fbce35:2790deb9:210a2c3b
RAID Level : 1
Members : 2
Slots : [UU]
Failed disk : none
This Slot : 0
Array Size : 7813988352 (3726.00 GiB 4000.76 GB)
Per Dev Size : 7813988616 (3726.00 GiB 4000.76 GB)
Sector Offset : 0
Num Stripes : 30523392
Chunk Size : 64 KiB
Reserved : 0
Migrate State : idle
Map State : uninitialized
Dirty State : clean
Disk01 Serial : S300ZTDP
State : active
Id : 00000003
Usable Size : 7814030862 (3726.02 GiB 4000.78 GB)
sudo mdadm --examine /dev/sdc
/dev/sdc:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.3.00
Orig Family : aeceb881
Family : aeceb881
Generation : 00000003
Attributes : All supported
UUID : 7163688a:ffbbddc9:a1ef9d17:c8c62c84
Checksum : 97950a1f correct
MPB Sectors : 1
Disks : 2
RAID Devices : 1
Disk01 Serial : S300ZTDP
State : active
Id : 00000003
Usable Size : 7814030862 (3726.02 GiB 4000.78 GB)
[Volume1]:
UUID : 560af17d:e7fbce35:2790deb9:210a2c3b
RAID Level : 1
Members : 2
Slots : [UU]
Failed disk : none
This Slot : 1
Array Size : 7813988352 (3726.00 GiB 4000.76 GB)
Per Dev Size : 7813988616 (3726.00 GiB 4000.76 GB)
Sector Offset : 0
Num Stripes : 30523392
Chunk Size : 64 KiB
Reserved : 0
Migrate State : idle
Map State : uninitialized
Dirty State : clean
Disk00 Serial : S300ZMX0
State : active
Id : 00000002
Usable Size : 7814030862 (3726.02 GiB 4000.78 GB)
saída do syslog do mdadm após a reinicialização:
mdadm[12155]: DeviceDisappeared event detected on md device /dev/md/Volume1