RAID 5 array disappearing after a reboot.

kellym · 24. März 2017

I have OMV 2.1 installed on a machine.
i7-4790
Asus Z series MoBo
16GB Corsair memory
Crucial M.2 SATA3 256GB
4 x 3TB WD Red drives connected straight to the MoBo

A couple times in a row now after installing I have lost the RAID array. At first I thought maybe it was me and I clicked a wrong button. After recreating and doing some searching it kept happening. I decided to do a fresh install. Same thing before any updates are applied at all. Here is my outputs from the "Degraded or Missing" thread...

Code

root@openmediavault:~# cat /proc/mdstat
Personalities :
unused devices: <none>
root@openmediavault:~# blkid
/dev/sde1: UUID="3ff44633-64cc-4187-a332-297dad2a65c3" TYPE="ext4"
/dev/sde5: UUID="610cbe88-0db5-4e68-afa1-8cdf849318d2" TYPE="swap"
root@openmediavault:~# fdisk -l | grep sde1


WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


/dev/sde1   *        2048   904658943   452328448   83  Linux
root@openmediavault:~# fdisk -l | grep sde5


WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


/dev/sde5       904660992   937701375    16520192   82  Linux swap / Solaris
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:Storage UUID=2a3b5722:c8e0227d:b5c5dd1f:9e6ea63d
root@openmediavault:~# mdadm --detail --scan --verbose
root@openmediavault:~#

Alles anzeigen

kellym · 28. März 2017

Anyone?

ryecoaaron · 28. März 2017

What is the output of: fdisk -l | grep "Disk " | grep sd | sort

kellym · 29. März 2017

Code

root@openmediavault:~# fdisk -l | grep "Disk " | grep sd | sort


WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.




WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
Disk /dev/sde: 480.1 GB, 480103981056 bytes
root@openmediavault:~#

Alles anzeigen

ryecoaaron · 29. März 2017

The following should assemble the array.
mdadm --assemble --force --verbose /dev/md0 /dev/sd[abcd]

Then update initramfs

update-initramfs -u

kellym · 29. März 2017

Code

root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[abcd]
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: /dev/sda has no superblock - assembly aborted
root@openmediavault:~#

kellym · 30. März 2017

Anything else I can try?

ryecoaaron · 30. März 2017

Try to assemble a degraded array (without sda). Then wipe sda and add it later.

mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcd]
cat /proc/mdstat

kellym · 31. März 2017

Code

root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcd]
mdadm: looking for devices for /dev/md0
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[cd]
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sdc
mdadm: /dev/sdc has no superblock - assembly aborted
root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sdd
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sdd
mdadm: /dev/sdd has no superblock - assembly aborted
root@openmediavault:~#

Alles anzeigen

Why do I get the feeling these drives, which I swore I wiped, I not actually wiped...

ryecoaaron · 31. März 2017

Your last two commands would have never worked since you can't start a raid 5 array with two or more missing disks.

How did you wipe them? I use dd if=/dev/zero of=/dev/sda bs=512 count=100000 Obviously, you don't want to do that if there is data on them.

kellym · 31. März 2017

I just used the feature in the gui. Whipe > quick wipe. The data on the disks does not matter.

Code

root@openmediavault:~# dd if=/dev/zero of=/dev/sda bs=512 count=100000
100000+0 records in
100000+0 records out
51200000 bytes (51 MB) copied, 1.20614 s, 42.4 MB/s

kellym · 31. März 2017

Well this is a first. I went in through SSH and ran fdisk with options s, then w, then p, then d for each number, then s and w again. Now in the GUI it shows all is good when I choose the quick wipe feature.

Making a new RAID 5 array and didn't tell me to kick rocks yet. I'll check this after work.

flechoide · 18. April 2017

Zitat von kellym

Well this is a first. I went in through SSH and ran fdisk with options s, then w, then p, then d for each number, then s and w again. Now in the GUI it shows all is good when I choose the quick wipe feature.

Making a new RAID 5 array and didn't tell me to kick rocks yet. I'll check this after work.

Hi,

Not sure if it worked for yu already, I had a similar issue , yu can read here : Mdadm device (/dev/md3) raid5 get lost on every reboot

My problem was solved when I used primary partitions instead the whole disk ; using /dev/sda1 /dev/sdb1 etc ... instead of /dev/sda /dev/sdb .

I think it should work anyway with full disk device instead of using partiions, but for some reason after the reboot the superblocks were overwrited.

Jetzt mitmachen!