Hallo zusammen,
Mein Raid ist mal wieder "verschwunden"... Das Problem tauchte auf nach einem Stromausfall. Nach dem lesen verschiedener Beiträge im Forum, denke ich, dass sich das Problem lösen lässt, indem man den superblock des betreffenden Laufwerks löscht bzw. neu erstell(en)t (lässt). Sollte ich falsch liegen mit meiner Vermutung, lasse ich mich gern berichtigen. Das Hinzufügen des Laufwerks zum Raidverbund schlug jedenfalls fehl. Da ich mir unsicher bin, ob ich recht habe mit dem Superblock auf /dev/sdd und da ich das mit dem superblock löschen noch nicht gemacht habe, benötige ich mal etwas Hilfe dabei, wie ich vorgehen muss. Vielen Dank schon mal im Voraus.
Wie oben bereits erwähnt, war / ist das RAID nach einem Powerloss inaktiv, degraded - Das Raid besteht aus 6 Disk (derzeit kein spare) /dev/sda ist eine SSD mit dem OS + OMV
root@openmediavault:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sde[4](S) sdd[2](S) sdb[0](S) sdc[5](S) sdg[1](S) sdf[3](S)
17580834576 blocks super 1.2
root@openmediavault:~# blkid
/dev/sdb: UUID="012a11bc-bce8-c44a-f036-c177460a832e" UUID_SUB="379dceec-ea33-269f-43aa-afbf2a0040f0" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdc: UUID="012a11bc-bce8-c44a-f036-c177460a832e" UUID_SUB="de87bac5-94f9-bd6f-cd6a-ccd1d5c75b2d" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdg: UUID="012a11bc-bce8-c44a-f036-c177460a832e" UUID_SUB="034bda2d-eb82-de29-3aef-d977ebf0ceeb" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sda1: UUID="399A-16F5" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="5901e741-a0d6-4741-83e5-cbe1b9eec2ae"
/dev/sda2: UUID="592dfef8-5d55-48c1-9534-00cb2ff00430" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a2509af3-792e-4a0e-9436-6a4c40226892"
/dev/sda3: UUID="b459774e-d1f4-41fa-acec-cb43193f45a9" TYPE="swap" PARTUUID="998f86df-7122-4a51-9a46-785cee567728"
/dev/sda4: UUID="5168aceb-50ce-45be-b5f2-861d704678d7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="10cfd585-3d6f-4ddf-8a55-fc7f31aa4a4a"
/dev/sdf: UUID="012a11bc-bce8-c44a-f036-c177460a832e" UUID_SUB="5def3075-26ce-76f7-d74a-204b4631afa5" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sde: UUID="012a11bc-bce8-c44a-f036-c177460a832e" UUID_SUB="c9c0a720-47cc-bbbf-001f-4af58b458a6a" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdd: UUID="012a11bc-bce8-c44a-f036-c177460a832e" UUID_SUB="d3b8b37d-ddca-a70d-b581-b091e195ad72" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
root@openmediavault:~# fdisk -l | grep "Disk"
Disk /dev/sdb: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sdc: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sdg: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SanDisk SDSSDH3
Disklabel type: gpt
Disk identifier: 4563910D-1B11-45C2-BE61-BDF9115BCC1D
Disk /dev/sdf: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sde: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sdd: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Disk /dev/sdh: 460.27 GiB, 494206451712 bytes, 965246976 sectors
root@openmediavault:~# 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>
# definitions of existing MD arrays
ARRAY /dev/md/NAS metadata=1.2 name=openmediavault:NAS UUID=012a11bc:bce8c44a:f036c177:460a832e
root@openmediavault:~# mdadm --detail --scan --verbose
INACTIVE-ARRAY /dev/md127 num-devices=6 metadata=1.2 name=openmediavault:NAS UUID=012a11bc:bce8c44a:f036c177:460a832e
devices=/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde,/dev/sdf,/dev/sdg
root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@openmediavault:~# mdadm --examine --scan
ARRAY /dev/md/NAS metadata=1.2 UUID=012a11bc:bce8c44a:f036c177:460a832e name=openmediavault:NAS
root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcdefg]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 5.
mdadm: /dev/sdd is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sde is identified as a member of /dev/md127, slot 4.
mdadm: /dev/sdf is identified as a member of /dev/md127, slot 3.
mdadm: /dev/sdg is identified as a member of /dev/md127, slot 1.
mdadm: added /dev/sdg to /dev/md127 as 1
mdadm: added /dev/sdd to /dev/md127 as 2 (possibly out of date)
mdadm: added /dev/sdf to /dev/md127 as 3
mdadm: added /dev/sde to /dev/md127 as 4
mdadm: added /dev/sdc to /dev/md127 as 5
mdadm: added /dev/sdb to /dev/md127 as 0
mdadm: /dev/md127 has been started with 5 drives (out of 6).
root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
