I've had a drive on my RAID5 array go bad. I replaced it, formatted the new one (GPT, since it's 3TB), and added it to the array using the webUI. Took a long time to sync, but it was working fine.
Then I got a SpareMissing event email, so I edited mdadm.conf to set spares = 0, and it was all good.
But recently, I had to reboot the server, and the array was back to 3 devices with a failed one (removed). So I re-added my new hard-disk, and waited for the resync to finish (again) - this time I didn't get the SparesMissing event email, but now I'm worried... will this happen again on reboot? It takes a long time to re-sync... using OMV 2.1.23 now.
My array (/dev/md127 - sda is the new drive):
Code
Version : 1.2
Creation Time : Tue Apr 23 20:41:25 2013
Raid Level : raid5
Array Size : 5860538880 (5589.05 GiB 6001.19 GB)
Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Tue Jan 5 10:35:31 2016
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : omv:raid5device
UUID : 76ecf19d:6eff237c:48bdc781:f074fd09
Events : 30140
Number Major Minor RaidDevice State
0 8 16 0 active sync /dev/sdb
1 8 48 1 active sync /dev/sdd
4 8 0 2 active sync /dev/sda
3 8 64 3 active sync /dev/sde
Alles anzeigen
My mdadm.conf:
Code
# 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/raid5device metadata=1.2 spares=0 name=omv:raid5device UUID=76ecf19d:6eff237c:48bdc781:f074fd09
# instruct the monitoring daemon where to send mail alerts
MAILADDR XXXXXXXXXX (redacted)
MAILFROM root
Alles anzeigen
Any help appreciated!