Crash of System Disc - Fresh 3.x Installation - Raid not accessible

Gardinero · 29. Dezember 2016

Hello there,

I am an absolute idiot... My system disc with OMV 2 crashed, so I replaced it by a new one, unplugged my three RAID drives and installed a fresh version of OMV 3.0.58.
Now I do not have access to my existing RAID and I really do not know, what to do.
Unfortunately I do not have any backup of my old config files. Will I have any possibility to get access to my files?

The output of

Code

fdisk -l

gives me the following:

Code

Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 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
Disklabel type: dos
Disk identifier: 0x7bbb5732


Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048 937195519 937193472 446,9G 83 Linux
/dev/sda2       937197566 976771071  39573506  18,9G  5 Extended
/dev/sda5       937197568 976771071  39573504  18,9G 82 Linux swap / Solaris


Partition 3 does not start on physical sector boundary.




Disk /dev/sdb: 3,7 TiB, 4000787030016 bytes, 7814037168 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 /dev/sde: 7,3 TiB, 8001563222016 bytes, 15628053168 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
Disklabel type: gpt
Disk identifier: BD9E1D03-892F-4FF9-821A-0957A6890C0B


Device     Start         End     Sectors  Size Type
/dev/sde1   2048 15628053134 15628051087  7,3T Linux filesystem


Disk /dev/sdd: 3,7 TiB, 4000787030016 bytes, 7814037168 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 /dev/sdc: 3,7 TiB, 4000787030016 bytes, 7814037168 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

Alles anzeigen

I hope, that anybody can help me!

Thanks a lot in advance.

Regards
Gardinero

ryecoaaron · 29. Dezember 2016

Were you able to mount the filesystem on the raid array in the OMV Filesystems tab?

Gardinero · 29. Dezember 2016

Hi,

the physical discs are listed under "Physical Discs" as

/dev/sdb
/dev/sdc
/dev/sdd

but under the "File Systems" tab I only see my system disc (/dev/sda1) and an additional archive disc (/dev/sde1),which are both already mounted.

Regards
Gardinero

ryecoaaron · 29. Dezember 2016

What is the output of: cat /proc/mdstat

Gardinero · 29. Dezember 2016

This commands gives me the following:

Code

Personalities : 
md127 : inactive sdc[2](S) sdb[1](S) sdd[0](S)
      9459 blocks super external:imsm

unused devices: <none>

ryecoaaron · 29. Dezember 2016

mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]
update-initramfs -u

then post the content of: cat /etc/mdadm/mdadm.conf

Gardinero · 29. Dezember 2016

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

gives me:

mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdd is busy - skipping

The content of mdadm.conf:

Code

# 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

Alles anzeigen

Gardinero · 29. Dezember 2016

Should I do

mdadm --stop /dev/md127

before?

ryecoaaron · 29. Dezember 2016

I forgot to tell you to stop the existing array first.

mdadm --stop /dev/md127
mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]

mdadm --detail --scan >> /etc/mdadm/mdadm.conf
update-initramfs -u

Gardinero · 29. Dezember 2016

Now my mdadm.conf contains:

Code

# 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/md127 metadata=imsm UUID=dbe64fb9:524aa8c6:e1c861d2:019fe54b

Alles anzeigen

ryecoaaron · 29. Dezember 2016

Perfect. What is the output of: cat /proc/mdstat

Gardinero · 29. Dezember 2016

I still get

Code

Personalities : 
md127 : inactive sdd[2](S) sdb[1](S) sdc[0](S)
      9459 blocks super external:imsm

unused devices: <none>

ryecoaaron · 29. Dezember 2016

Looking at your output again, it is using the intel matrix storage management engine. I've never dealt with that mixed with mdadm. Try:

mdadm --incremental --verbose --metadata imsm /dev/md127

Gardinero · 29. Dezember 2016

Hello ryecoaaron,

You absolutely made my day!!

I again have access to my files.

What I do not understand is, that the RAID is shown as /dev/md126 not /dev/md127.

Do I need to do anything else, to keep the RAID mounted, also after rebooting my NAS?

Regards
Lars

ryecoaaron · 29. Dezember 2016

What is the output of: cat /proc/mdstat

Hopefully adding to mdadm.conf and executing update-initramfs -u will keep it working. I would do another update-initramfs -u just to make sure.

Gardinero · 3. Januar 2017

Hello and happy new year!

Sorry for the delay.

The output of cat /proc/mdstat again is

Code

Personalities : 
md127 : inactive sdb[2](S) sdd[1](S) sdc[0](S)
      9459 blocks super external:imsm
unused devices: <none>

although mdadm.conf contains

ARRAY /dev/md127 metadata=imsm UUID=dbe64fb9:524aa8c6:e1c861d2:019fe54b

and I executed update-initramfs -u several times...

After rebooting my NAS, I always have to execute sudo mdadm --incremental --verbose --metadata imsm /dev/md127, to get access to my RAID.

After that the output of cat /proc/mdstat is:

Code

Personalities : [raid6] [raid5] [raid4] 
md126 : active raid5 sdb[2] sdc[1] sdd[0]
      7423287296 blocks super external:/md127/0 level 5, 64k chunk, algorithm 0 [3/3] [UUU]
md127 : inactive sdb[2](S) sdd[1](S) sdc[0](S)
      9459 blocks super external:imsm
unused devices: <none>

So, it is again md126 until reboot.

mdadm --detail --scan shows:

ARRAY /dev/md127 metadata=imsm UUID=dbe64fb9:524aa8c6:e1c861d2:019fe54b
ARRAY /dev/md/NAS_RAID container=/dev/md127 member=0 UUID=42b0f49f:2a43e7c4:2ebafce5:bc5bd63b
then.

Regards
Gardinero

ryecoaaron · 3. Januar 2017

Not sure what to do to get it to survive the reboot. Personally I would want to get rid of the imsm dependency but that would require rebuilding the array (no way to save the data on it).

Gardinero · 3. Januar 2017

Ok, I will backup my data and rebuild the raid.

But I can do it through the openmediavault GUI and it will be built without the imsm dependency?

Thanks in advance.

ryecoaaron · 3. Januar 2017

Zitat von Gardinero

But I can do it through the openmediavault GUI and it will be built without the imsm dependency?

I think so but I honestly don't know. I don't have a board I can test on.

Gardinero · 10. Januar 2017

Hi,

I finally made a backup of all my RAID-data and created a new RAID5 from scratch.

Thanks a lot!

Regards
Gardinero

Jetzt mitmachen!