Hi,
I'm hoping I haven't done something irretrievable...
I had a 4x2tb RAID 5 setup running fine on OMV5. (5.5.3-1) A disk started to fail and the raid became "Degraded".
I determined which serial number was the bad disk.
Shut the system down.
Replaced the disk.
Started up again.
Did a "Quick wipe" on the new disk
Expected to be able to rebuild the RAID and carry on.
The RAID 5 I had set up is no longer on the list in the "Raid Management" section of OMV.
In "File systems", the file system I had set up is listed as "Missing"
If I try to set up a new RAID5, there are no disks available to select.
Can I rescue my original RAID array, Zulu? Looking below it seems to still be there...?
Code
cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : inactive sdd[3](S) sdb[1](S) sdc[2](S)
5860147464 blocks super 1.2
unused devices: <none>
Code
blkid
/dev/sdb: UUID="e722afd9-5803-5460-ce00-e63017883000" UUID_SUB="5667c0d5-4cec-a644-36a3-e641ec176a46" LABEL="openmediavault.local:zulu" TYPE="linux_raid_member"
/dev/sdc: UUID="e722afd9-5803-5460-ce00-e63017883000" UUID_SUB="d49ed9a5-6400-f405-ea4d-0601f2e60642" LABEL="openmediavault.local:zulu" TYPE="linux_raid_member"
/dev/sde1: UUID="173d1141-65e9-4ee1-ae31-b73d34f7b2cf" TYPE="ext4" PARTUUID="9d8e1096-01"
/dev/sde5: UUID="6947d5ca-f259-4fe7-be54-5b945620213c" TYPE="swap" PARTUUID="9d8e1096-05"
/dev/sdd: UUID="e722afd9-5803-5460-ce00-e63017883000" UUID_SUB="21ba9f1c-88ed-e1ea-944d-71ba862a1252" LABEL="openmediavault.local:zulu" TYPE="linux_raid_member"
/dev/sda1: PARTUUID="47bc5bbc-b468-49e3-a4ef-608d2bd5d20b"
Code
fdisk -l | grep "Disk "
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HDS72302
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: SAMSUNG HD204UI
Disk /dev/sde: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: CT120BX500SSD1
Disk identifier: 0x9d8e1096
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EARS-00M
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: TOSHIBA HDWD120
Disk identifier: FFD018E0-5D27-4155-AF1C-2C93CEF182EA
Alles anzeigen
Code
cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# 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>
# instruct the monitoring daemon where to send mail alerts
MAILADDR omv@spampit.co.uk
MAILFROM root
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=openmediavault.local:zulu UUID=e722afd9:58035460:ce00e630:17883000
Alles anzeigen