I bought new hard drives, and since it's been a while, I've reinstalled OMV from the 2.1 ISO and did all upgrades and so on. I created a RAID 5 array with 4 3TB WD Red drives, and waited for it to sync. One of the issues in my previous install is whenever I would reboot the server, the array would be degraded and missing a disk - I was hoping this reinstall with a new array would fix it. Since the previous install was an upgrade from 1.x, I thought some issues might have crept in.
But anyway - I waited for this new array to sync, created an ext4 FS, and rebooted. Lo and behold, the same issue:
[ 3.227253] md/raid:md0: device sdb operational as raid disk 1
[ 3.227257] md/raid:md0: device sde operational as raid disk 3
[ 3.227260] md/raid:md0: device sdd operational as raid disk 2
[ 3.227869] md/raid:md0: allocated 0kB
[ 3.227927] md/raid:md0: raid level 5 active with 3 out of 4 devices, algorithm 2
[ 3.227977] RAID conf printout:
[ 3.227979] --- level:5 rd:4 wd:3
[ 3.227982] disk 1, o:1, dev:sdb
[ 3.227984] disk 2, o:1, dev:sdd
[ 3.227987] disk 3, o:1, dev:sde
[ 3.228098] md0: detected capacity change from 0 to 9001374842880
Alles anzeigen
I went back to the web UI, and I can recover the array, but this is really annoying. I had a previous thread with the same issue, but can't find it now.
Basically - what do I need to do for my array to withstand a reboot? And to avoid the "SparesMissing event" emails I will get once the rebuild finishes?
mdadm output:
root@omv:~# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Fri Jul 29 20:37:32 2016
Raid Level : raid5
Array Size : 8790405120 (8383.18 GiB 9001.37 GB)
Used Dev Size : 2930135040 (2794.39 GiB 3000.46 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Sun Jul 31 02:28:20 2016
State : clean, degraded, recovering
Active Devices : 3
Working Devices : 4
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 512K
Rebuild Status : 1% complete
Name : omv:3TBtimesFour (local to host omv)
UUID : 9401745d:aca59cc3:6d78e076:7e233a98
Events : 143
Number Major Minor RaidDevice State
4 8 0 0 spare rebuilding /dev/sda
1 8 16 1 active sync /dev/sdb
2 8 48 2 active sync /dev/sdd
3 8 64 3 active sync /dev/sde
Alles anzeigen
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/md0 metadata=1.2 spares=1 name=omv:3TBtimesFour UUID=9401745d:aca59cc3:6d78e076:7e233a98
Alles anzeigen