Como afirmado no título, não consigo montar meu array RAID. Aqui está o meu 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 /dev/md/127 metadata=1.1 UUID=7228e3bb:e2927657:05bd319c:a646a849 name=dc.sec.net:0
# This file was auto-generated on Tue, 27 Sep 2016 20:52:52 +0530
# by mkconf $Id$
Aqui está o resultado do meu comando mount sudo mount / dev / md127 / media / md
mount: wrong fs type, bad option, bad superblock on /dev/md127,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
Ao inspecionar o syslog, noto
Oct 17 12:05:26 irj-SandyBridge-Platform kernel: [246065.060940] md127: bitmap initialized from disk: read 1 pages, set 0 of 29805 bits
Oct 17 12:05:26 irj-SandyBridge-Platform kernel: [246065.133456] md127: detected capacity change from 0 to 2000129359872
Oct 17 14:04:52 irj-SandyBridge-Platform kernel: [253230.799354] md127: detected capacity change from 2000129359872 to 0
Oct 17 14:04:52 irj-SandyBridge-Platform kernel: [253230.799371] md: md127 stopped.
Eu tentei executar o fsck e obtive
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md127
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Eu executei o e2fsck -b 8193 / dev / md127 e o e2fsck -b 32768 / dev / md127 e obtive o seguinte resultado.
e2fsck 1.42.13 (17-May-2015)
e2fsck: Bad magic number in super-block while trying to open /dev/md127
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Qualquer ideia sobre como corrigir isso e recuperar os dados seria muito apreciada!