RAID5 Array missing (after a short nap)

willocrisp5000 · 24. Dezember 2019

Hey everyone, recently moved from OMV4 to 5, which went well. So I got mylar kind of working last night, decided to take a nap and boom woke up to "missing" showing up in file system, devastated at the moment. I am here for help to get this array back up but I know its not a backup so am prepared for the worst, just hoping for better haha

One thing to note, it used to be called md0 on the old OMV4 but it was working in the new install as md127 so didn't really think too much of it till now. It was also around that time when my array checks its self so may have started from that, now that I think about it,
It should be a RAID5 with 7 disks sdc-sdi

Thank you in advance!

Code

cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sdd[5](S) sdf[2](S) sde[7](S) sdh[1](S) sdg[6](S)      39069523640 blocks super 1.2       
unused devices: <none>

Code

blkid
/dev/sdb1: LABEL="Pandora" UUID="466e4f7d-ab11-4a99-862f-bd9e450b7b46" UUID_SUB="95b342a3-4777-4650-a1db-dcca33d387d0" TYPE="btrfs" PARTUUID="a5fd4a51-04b0-46f7-952b-fd50e1ca98ce"
/dev/sda1: UUID="43ED-4927" TYPE="vfat" PARTUUID="7edadeba-a922-45d8-88e8-c725192edc37"
/dev/sda2: UUID="f0648f9c-07d5-43bf-bdb8-a26fa6442109" TYPE="ext4" PARTUUID="14dad181-7ce1-4d4b-9dfb-316a640e9c4d"
/dev/sda3: UUID="6b0b2f72-60d9-46ef-b85b-ca7d04de1785" TYPE="swap" PARTUUID="6f59412a-8ebc-44bc-9f77-d3274ea087b7"
/dev/sdc: UUID="fef6a73f-a34e-a748-a8be-bb649244a519" UUID_SUB="b3492b1e-60a9-98ec-5a7f-08af48cf4454" LABEL="GLaDOS:VGER" TYPE="linux_raid_member"
/dev/sdd: UUID="fef6a73f-a34e-a748-a8be-bb649244a519" UUID_SUB="0e10bd22-749c-2313-0ff9-80b726ecdb13" LABEL="GLaDOS:VGER" TYPE="linux_raid_member"
/dev/sde: UUID="fef6a73f-a34e-a748-a8be-bb649244a519" UUID_SUB="dfa90945-2530-fb16-f839-36b7595a04aa" LABEL="GLaDOS:VGER" TYPE="linux_raid_member"
/dev/sdf: UUID="fef6a73f-a34e-a748-a8be-bb649244a519" UUID_SUB="30258e20-52b7-d19a-9234-29b7aa325ad7" LABEL="GLaDOS:VGER" TYPE="linux_raid_member"
/dev/sdg: UUID="fef6a73f-a34e-a748-a8be-bb649244a519" UUID_SUB="86f82496-14b0-f3c1-baa6-b12c498b7cca" LABEL="GLaDOS:VGER" TYPE="linux_raid_member"
/dev/sdh: UUID="fef6a73f-a34e-a748-a8be-bb649244a519" UUID_SUB="a063fec8-3265-112f-7fb2-5e5b012eeedd" LABEL="GLaDOS:VGER" TYPE="linux_raid_member"
/dev/sdi: UUID="fef6a73f-a34e-a748-a8be-bb649244a519" UUID_SUB="c2610315-5b4c-8011-55f7-e5375742c6be" LABEL="GLaDOS:VGER" TYPE="linux_raid_member"

Alles anzeigen

Code

fdisk -l | grep "Disk "
Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EZRZ-00W
Disk identifier: 86F96E9C-891B-4DEB-A641-73AD40D2EEFD
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: ADATA SU800     
Disk identifier: 48F4FE93-A7B6-4028-8E26-52F52BD87E5F
Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EFZX-68U
Disk /dev/sdd: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EFZX-68U
Disk /dev/sde: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EFAX-68K
Disk /dev/sdf: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EFAX-68L
Disk /dev/sdg: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EFAX-68K
Disk /dev/sdh: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EFAX-68L
Disk /dev/sdi: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EFAX-68L

Alles anzeigen

Code

cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# instruct the monitoring daemon where to send mail alerts
MAILADDR root


# definitions of existing MD arrays


# This configuration was auto-generated on Fri, 16 Aug 2019 07:12:16 +0000 by mkconf
ARRAY /dev/md/VGER metadata=1.2 UUID=fef6a73f:a34ea748:a8bebb64:9244a519 name=GLaDOS:VGER
root@GLaDOS:~# mdadm --detail --scan --verbose
INACTIVE-ARRAY /dev/md127 num-devices=5 metadata=1.2 name=GLaDOS:VGER UUID=fef6a73f:a34ea748:a8bebb64:9244a519
devices=/dev/sdd,/dev/sde,/dev/sdf,/dev/sdg,/dev/sdh

Alles anzeigen

geaves · 24. Dezember 2019

Have you tried rebooting

The change to the raid reference is irrelevant and nothing to worry about, what is is 7 x 8TB drives in a Raid 5, Raid 5 allows for one physical drive failure, you currently have two missing and by the output it's /dev/sd[ci]. Therefore it 'might' be possible to re assemble the array and all's well, or it could be terminal which means it's unrecoverable.

Try rebooting if the raid still shows as missing run cat /proc/mdstat if the output is the same as your post then prepare for the worst.

mdadm --stop /dev/md127

mdadm --assemble --force --verbose /dev/md127 /dev/sd[cdefghi]

This will either reassemble or it will throw an error/s

willocrisp5000 · 24. Dezember 2019

Zitat von geaves

Have you tried rebooting

The change to the raid reference is irrelevant and nothing to worry about, what is is 7 x 8TB drives in a Raid 5, Raid 5 allows for one physical drive failure, you currently have two missing and by the output it's /dev/sd[ci]. Therefore it 'might' be possible to re assemble the array and all's well, or it could be terminal which means it's unrecoverable.

Try rebooting if the raid still shows as missing run cat /proc/mdstat if the output is the same as your post then prepare for the worst.

mdadm --stop /dev/md127

mdadm --assemble --force --verbose /dev/md127 /dev/sd[cdefghi]

This will either reassemble or it will throw an error/s

Alles anzeigen

Thanks for the help. So I rebooted stopped the RAID and tried the command

Code

mdadm --assemble --force --verbose /dev/md127 /dev/sd[cdefghi]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3.
mdadm: /dev/sdd is identified as a member of /dev/md127, slot 4.
mdadm: /dev/sde is identified as a member of /dev/md127, slot 5.
mdadm: /dev/sdf is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sdg is identified as a member of /dev/md127, slot 6.
mdadm: /dev/sdh is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdi is identified as a member of /dev/md127, slot 0.
mdadm: added /dev/sdh to /dev/md127 as 1
mdadm: added /dev/sdf to /dev/md127 as 2
mdadm: added /dev/sdc to /dev/md127 as 3
mdadm: added /dev/sdd to /dev/md127 as 4
mdadm: added /dev/sde to /dev/md127 as 5
mdadm: added /dev/sdg to /dev/md127 as 6
mdadm: added /dev/sdi to /dev/md127 as 0
mdadm: /dev/md127 has been started with 7 drives.

Alles anzeigen

Annnd it worked. Is there anything I should change to avoid this happening again?

OMG thank you so much geaves!! Have an amazing holiday!
Is there a way I can buy you a beer?

geaves · 24. Dezember 2019

Zitat von willocrisp5000

Is there anything I should change to avoid this happening again?

No, but for peace of mind if you can add another drive and move to raid 6, this will allow two drive failures.

At least you have your system back for holidays

Jetzt mitmachen!