Raid 1 Missing After Reboot

DeviousDog · Feb 19th 2016

Hello,

This topic may not be in the right sub-forum, I am new to forums, but yesterday I decided to power down the OMV NAS and ran into problems with the RAID. After I turned the NAS on, the RAID 1 Array which was created through the OMV GUI disappeared. Luckily, I have a backup from about a week ago. I was wondering if the software RAID 1 behavior always acts this way? I am currently recreating the array, but I believe the Issue will arise the next time I reboot. I read some other posts but there is no clear answer as to why this happens. I am running OMV off USB Flash Drive with fs2ram enabled with changes made to fstab. I am also using 2X2TB Hard Drives for Raid 1.

Display Spoiler

Above is the output of cat /proc/mdstat if it helps

Display Spoiler

Above is the output of blkid

Display Spoiler

Code

fdisk -l


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


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1  3907029167  1953514583+  ee  GPT


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


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  3907029167  1953514583+  ee  GPT


Disk /dev/sdc: 15.5 GB, 15522070528 bytes
255 heads, 63 sectors/track, 1887 cylinders, total 30316544 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000968db


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048    28983295    14490624   83  Linux
/dev/sdc2        28985342    30314495      664577    5  Extended
/dev/sdc5        28985344    30314495      664576   82  Linux swap / Solaris


Disk /dev/md0: 2000.3 GB, 2000264560640 bytes
2 heads, 4 sectors/track, 488345840 cylinders, total 3906766720 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/md0 doesn't contain a valid partition table

Display More

Above is the output of fdisk -l

Here is a link to another similar forum.

Any help would be appreciated.

DeviousDog · Feb 19th 2016

I forgot to mention that the raid is currently re-syncing.

DeviousDog · Feb 20th 2016

I re synced the raid and the data is all where it was. I just do not understand why with a standard shutdown the RAID 1 would be lost.

DeviousDog · Feb 20th 2016

This is the mdadm.conf file

Display Spoiler

DeviousDog · Feb 21st 2016

Looking at the support info like the sticky stated to do, below are the partitions from support info.

Display Spoiler

DeviousDog · Feb 21st 2016

Below is the static file system information.

Display Spoiler

DeviousDog · Feb 21st 2016

Lastly, here is the mount information. (very long)

Display Spoiler

Code

================================================================================
= Mount information
================================================================================
14 20 0:13 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
15 20 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
16 20 0:5 / /dev rw,relatime - devtmpfs udev rw,size=10240k,nr_inodes=1008238,mode=755
17 16 0:10 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts rw,gid=5,mode=620,ptmxmode=000
18 20 0:14 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs rw,size=808308k,mode=755
20 1 8:33 / / rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
21 18 0:16 / /run/lock rw,nosuid,nodev,noexec,relatime - tmpfs tmpfs rw,size=5120k
22 18 0:17 / /run/shm rw,nosuid,nodev,noexec,relatime - tmpfs tmpfs rw,size=1616600k
23 20 0:18 / /var/lib/nfs/rpc_pipefs rw,relatime - rpc_pipefs rpc_pipefs rw
24 20 8:33 /var/spool /var/folder2ram/var/spool rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
25 20 8:33 /var/log /var/folder2ram/var/log rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
26 20 8:33 /var/lib/php5 /var/folder2ram/var/lib/php5 rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
27 20 8:33 /var/lib/monit /var/folder2ram/var/lib/monit rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
28 20 8:33 /var/lib/rrdcached /var/folder2ram/var/lib/rrdcached rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
29 20 0:19 / /var/lib/php5 rw,relatime - tmpfs folder2ram rw
30 20 0:20 / /var/log rw,relatime - tmpfs folder2ram rw
31 20 0:21 / /var/spool rw,relatime - tmpfs folder2ram rw
32 20 0:22 / /var/lib/monit rw,relatime - tmpfs folder2ram rw
33 20 8:33 /var/lib/openmediavault/rrd /var/folder2ram/var/lib/openmediavault/rrd rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
34 20 0:23 / /var/lib/rrdcached rw,relatime - tmpfs folder2ram rw
35 20 0:24 / /var/lib/openmediavault/rrd rw,relatime - tmpfs folder2ram rw
36 20 8:33 /var/tmp /var/folder2ram/var/tmp rw,noatime,nodiratime - ext4 /dev/disk/by-uuid/7da352e3-1578-4917-9069-2627852d9716 rw,errors=remount-ro,user_xattr,barrier=1,data=ordered
37 20 0:25 / /var/tmp rw,relatime - tmpfs folder2ram rw
38 20 9:0 / /media/52e47c5e-01d3-4fca-ba05-dcbafc611780 rw,noexec,relatime - ext4 /dev/md0 rw,user_xattr,barrier=1,stripe=256,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group
--------------------------------------------------------------------------------
0:13 sysfs  /sys
0:3 /proc  /proc
0:5 udev  /dev
0:10 devpts  /dev/pts
0:14 tmpfs  /run
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /
0:16 tmpfs  /run/lock
0:17 tmpfs  /run/shm
0:18 rpc_pipefs  /var/lib/nfs/rpc_pipefs
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /var/folder2ram/var/spool
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /var/folder2ram/var/log
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /var/folder2ram/var/lib/php5
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /var/folder2ram/var/lib/monit
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /var/folder2ram/var/lib/rrdcached
0:19 folder2ram  /var/lib/php5
0:20 folder2ram  /var/log
0:21 folder2ram  /var/spool
0:22 folder2ram  /var/lib/monit
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /var/folder2ram/var/lib/openmediavault/rrd
0:23 folder2ram  /var/lib/rrdcached
0:24 folder2ram  /var/lib/openmediavault/rrd
8:33 /dev/sdc1 7da352e3-1578-4917-9069-2627852d9716 /var/folder2ram/var/tmp
0:25 folder2ram  /var/tmp
9:0 /dev/md0 52e47c5e-01d3-4fca-ba05-dcbafc611780 /media/52e47c5e-01d3-4fca-ba05-dcbafc611780

Display More

DeviousDog · Feb 21st 2016

I just restarted OMV and these are the relevant configurations.

cat /proc/mdstat

Display Spoiler

blkid

Display Spoiler

fdisk -l

Display Spoiler

There are 2x2tb hdd in my system that are shown in physical disks but not as raid and without a file system after restart.

DeviousDog · Feb 21st 2016

I do not know whether I was clear or how clear I was in my last post, but the raid 1 completely vanishes after reboot and the only solution that I know of is to recreate the array, but that takes at least 6 hours. I do not know what to do to mediate this problem.

DeviousDog · Feb 21st 2016

Could the raid issues be associated with the Flash Memory Plugin, or is it just something with OMV or my hardware? I really am at a dead end here. I know the OMV experts like @subzero79 and @davidh2k are great at resolving these issues and their help would be greatly appreciated.

DeviousDog · Feb 21st 2016

If I try mdadm --assemble --verbose --force /dev/md127 /dev/sd[abcdefghijl] like other users have, below is the output

Display Spoiler

subzero79 · Feb 21st 2016

I dont have a clear answer for you with the info you post here. Raid not engaging at boot might be caused by several causes. Experience gathered here in the forum, for example people using some of the disks arrays with partition and brand of the disks, some of them are constant trouble at raid.

Can you post here dmesg in pasteBin please link.

DeviousDog · Feb 22nd 2016

What exactly is dmesg? Is it the OMV log or is it a command to enter in ssh?

subzero79 · Feb 22nd 2016

In ssh type dmesg > /root/dmesg.txt

You can take the file out and paste the contents in pasteBin.

davidh2k · Feb 22nd 2016

I'm no good with mdadm, so pardon me if I stay out of such issues.

Greetings
David

DeviousDog · Feb 22nd 2016

Sorry if I can't reply immediately, I am currently away from home and will return soon. Thank you for your help.

DeviousDog · Feb 22nd 2016

Here are the results. I am not sure this is correct because typing

Code

dmesg > /root/dmesg.txt

led to a file creation i believe, but I do not know how to extract the file since I am a Linux noob, so I simply typed dmesg and pasted the contents on Pastebin.

DeviousDog · Feb 22nd 2016

Ok I used filezilla to copy the file and this is the output.

subzero79 · Feb 22nd 2016

I don't see any mdadm action at boot.

Can you post here ls -la /etc/rc[S2345].d | grep mdadm

DeviousDog · Feb 22nd 2016

@subzero79, below is the output of ls -la /etc/rc[S2345].d | grep mdadm

Code

ls -la /etc/rc[S2345].d | grep mdadm
lrwxrwxrwx   1 root root   15 Feb  6 13:11 S04mdadm -> ../init.d/mdadm
lrwxrwxrwx   1 root root   15 Feb  6 13:11 S04mdadm -> ../init.d/mdadm
lrwxrwxrwx   1 root root   15 Feb  6 13:11 S04mdadm -> ../init.d/mdadm
lrwxrwxrwx   1 root root   15 Feb  6 13:11 S04mdadm -> ../init.d/mdadm
lrwxrwxrwx   1 root root   20 Dec 25 16:56 S08mdadm-raid -> ../init.d/mdadm-raid

Raid 1 Missing After Reboot

Participate now!

Tags