Hi,
maybe you could give me some advice to bring my storage back to live?
I use a OMV 2.2.14, wihch was running since 2016 without problems.
The RAID5 presists of 3x3TB WD RED
Drive configuration:
/dev/sda: system and swap
/dev/sdb - /dev/sdd RAID5 array
I didn't do anythig special when the array suddenly stopped working.
As I don't need the storage permanently, I start the OMV via WOL on demand and use Autoshutdown.
Checking the OMV GUI, SMART reports for /dev/sdc:
'Device has a vew bad sectors'
All other devices are 'Good'
Here some information that may help to understand the problem:
root@OpenMediaVault:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : inactive sdd[2]
2930135512 blocks super 1.2
unused devices: <none>
root@OpenMediaVault:~# blkid
/dev/sda1: UUID="439440a1-b67d-44a9-9569-5d05be5eb1d4" TYPE="ext4"
/dev/sda5: UUID="59834cdd-708d-4ba9-9a59-1f1d6a5ee2cf" TYPE="swap"
/dev/sdd: UUID="7c016f86-f8df-c2fe-7be1-d809b79b6f1e" UUID_SUB="8d28819a-df0b-1da1-f7c1-0143ff15a021" LABEL="OpenMediaVault:RAID5" TYPE="linux_raid_member"
/dev/sdb: UUID="7c016f86-f8df-c2fe-7be1-d809b79b6f1e" UUID_SUB="d92491d5-94b1-0b92-a7a3-c28e53dcec4b" LABEL="OpenMediaVault:RAID5" TYPE="linux_raid_member"
/dev/sdc: UUID="7c016f86-f8df-c2fe-7be1-d809b79b6f1e" UUID_SUB="750ce038-2cce-d625-4ae3-4bffa812f4d4" LABEL="OpenMediaVault:RAID5" TYPE="linux_raid_member"
root@OpenMediaVault:~# fdisk -l | grep "Disk "
Disk /dev/sdc doesn't contain a valid partition table
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/sda: 250.1 GB, 250059350016 bytes
Disk identifier: 0x000307a0
Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
Disk identifier: 0x00000000
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
Disk identifier: 0x00000000
Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
Disk identifier: 0x00000000
root@OpenMediaVault:~# 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/md0 metadata=1.2 name=OpenMediaVault:RAID5 UUID=7c016f86:f8dfc2fe:7be1d809:b79b6f1e
My plan to solve the problem is to replace /dev/sdc (the drive with bad sectors) with a new (WD RED 4TB) disk and start a reassemby by:
mdadm --stop /dev/md0
mdadm --assemble --force --verbose /dev/md0 /dev/sd[dcb]
Do you agree that this is the best plan?
Thanks in advance,
Markus