OMV loses mirrored RAID

Hexcode · 16. Dezember 2014

Hi,

I installed 2x 3TB and 2x 1TB Hard-Drives into the OMV-System - on each harddrive of the same system I want to add a RAID1 System.
On the 3TB Harddrives it's no problem - there are two RAIDs running (dev/sdd2 + dev/sde2 and dev/sdd3 + dev/sde3)
The problem is: everytime I want to set up the RAID on the 1TB-harddrives, everything is working fine, until a reboot - then OMV doesn't remeber that there was a RAID /dev/md2 on the two 1TB-drives.
I can rebuild the raid without any problems, but I have to do this everytime the systems has to reboot.

Is there a setting I'm missing or something?

Greetings
Hexcode

subzero79 · 16. Dezember 2014

Did you partition those drives? For the second array? Can you post here fdisk -l and blkid
Anyway if you're willing to start the array again first wipe the disks in the physical section and create the array again. Check if they persist this time.
BTW why are you using 2 partitioned hard drives to make 2 x raid1? I mean the first ones

Hexcode · 16. Dezember 2014

I already tried the wipe and create a new array solution already - didn't work.

fdisk -l:

Code

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


Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 1953525167 976762583+ ee GPT


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


Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 1953525167 976762583+ ee GPT


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


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


 Device Boot Start End Blocks Id System
/dev/sdd1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.


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


Disk /dev/sdc: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 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/sdc1 1 62533295 31266647+ ee GPT


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


Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


 Device Boot Start End Blocks Id System
/dev/sde1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/md0: 15.0 GB, 14991360000 bytes
2 heads, 4 sectors/track, 3660000 cylinders, total 29280000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


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


Disk /dev/md1: 2984.9 GB, 2984946499584 bytes
2 heads, 4 sectors/track, 728746704 cylinders, total 5829973632 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


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


Disk /dev/md2: 1000.1 GB, 1000070512640 bytes
2 heads, 4 sectors/track, 244157840 cylinders, total 1953262720 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/md2 doesn't contain a valid partition table

Alles anzeigen

-> Seems like it doesn't work because they are usign GPT instead of MBR.

blkid:

Code

/dev/sde2: UUID="e64ccd0d-4273-aad7-b678-3240c80b9884" UUID_SUB="c3442447-583c-7da6-6062-f9f2474f4ed6" LABEL="NAS:0" TYPE="linux_raid_member"
/dev/sde3: UUID="947f253b-68a2-fa9c-bf23-4046e027e208" UUID_SUB="12a25c1b-d4e3-f9e2-4522-c55bd17db6e0" LABEL="NAS:1" TYPE="linux_raid_member"
/dev/sdd2: UUID="e64ccd0d-4273-aad7-b678-3240c80b9884" UUID_SUB="6d2158f2-b632-65fe-25d2-81cfdadfe910" LABEL="NAS:0" TYPE="linux_raid_member"
/dev/sdd3: UUID="947f253b-68a2-fa9c-bf23-4046e027e208" UUID_SUB="33233cd6-e491-3000-559b-a3b8937a4e8f" LABEL="NAS:1" TYPE="linux_raid_member"
/dev/sdc1: UUID="5748-248B" TYPE="vfat"
/dev/sdc2: UUID="0b2bc64e-3a1b-48e6-be15-b597767be52d" TYPE="ext4"
/dev/md1: UUID="f4bddd95-df10-4822-8043-3b12867715b0" TYPE="ext4"
/dev/md0: UUID="54b98109-4f1b-4f04-ad52-6717e56e5e79" TYPE="ext4"
/dev/sda: UUID="9165353f-380d-2064-7e9e-f964852b62ae" UUID_SUB="17183433-28d5-8d3a-e961-f7f698c008ea" LABEL="NAS:2" TYPE="linux_raid_member"
/dev/sdb: UUID="9165353f-380d-2064-7e9e-f964852b62ae" UUID_SUB="757b2e16-3406-b549-1c3f-d1b720b7b157" LABEL="NAS:2" TYPE="linux_raid_member"
/dev/md2: UUID="43b0d8c8-3f27-46c7-aec8-d4a066d9e9d6" TYPE="ext4"

Alles anzeigen

And I'm using the 3TB Raid with the two partitions, because it's an old RAID build from another system, which I just plugged in into the OMV-NAS. Is there a known way to delete the first RAID and add the space do the second RAID on the 3TB drives - without recreating the RAID?

subzero79 · 16. Dezember 2014

Is strange the blkid displays sda and sdb as raw drives for raid. fdisk shows a partition like sda1

I usually run wipe secure for 10 seconds then the quick one. After that make sure fdisk displays sda and sdb without the partition (sda1 or sdb1)

From there make the raid again in the webUI of OMV

There was a user with a similar problem last week

RAID vanishes after reboot

Hexcode · 17. Dezember 2014

Thanks subzero - after doing what you said everything seems to run smooth now.

subzero79 · 17. Dezember 2014

You can transform your double partition array. Is a long process but you will have to work with a degraded array. Removing one of the drives from the two arrays and using that drive to construct another whole drive "degraded" array. Move the contents (across degraded arrays) and then remove the old one and add the drive it to the new degraded array.
Most of this is done with CLI BTW

Lots of degraded in the sentence....let me know if you have any doubts

Jetzt mitmachen!