Hello,
I don't understand what is happening.
I'm using OpenMediaVault 3.0.99 (Erasmus)
- 1 mounth before, I had a RAID 1 alert so I bought a new HDD.
- After trying RAID reconstruction, I had mail alert because the old HDD had one bad sector...
- Today, RAID was not available yet.
I tried reboots: nothing
I tried to check all HDD on my computer: I couldn't mount them to see the data's inside - After removing the fail HDD and keeping the new: I have no data yet
- After plugin the fail HDD and keeping the now: I have no data yet but RAID is available now for repair.
To avoid mistake and data lost, what please I have to do?
Informations
root@ntx-010b:/srv/dev-disk-by-label-Donnees# mdadm -S /dev/md127mdadm: stopped /dev/md127
root@ntx-010b:/srv/dev-disk-by-label-Donnees# cat /proc/mdstat
Personalities : [raid1]
unused devices: <none>
root@ntx-010b:/srv/dev-disk-by-label-Donnees# uname -a
Linux ntx-010b 3.10.92+ #1 SMP PREEMPT Tue Nov 17 11:14:11 CET 2015 armv7l GNU/Linux
blkid
root@ntx-010b:/srv/dev-disk-by-label-Donnees# blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="96C3-9298" TYPE="vfat" PARTUUID="000f1766-01"
/dev/mmcblk0p2: LABEL="omv" UUID="e139ce78-9841-40fe-8823-96a304a09859" TYPE="ext4" PARTUUID="000f1766-02"
/dev/mmcblk0p3: LABEL="files" UUID="540b009b-4190-4cfd-a50b-1bceadb10421" TYPE="ext4" PARTUUID="000f1766-03"
/dev/mmcblk0p5: LABEL="Local" UUID="e839b1e6-1c66-4553-afa8-4413ce915c0d" TYPE="ext4" PARTUUID="000f1766-05"
/dev/mmcblk0p6: LABEL="SWAP" UUID="59da0ba6-5322-4595-8a6e-1c87c24100a6" TYPE="swap" PARTUUID="000f1766-06"
/dev/sda: UUID="fe4404b3-c566-b890-5815-01be50dd69c4" UUID_SUB="96adc445-7afb-cc5d-8f4a-2d596ecd7ab7" LABEL="ntx-010b:RAID1" TYPE="linux_raid_member"
/dev/sdb: UUID="fe4404b3-c566-b890-5815-01be50dd69c4" UUID_SUB="ce201133-9a4f-b0a5-2298-42c8a3933b59" LABEL="ntx-010b:RAID1" TYPE="linux_raid_member"
/dev/mmcblk0: PTUUID="000f1766" PTTYPE="dos"
lsmod | grep raid
root@ntx-010b:/srv/dev-disk-by-label-Donnees# lsmod | grep raid
raid6_pq 86188 1 btrfs
raid1 29063 1
md_mod 115158 1 raid1
cat /etc/mdadm/mdadm.conf
root@ntx-010b:/srv/dev-disk-by-label-Donnees# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# 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>
# definitions of existing MD arrays
ARRAY /dev/md/ntx-010b:RAID1 metadata=1.2 spares=1 name=ntx-010b:RAID1 UUID=fe4404b3:c566b890:581501be:50dd69c4
# instruct the monitoring daemon where to send mail alerts
MAILADDR judibet@jvlinux.fr
MAILFROM root
/etc/default/mdadm
# INITRDSTART:
# list of arrays (or 'all') to start automatically when the initial ramdisk
# loads. This list *must* include the array holding your root filesystem. Use
# 'none' to prevent any array from being started from the initial ramdisk.
#INITRDSTART='none'
# AUTOSTART:
# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically
# during boot?
AUTOSTART=true
# AUTOCHECK:
# should mdadm run periodic redundancy checks over your arrays? See
# /etc/cron.d/mdadm.
AUTOCHECK=true
# START_DAEMON:
# should mdadm start the MD monitoring daemon during boot?
START_DAEMON=true
# DAEMON_OPTIONS:
# additional options to pass to the daemon.
DAEMON_OPTIONS="--syslog"
# VERBOSE:
# if this variable is set to true, mdadm will be a little more verbose e.g.
# when creating the initramfs.
VERBOSE=false
This topic checked